It's not really needed to track the browser.
It is "easy" to detect NAT-ing devices like routers. And with "AI" it's just a job of a few CPU cycles.
You should be able to get around this using a VPN to mask content once you are able to connect. You might have to try several methods (wireguard, tailscale, openssl, ipsec) if they have something in place to block VPNs.
1 Like
Could you export the log?
Connected my phone, noted the mac address. This process has worked for me on MSC in the past, but not this time.
Interestingly in my case I was able to update the firmware to the latest beta when I manually set the router's mac address. However, nothing was being routed to client devices. I also was never able to get the GLinet to show the captive portal. Neither with the known working mac or a random mac.
They also were blocking my VPN and Tailscale connections both of which worked before but thats another topic. Anydesk did work this trip and was able to do what I needed to do on the remote device.
Hope this is helpful
logread.tar (151.5 KB)
Please show the file.
/var/log/gl-repeater/portal.html
What is this for? @FooBeard
@mudi-npc JerryZhao asked for a log.
@JerryZhao I'm not sure how you access that file in the UI. I'm guessing via SSH, but I don't see anything. Maybe it doesn't persist. In that case I don't have it any longer.
1 Like
All logs are flushed on reboot / power-loss.
I'm going to be on another MSC cruise next week and can send more logs. The logread.tar was the ui exported logs from when the issue was occurring. I didn't know there were additional logs via ssh.
The tar file is mostly fine.
New logfiles.
logread.tar (183 KB)
First, I'm just tried to get the portal to get routed to my laptop. If I curl from the router itself, it connects fine.
Some ping tests and curl test from my laptop
same tests direct from router (over ssh)
portal.html
Went ahead and logged in with my phone, then spoofed the mac on my laptop, which works just like it did before.
3 Likes
Bump! Facing same problems
1 Like
Interested in the resolution of this
2 Likes
Did you get the router to work as repeater?
I am going on MSC Grandiosa in a week and I need to get this working. I am ready to provide more logs etc if GL-Inet staff wants to look into this. I will be onboard for 21 days (Genoa to Santos)
1 Like
1 Like
Sounds good. I'm on an MSC Cruise Ship over NewYear. I'm using GL-MT3000 Beryl AX with op24 firmware. If there is anything i can test, let me know.
Sure, please let me know when you on MSC and the GL router repeater portal does not work.
1 Like
I am on an MSC cruise ship now and i was able to connect without a problem with version 4.7.0-op24.
2 Likes
@buntspext What options did you use to connect to the MSC wifi? I see several options that don't really have an explanation (e.g., "Enable Disguide", "Lock BSSID", etc). Did you have to clone your device MAC first?
I'm heading on an MSC Sea* cruise next week - hopefully can get this to work! Thank you!
1 Like