Cannot use repeater function for a cruise wifi

Hi, I am using a GL-MT1300 Beryl router with the firmware 4.3.6. I tried to connect to the cruise wifi through the router. The connection is fine, the router gets the IP and default gateway info etc, but after series of attempts to load the captive portal page my browser got redirected to the page with the url something like www.whatever-authentication.url/blocked_device.php?blahblahblah
I connected my laptop directly to the cruise wifi and the captive portal loaded ok. So I registered the laptop there. I am assuming the cruise wifi blocks the router vendor by MAC address. I cloned the registered laptop’s MAC address and tried to connect the router again, but besides the successful connection and getting the IP address it is not going anywhere. Tracert to the external IP addresses does not go anywhere after the 1st hop following the router’s default gateway (I mean it does show that second local IP in the tracert after the router’s gateway but stops there). I am not using the DNS rebinding feature, VPN or anything else, it is pretty much out of the box config. What is weird is that my phone connected to the router’s wifi network managed to receive some data from the internet at some point. It stayed connected to the wifi for a few hours and once in a while it showed some notifications from the apps, loaded some emails etc., so the internet supposedly worked for at least a few seconds. But every time I am trying going to the internet manually it does not receive anything from the DNS and does not want to open any IP farther than that next hop of the router’s gateway. The router’s log does not show any obvious failures or blocks. And again, the same laptop can access the Internet when connected directly to the cruise wifi

Anyone had this issue before? Is there a way around?

1 Like

Below are some logs

Sun Apr 9 13:35:32 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:33 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:35:34 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:34 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:35:35 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:35:35 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:35 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:35:36 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:35:37 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:37 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:35:37 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:35:37 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 RADIUS: starting accounting session 586569EA0DA8968F
Sun Apr 9 13:35:37 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 WPA: pairwise key handshake completed (RSN)
Sun Apr 9 13:35:37 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 60:57:18:c0:66:79
Sun Apr 9 13:35:37 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.8.218 60:57:18:c0:66:79
Sun Apr 9 13:35:37 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.8.218 60:57:18:c0:66:79 LAPTOP-NAME-REDACTED
Sun Apr 9 13:35:53 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:35:53 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:54 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:56 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:56 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:35:57 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:35:57 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:35:57 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:00 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:36:01 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:01 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:02 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:36:02 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:02 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:11 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: deauthenticated due to local deauth request
Sun Apr 9 13:36:48 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:48 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:49 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:36:50 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:50 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:51 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:51 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:52 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:36:52 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:36:52 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:36:52 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:36:52 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 RADIUS: starting accounting session 6CEE307B4DDB84C1
Sun Apr 9 13:36:52 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 WPA: pairwise key handshake completed (RSN)
Sun Apr 9 13:36:52 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 60:57:18:c0:66:79
Sun Apr 9 13:36:55 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.8.218 60:57:18:c0:66:79
Sun Apr 9 13:36:55 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.8.218 60:57:18:c0:66:79 LAPTOP-NAME-REDACTED
Sun Apr 9 13:37:09 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:37:24 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:37:24 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:24 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:37:26 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:37:26 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:26 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:37:27 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:37:28 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:28 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:37:29 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:37:29 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:29 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:37:37 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:38 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Apr 9 13:37:38 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:39 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:40 2023 daemon.notice hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:37:41 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:37:41 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 2)
Sun Apr 9 13:37:41 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:37:41 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 RADIUS: starting accounting session 42A7EEFDC0106CE3
Sun Apr 9 13:37:41 2023 daemon.info hostapd: wlan0: STA 60:57:18:c0:66:79 WPA: pairwise key handshake completed (RSN)
Sun Apr 9 13:37:41 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 60:57:18:c0:66:79
Sun Apr 9 13:37:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.8.218 60:57:18:c0:66:79
Sun Apr 9 13:37:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.8.218 60:57:18:c0:66:79 LAPTOP-NAME-REDACTED
Sun Apr 9 13:38:10 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1452) new scan task…
Sun Apr 9 13:38:10 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1464) Scan starting…
Sun Apr 9 13:38:11 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1606) .tmp.phy0.sta0: scan…
Sun Apr 9 13:38:16 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1644) .tmp.phy0.sta0: found 18 networks
Sun Apr 9 13:38:16 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1606) .tmp.phy1.sta0: scan…
Sun Apr 9 13:38:26 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1644) .tmp.phy1.sta0: found 53 networks
Sun Apr 9 13:38:26 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1507) scan finished
Sun Apr 9 13:38:29 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:866) Switching…
Sun Apr 9 13:38:29 2023 daemon.err lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:658) skip bss with dfs channel: CRUISE-NETWORK-NAME-REDACTED 40:E3:D6:57:55:91 52
Sun Apr 9 13:38:29 2023 daemon.err lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:658) skip bss with dfs channel: CRUISE-NETWORK-NAME-REDACTED 40:E3:D6:55:0A:31 116
Sun Apr 9 13:38:29 2023 daemon.err lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:658) skip bss with dfs channel: CRUISE-NETWORK-NAME-REDACTED 40:E3:D6:56:E5:31 100
Sun Apr 9 13:38:29 2023 daemon.err lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:658) skip bss with dfs channel: CRUISE-NETWORK-NAME-REDACTED 40:E3:D6:55:3E:31 64
Sun Apr 9 13:38:29 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1329) prepare connect ‘CRUISE-NETWORK-NAME-REDACTED(40:E3:D6:55:3E:21)’, None channel 11
Sun Apr 9 13:38:29 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1427) connecting ‘CRUISE-NETWORK-NAME-REDACTED 40:E3:D6:55:3E:21’…
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: Remove interface ‘wlan0’
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: wlan0: interface state ENABLED->DISABLED
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED be:80:d2:15:db:af
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: wlan0: AP-DISABLED
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sun Apr 9 13:38:29 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Apr 9 13:38:29 2023 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sun Apr 9 13:38:29 2023 kern.info kernel: [ 3692.686557] device wlan0 left promiscuous mode
Sun Apr 9 13:38:29 2023 kern.info kernel: [ 3692.691347] br-lan: port 3(wlan0) entered disabled state
Sun Apr 9 13:38:29 2023 daemon.notice netifd: bridge ‘br-lan’ link is down
Sun Apr 9 13:38:29 2023 daemon.notice netifd: Interface ‘lan’ has link connectivity loss
Sun Apr 9 13:38:29 2023 daemon.notice netifd: Network device ‘wlan0’ link is down
Sun Apr 9 13:38:30 2023 daemon.notice netifd: Wireless device ‘radio0’ is now down
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0-1) → new PHY
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.380431] br-lan: port 3(wlan0-1) entered blocking state
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.386062] br-lan: port 3(wlan0-1) entered disabled state
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.392562] device wlan0-1 entered promiscuous mode
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.398695] br-lan: port 3(wlan0-1) entered blocking state
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: wlan0-1: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.404400] br-lan: port 3(wlan0-1) entered forwarding state
Sun Apr 9 13:38:31 2023 kern.info kernel: [ 3694.420969] br-lan: port 3(wlan0-1) entered disabled state
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: wlan0-1: interface state COUNTRY_UPDATE->ENABLED
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: wlan0-1: AP-ENABLED
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:31 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.notice hostapd: handle_probe_req: send failed
Sun Apr 9 13:38:32 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:493) wait wpa_supplicant run…
Sun Apr 9 13:38:32 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:493) wait wpa_supplicant run…
Sun Apr 9 13:38:32 2023 daemon.notice netifd: Wireless device ‘radio0’ is now up
Sun Apr 9 13:38:34 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>CTRL-EVENT-SCAN-STARTED
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>CTRL-EVENT-SCAN-RESULTS
Sun Apr 9 13:38:35 2023 daemon.notice wpa_supplicant[2433]: wlan-sta0: SME: Trying to authenticate with 40:e3:d6:55:3e:21 (SSID=‘CRUISE-NETWORK-NAME-REDACTED’ freq=2462 MHz)
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>SME: Trying to authenticate with 40:e3:d6:55:3e:21 (SSID=‘CRUISE-NETWORK-NAME-REDACTED’ freq=2462 MHz)
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.880233] wlan-sta0: authenticate with 40:e3:d6:55:3e:21
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.887544] wlan-sta0: send auth to 40:e3:d6:55:3e:21 (try 1/3)
Sun Apr 9 13:38:35 2023 daemon.notice wpa_supplicant[2433]: wlan-sta0: Trying to associate with 40:e3:d6:55:3e:21 (SSID=‘CRUISE-NETWORK-NAME-REDACTED’ freq=2462 MHz)
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>Trying to associate with 40:e3:d6:55:3e:21 (SSID=‘CRUISE-NETWORK-NAME-REDACTED’ freq=2462 MHz)
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.895015] wlan-sta0: authenticated
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.903105] wlan-sta0: associate with 40:e3:d6:55:3e:21 (try 1/3)
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.919354] wlan-sta0: RX AssocResp from 40:e3:d6:55:3e:21 (capab=0x421 status=0 aid=2)
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3698.929602] wlan-sta0: associated
Sun Apr 9 13:38:35 2023 daemon.notice netifd: Network device ‘wlan-sta0’ link is up
Sun Apr 9 13:38:35 2023 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Sun Apr 9 13:38:35 2023 daemon.notice wpa_supplicant[2433]: wlan-sta0: Associated with 40:e3:d6:55:3e:21
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>Associated with 40:e3:d6:55:3e:21
Sun Apr 9 13:38:35 2023 daemon.notice wpa_supplicant[2433]: wlan-sta0: CTRL-EVENT-CONNECTED - Connection to 40:e3:d6:55:3e:21 completed [id=0 id_str=]
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>CTRL-EVENT-CONNECTED - Connection to 40:e3:d6:55:3e:21 completed [id=0 id_str=]
Sun Apr 9 13:38:35 2023 daemon.notice wpa_supplicant[2433]: wlan-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Apr 9 13:38:35 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:517) <3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Apr 9 13:38:35 2023 daemon.notice netifd: Network device ‘wlan0-1’ link is up
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3699.128824] br-lan: port 3(wlan0-1) entered blocking state
Sun Apr 9 13:38:35 2023 kern.info kernel: [ 3699.134405] br-lan: port 3(wlan0-1) entered forwarding state
Sun Apr 9 13:38:35 2023 daemon.notice netifd: bridge ‘br-lan’ link is up
Sun Apr 9 13:38:35 2023 daemon.notice netifd: Interface ‘lan’ has link connectivity
Sun Apr 9 13:38:38 2023 daemon.info lua: (…/ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1208) connected to ‘CRUISE-NETWORK-NAME-REDACTED(40:e3:d6:55:3e:21)’ channel: 11, spent 5s
Sun Apr 9 13:38:38 2023 daemon.notice netifd: Interface ‘wwan’ is enabled
Sun Apr 9 13:38:38 2023 daemon.notice netifd: Interface ‘wwan’ is setting up now
Sun Apr 9 13:38:38 2023 daemon.notice netifd: wwan (7091): udhcpc: started, v1.35.0
Sun Apr 9 13:38:38 2023 daemon.notice netifd: wwan (7091): udhcpc: broadcasting discover
Sun Apr 9 13:38:39 2023 daemon.notice netifd: wwan (7091): udhcpc: broadcasting select for 10.129.54.152, server 10.129.102.100
Sun Apr 9 13:38:39 2023 daemon.notice netifd: wwan (7091): udhcpc: lease of 10.129.54.152 obtained from 10.129.102.100, lease time 345600
Sun Apr 9 13:38:39 2023 daemon.notice netifd: Interface ‘wwan’ is now up
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using nameserver 10.129.103.22#53
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Sun Apr 9 13:38:39 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Sun Apr 9 13:38:40 2023 user.notice mwan3[7179]: Execute ifup event on interface wwan (wlan-sta0)
Sun Apr 9 13:38:41 2023 user.notice mwan3[7179]: Starting tracker on interface wwan (wlan-sta0)
Sun Apr 9 13:38:45 2023 user.info mwan3rtmon[4910]: Detect rtchange event.
Sun Apr 9 13:38:46 2023 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sun Apr 9 13:39:01 2023 daemon.notice hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:39:01 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:39:01 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 1)
Sun Apr 9 13:39:02 2023 daemon.notice hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:39:03 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:39:03 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 1)
Sun Apr 9 13:39:04 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:39:04 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 1)
Sun Apr 9 13:39:05 2023 daemon.notice hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: did not acknowledge authentication response
Sun Apr 9 13:39:05 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: authenticated
Sun Apr 9 13:39:05 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 IEEE 802.11: associated (aid 1)
Sun Apr 9 13:39:05 2023 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 60:57:18:c0:66:79
Sun Apr 9 13:39:05 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 RADIUS: starting accounting session B5F6BC351C6CF657
Sun Apr 9 13:39:05 2023 daemon.info hostapd: wlan0-1: STA 60:57:18:c0:66:79 WPA: pairwise key handshake completed (RSN)
Sun Apr 9 13:39:05 2023 daemon.notice hostapd: EAPOL-4WAY-HS-COMPLETED 60:57:18:c0:66:79
Sun Apr 9 13:39:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.8.218 60:57:18:c0:66:79
Sun Apr 9 13:39:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.8.218 60:57:18:c0:66:79 LAPTOP-NAME-REDACTED
Sun Apr 9 13:39:21 2023 user.notice mwan3[9210]: Execute ifdown event on interface wwan (wlan-sta0)
Sun Apr 9 13:39:22 2023 user.notice firewall: Reloading firewall due to ifdown of wwan (wlan-sta0)
Sun Apr 9 13:39:24 2023 user.info mwan3track[7625]: Detect ifdown event on interface wwan (wlan-sta0)
Sun Apr 9 13:39:29 2023 user.notice mwan3track[7625]: Interface wwan (wlan-sta0) is offline

Some thoughts about getting some Internet data. I kept the router connected and also connected my laptop directly to the cruise wifi. At that time the phone that was connected to the router got some new portion of the app notifications. But trying to use a browser on the phone or otherwise get something manually from the Internet was unsuccessful. Also, the wifi connection on the laptop connected to the cruise wifi got very unstable, it kept disconnecting randomly. I am assuming the router experienced the same thing. Once I disconnected the router from the wifi, direct connection to wifi on the laptop stabilized.

You seem to have already done a lot of troubleshooting, tweaking and experimenting. Sorry for not being able to help you there but of note that my firestick with its most primitive of networking settings can connect to host wifi networks much more easily than these so called “travel routers”. I would stop wasting my time and enjoy the holiday if I were you (and get a different router the next time).

1 Like

So this reads that cloning a ‘known good’ MAC to your Beryl might be worth a shot:

All of that was when the router already had a cloned good MAC. So essentially 2 devices with the same MAC were connected to the same cruise wifi. Nevertheless, when the laptop disconnects and only the router stays connected to the cruise wifi, it does not work

Well now you have me wondering if there isn’t something ‘just not quite right’ going on with the upstream Wi-Fi & the GL device. Can you do a site scan from a ‘known good’ connected device to the ship’s Wi-Fi? Eg:

Not sure if this is what you wanted to see… Survey feature is not included in the free version of Netspot

Here is another one from Xirrus…

So, presuming it is the right one for the hotspot/captive portal, the only BSSID with anything close to approp. SNR’s ‘Mode’ is reporting AC but uses the 2.4GHz band, Channel 11 (YMMV but I consider -70 dB to be about 50% signal quality).

Your screen shot is better than nothing but I’d expect anything truly Wi-Fi AC (aka Wi-Fi 5) to be above Channel 12 (eg: Ch 36, 56, 149, 162, etc.) comparing the survey of my neighbourhood via the afore-linked Wifi Analyzer. It shows the specific frequencies/SSID used (see its screenshots). I’m not how much of that would apply to Enterprise-class gear as found from Aruba Networks.

IDK; at this point I’d try to improve the quality of the signal for both SSIDs. That apparent ‘AC on 2.4G’ has me disconcerted, though.

EDIT: Yeah, those ‘Wi-Fi Modes’ of the second screenshot lead me to want to ensure I match as many of those specs for the Repeater’s 2.4 GHz radio.

Maybe we are talking about different things here… I am not trying to improve the signal quality. Just trying to connect more than one device I paid for :slight_smile: The router seems to connect to the ship wifi and can reach the gateway and what not just perfectly. The problem is that the traffic does not go anywhere, like something is blocking it. So I am wondering how to make the ship wifi believe my router is my laptop that is a “good” mac.

Yeah I get what you’re trying to set up but I was somewhat thinking the signal quality might be at play.

That should (ideally) just be a matter of a MAC Clone but you report that didn’t avail the issue. You also said DNS & VPN isn’t in play so I’m really not sure how much more I could personally offer for help.

Do you have a length of Ethernet to attempt Ship WLWAN → Repeater → LAN → Laptop?

Beyond that, all I got is & it may not even be related:

Unfortunately I do not have a cable with me.

Well this states cloning the MAC solves all issues, but that is not working for me. Of course I have a lot less time and budget for this little project than the whole cruiseline company, but the solution must be something stupidly simple…

It probably is but it seems I’m either too stupid or simple to further assist. I’ll bow out here.

Thanks for your help dude! Maybe I should really forget it and enjoy the holiday :slight_smile:

2 Likes

Enjoy your time on the boat.

Here is my thought::

The MAC Address of the access point of the boat is Aruba enterprise.

Companies are using software like Clearpass that can block mac address switching. It’s becoming harder to use portable routers.

The cloned MAC address needs to also match the IP address as well, try cloning both IP and MAC. BUT that still might not work as it also checks other items like OS, etc of the device. So if you have a windows machine, then the same MAC is used for a Linux machine, it won’t work as the profile is a mismatch.

So please enjoy your trip instead :slight_smile:

https://www.arubanetworks.com/techdocs/ClearPass/6.6/PolicyManager/Content/CPPM_UserGuide/Uses/UseCaseMACAuth.html

1 Like

I was recently camping on a farm and faced a similar problem with trying to use the Beryl AX as a repeater with no amount of MAC cloning, DNS changes…etc working at all and I could not believe that their system would have been sophisticated enough to block the router in the way you have described. Furthermore, trying a different make worked straight away and with no fuss at all leading me to the conclusion that there is undoubtedly an inherent issue with the GL.iNET’s abilities to repeat WiFi and/or deal with captive portal.

Yep; I may well be quite simple (note to self: read the damn logs!). Perhaps it’s a matter of disabling (ideally just adjusting the timeouts of) Multi-WAN tracking as the Repeater appears to handshake to the WLWAN but then drops connectivity some 13 seconds later:

Sun Apr 9 13:39:05 2023 daemon.notice hostapd: EAPOL-4WAY-HS-COMPLETED 60:57:18:c0:66:79
Sun Apr 9 13:39:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.8.218 60:57:18:c0:66:79
Sun Apr 9 13:39:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.8.218 60:57:18:c0:66:79 LAPTOP-NAME-REDACTED
Sun Apr 9 13:39:21 2023 user.notice mwan3[9210]: Execute ifdown event on interface wwan (wlan-sta0)

GL GUI → Network → Multi-WAN → Interface Status Tracking Method → Repeater → [gear icon(s)]

(I swear I’m bowing out now!)

What was the other make?

Good find, I skimmed the logs myself. I didn’t notice the mwan3. I don’t think that multi wan is enabled by default out of the box, is it?