I used a travel router at the last hotel I was at but didn’t realize the firmware was buggy — it wouldn’t respond to DNS queries whatsoever on my personal network.
I unfortunately forgot my Ethernet cable so it was a real challenge.
Remembering that iOS uses Wi-Fi Privacy (changes MAC address constantly) I just brought up their portal on my phone, signed in, cloned the MAC address then on iOS chose “Forget this Network.”
Worked like a charm! (Then the travel router updated its firmware and DNS was back on track.)
What was incredibly strange about my situation was that it was initially a DNS problem, it couldn’t resolve the addresses tha tthe hotel wifi wanted it to get to for the portal. I double checked, and basic DNS queries were working, just not those ones.
So I figured, I’ll go on my phone, grab the IP addresses it’s connecting to, stick those in my hosts file, and they’ll get resolved. Well, this worked for the first portal address, but the one it redirected to couldn’t be reached. Nothing I tried worked, so I had to do what I described above.
In my situation the hotel’s DNS was properly giving out the IP address to its portal but the travel router wouldn’t respond whatsoever to DNS queries. Wireshark on a laptop showed no traffic whatsoever back; that was the firmware bug they’d addressed in the update. (DNS on the router itself going out to the hotel network was fine though.)
I used a travel router at the last hotel I was at but didn’t realize the firmware was buggy — it wouldn’t respond to DNS queries whatsoever on my personal network.
I unfortunately forgot my Ethernet cable so it was a real challenge.
Remembering that iOS uses Wi-Fi Privacy (changes MAC address constantly) I just brought up their portal on my phone, signed in, cloned the MAC address then on iOS chose “Forget this Network.”
Worked like a charm! (Then the travel router updated its firmware and DNS was back on track.)
What was incredibly strange about my situation was that it was initially a DNS problem, it couldn’t resolve the addresses tha tthe hotel wifi wanted it to get to for the portal. I double checked, and basic DNS queries were working, just not those ones.
So I figured, I’ll go on my phone, grab the IP addresses it’s connecting to, stick those in my hosts file, and they’ll get resolved. Well, this worked for the first portal address, but the one it redirected to couldn’t be reached. Nothing I tried worked, so I had to do what I described above.
Nice workaround!
In my situation the hotel’s DNS was properly giving out the IP address to its portal but the travel router wouldn’t respond whatsoever to DNS queries. Wireshark on a laptop showed no traffic whatsoever back; that was the firmware bug they’d addressed in the update. (DNS on the router itself going out to the hotel network was fine though.)