Hotel Wifi forward not working (net::ERR_ADDRESS_UNREACHABLE)

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi all

I bought a GL inet AR750S-EXT and want to use it for a hotel, which allows only one device.
Several devices from my side shall then connect to the router.
Based on some entries it shall be possible. I tried it at an airport and it worked.
I already disabled DNS Rebind Attack Protection, to get it working for the airport.

Now I was using my android smartphone, connecting to AR750 5Ghz Wifi.
Connecting with Hotel Wifi is o.k., but then redirect leads to 192.168.1.250:8083 and replies with "net::ERR_ADDRESS_UNREACHABLE".
Entering correct transfered Url also does not work.

Using other smartphones connected to Hotel Wifi routes and translates correct.

I got the complete system log and seen the following part within:

Sun Jun 16 06:46:47 2019 user.info : [  145] gl-wifi-core>> (HTML) new session init...
Sun Jun 16 06:47:18 2019 user.info : [  243] gl-sdk>> session delete .. Token invalid!
Sun Jun 16 06:47:20 2019 user.info : [  162]: gl-sdk>> (FCGI) new session init...
Sun Jun 16 06:49:39 2019 user.info : [  145] gl-wifi-core>> (HTML) new session init...
Sun Jun 16 06:49:53 2019 user.info : [  243] gl-sdk>> session delete .. Token invalid!
Sun Jun 16 06:58:24 2019 daemon.notice netifd: wwan (10085): udhcpc: sending renew to 192.168.8.250
Sun Jun 16 07:04:43 2019 daemon.err gl_monitor[3526]: Failed to connect to the switch. Use the "list" command to see which switches are available.
Sun Jun 16 07:13:24 2019 daemon.notice netifd: wwan (10085): udhcpc: sending renew to 192.168.8.250
Sun Jun 16 07:19:41 2019 user.info : [  145] gl-wifi-core>> (HTML) new session init...
Sun Jun 16 07:19:51 2019 user.info : [  243] gl-sdk>> session delete .. Token invalid!
Sun Jun 16 07:20:54 2019 daemon.notice ne

tifd: wwan (10085): udhcpc: sending renew to 192.168.8.250

Any suggestion?

Best regards
Chris

2

Chris, I recognize the GL.iNet OEM firmware there, which I run myself on the GL-AR750S I travel with. My first guess is a captive-portal issue, but that puts you squarely in the packages that GL.iNet provides. They’ve got an active forum that might be a better place to ask.

More detail of the problem you’re seeing would be helpful on either forum.

3

Hi Jeff
I already placed my question there either.
Sometimes different forums are useful :wink:

They replied that within twice the same IP range 192. of both different wifi will cause to this behavior.
After I changed my local one (LAN) to 10.xx.xx.xx it worked.

I suggest that within two different interfaces it would handle it correctly, but it does not.

So topic can be closed..maybe useful for others, which got the same issue,

BR

1 Like
4

Feel free to mark as solution with the checkbox and edit the title to start with "[Solved]" or the like

image click dots, thenimage

Click "pencil" then edit
image