GL sft1200 opal on MSC cruise

I was in several groups that recommended this travel router for cruises, and I wanted to know if there are any other options I should consider because, despite having intermediate/advanced knowledge, I haven't been able to get it to work. It also seems that in the last 4-5 months, no one has reported being able to make it work, so perhaps it’s no longer useful for this purpose...

The first thing I did was disable MAC randomization on the iPhone, turn off auto-join, and not hide the IP. That is, on the iPhone, I kept the same IP, the same MAC without hiding it.

I cloned the MAC on the router and connected it, but the captive portal doesn’t appear (although it's not mandatory), and I can’t browse the internet.

I then decided to copy all the properties to the router when connecting it, such as IP, mask, and DNS, but with the same result.

I accessed the firewall and modified the TTL as several people here suggested, to 65 or 64, but still no results. I don’t have DNS override or anything similar enabled.

Any suggestions? If not, we should notify the cruise groups that recommended purchasing it, as it’s currently useless

If your Opal cannot open the captive portal, please export the syslog and PM me.

The forum is for discussion and feedback. If the portal is available, users will not go to the forum to post a thread to show.

The network facilities and technology behind each portal WiFi may be different, so would you like to help us troubleshoot?

Have you tried both of these methods?

Yeah i tried both methods.

  1. Clone only MAC, all automatic , didnt work
  2. Clone MAC, static IP, gateway, DNS, si mask, didnt work.

I am going onboard MSC Grandiosa next week on the 16th. I will post here if I am able to connect my Mudi to the ship wifi as repeater. If there are any issues it would be really nice if GL-Inet staff could look into it. I will be on the cruise for 21 days so we have plenty of time to work this out for everybody.

2 Likes

Hello,

I am now onboard MSC Grandiosa and I have bad news.

I have tried to connect Mudi to the ship Wifi, but I cannot get the captive portal to pop up.
I hope support could help this figure out during the next 21 days I am onboard so all other can benefit in the future. I can send whatever logs etc you want, just tell me what you want me to do.

Whatever I try to do I cannot get the captive portal to pop up.. I am techincally advanced and I know what I am doing but I cannot figure this out.

I have a Mac with me and a iPhone. I have connected my phone to the ship network succesfully.

  1. I have tried normally just joining the wifi network with the repeater setting and Mudi connects to the Wifi, gets IP etc but captive portal won't pop up. I have tried going to neverssl.com, stright to the wifi gateway IP and login.mscwifi.com and mscwifi.com but nothing pops up on the laptop
  2. I took note of the IP address which my phone got form the wifi and the wifi was working. I set the MAC address to match my phone MAC address and also set all the IP addreses the same as my phone had while connected to the network. I disconnected my phone from the network and tried joining with my Mudi, it connects to the network but internet doesn't work.
1 Like

Hi,

Thanks for your update.

  1. Please share us the syslog which the router connects (try connecting) MSC WIFI.
  2. Did you have another network source for router connect to the Internet (MSC WiFi for debugging), and bind the router to GoodCloud, share it with us?
    Technical support via GoodCloud - GL.iNet Router Docs 4

Purely theoretically, you can try to use this script:

It bypasses captive portals. I think it should be modified to work on OpenWRT, but on Linux it is working perfectly in nearly all cases.

@admon, can you take a look on it?

Hello Bruce,

thanks for your reply and willingness to help.

Quick reply for your questions:

  1. You can find the log below
  2. Yes I have a second internet source but I need to be in port so I can use it. There is no 4G/3G signal while we are at sea.

I decided to reset my Mudi v1 completely so all the settings are factory default to make your troubleshooting easier.
I have only done the following changes:

  • Set time zone
  • I have a sim card (from Finland) (Roaming) and I did auto setup to be able to have internet
  • Enabled GoodCloud

--> After doing these changes I rebooted the device and tried to connect to MSC Hotspot
The hotspot name is MSCGRANDIOSA-HOTSPOT
--> You can find this log with name FIRST logread.tar

--> After this I decided to disconnect my modem from the network and also disconnected from repeater
--> While keeping my modem in disconnected state, I tried to connect again to MSCGRANDIOSA-HOTSPOT --> You can find this log with name SECOND logread.tar

I cannot get the captive portal to pop up in any way I try, like:

  • I have also tried earlier (Yesterday and the day before) giving Mudi same MAC address as my phone which I have succesfully connected to the network and logged in but there is no Internet traffic going through Mudi (When connecting Mudi to ship network, I have of course disabled the Wifi on my phone so the Mac address is not already connected to the ship wifi)

I have set up Goodcloud and shared access for user gl.inet_support (My device serial is: cd13e00b79778e3d)
I am currently in Barcelona with MSC Grandiosa, we have a sea day tomorrow
It is a bit hard to have mobile signals during sea days so you could connect to my device but I am willing to agree on time when you could troubleshoot the device and I can go outside on deck so the device has mobile signal and you can connect. What are your working hours in UTC?
Maybe we can arrange a time on 20th on November when the ship is in port in Malaga.

Let me know if you need root password or something else.

Firwmware info:
Current Firmware

Version 4.0

Firmware Type 0319release3

Compile Time 2024-09-06 8:58:20(UTC+08:00)
SECOND logread.tar (194.5 KB)
FIRST logread.tar (188 KB)

Thank you, slebu.

I am in UTC+8, and 9:00 AM. later at work.

  1. I have viewed and checked the 2 syslog you provided, there is not any exception to found. The repeater connection process, repeater interface, IP, DNS, they are normal, why the client devices (laptop/phone) cannot open the portal page, have to further check.

  2. When you have second Internet source, please message me, I would like to remote check via the remote software Anydesk, use WireShark in laptop to capture the network packets when the router connects to portal WiFi and access the portal page in the laptop.

Do you have a laptop?
Please follow this topology figure to deploy the debug environment, and please PM me your router root password, remote desktop ID.

Hello Bruce,

thank you for your reply.

Just a heads up that I currently have a 4G signal on Mudi and at the moment you can access the device remotely using GoodCloud. If you can do any debugging now by using Goodcloud, I would appericate it. I will DM you my root password.

I can set up the environment you provided an image of later today or tomorrow. I will get back to you.

Thank you. Received password.



Shows there is not Internet, but in the SSH test the interface ICMP work ok, I think also need the remote desktop to confirm...

May I know what time range is available?

Hello,

I will have the test environment setup for you for two hour window tomorrow. I hope this works out to you :slight_smile: Spain time 8:30 to 10:30 - So 15:30 to 17:30 UTC +8 time. I will get back to you privately with Anydesk ID around 8:30 Spanish time tomorrow. I have installed Wireshark for you, it is tha MAC ARM version.

I am not 100% sure but as you used -I and specified the router IP address (10.132.59.87) as the interface --> The ping packstes went through the 4G modem which was connected to the router and no data went through the repeater.

Br, Samuli

1 Like

Thank you.

The time windows work out for me.

Yes, I am also not pretty sure that ICMP traffic went through the repeater or not.

I'll be waiting for your message at Spain time 8:30 tomorrow.

Hello, I have sent you the Anydesk ID in private.
The test environment is ready for you.

Br, Samuli

1 Like

Hello @bruce

I am currently aboard MSC Seaside and unable to get captive portal to show using repeater mode on my Opal 1200. I will be on board for 8 days and able to provide remote access on some of those days. Can you give any insight on how you were able to solve the issue?

Thanks!

Hi,

This issue we are resolved and will update the codes.

Please try these commands in the SSH of router to temporary use:

mkdir -p /usr/share/nftables.d/chain-pre/mangle_prerouting
echo 'iifname wlan-sta0 counter ip ttl set 64' > /usr/share/nftables.d/chain-pre/mangle_prerouting/01-set-ttl-portal.nft
/etc/init.d/firewall reload

If the above operation still doesn't work, please execute the following command after repeater connected.

iptables -t mangle -A PREROUTING -i wlan-sta0 -j TTL --ttl-set 64

Some uses nft as the firewall feature, and some are iptables. In addition, different models, different band, relay interface name is also different, so it is not easy to provide temporary commands. Please wait for our new firmware if you cannot use the SSH debugging.

Hi all,

The GL R&D team, PM team, and support team would like to publicly thanks to the user @slebu.

During his trip on the MSC, he spends valuable travel time and cooperated with us, which helping us to manually capture the network packages by himself over 6 times according to our steps and requirements.

Why cannot remote capture the network packages?
Because when we can access remote the laptop desktop, the default route of the laptop is directly to the gateway which is available to the Internet (like phone USB sharing, or others WiFi), but not Laptop -> E750 -> MSC, thus we cannot capture the packages from laptop browser -> GL router with repeater -> MSC.

The total number of messages exceeded 100 in these 20 days, always very professional, meticulous and helpful. He even had some accidents his phone was robbed during his personal trip. Fortunately safety to back to the ship, and his emotions were very stable. He still continued to contact with GL, and he completed packet capture step by step. Also synchronization records the screen and the operation to prevent any steps from being missed. Therefore, more than 1GB of files we are received each time.

GL Will send an GL router as a gift, and we would like to thank you again to help us to resolve this important issue @slebu.

At the same time, we are very grateful to all forum users who like GL products and providing us with many suggestions to make GL products better, more user-friendly, and more powerful.
This is our team mission and responsibility to listen voice from user and resolve the issue.

We wish all users and all friends a Merry Christmas and a Happy 2025!

10 Likes

I would like to add my thanks for all involved in this very helpful thread.

For me two matters arise:

  1. Why didn’t the existing GLINET setting for TTL work?

  2. It seems a matter of time before IPV6 HL is exploited to block travel routers in the same way. If GLINET firmware is to be fixed for TTL should it be fixed for HL also?

1 Like

Well done, @slebu !

The likelihood of me ever going on a cruise is somewhere between zero and none, but you've done a great service for the community!

Thanks.

2 Likes

At present the GL firmware supported to set the TTL of network outbound packets.

The above issue is the TTL of the inbound package.

IPv4 is the basis for Internet access. Thank you, we will be observing the HL.