# PSA to GL.iNet regarding Cruise ships

**URL:** <https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219>\
**Category:** Router\
**Created:** [May 13, 2024, 2:45pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219 "2024-05-13T14:45:02Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![KalEl](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/kalel/32/17269_2.png) [@KalEl](https://forum.gl-inet.com/u/KalEl)\
**Post date:** [May 13, 2024, 2:45pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/1 "2024-05-13T14:45:02Z")

</div>

For GL.iNet… I’m sure you guys see the huge issue of Cruise Ships (esp. MSC) figuring out how to block Travel Routers.

At least over the last few months there are tons of post online regarding this major issue.

People have tried everything in terms of a networking solution and it doesn’t work.

I think the manufacturers have to figure this out.  
Since one of the major use case for these products is the ability to use them at hotel and cruise ships to avoid this exact issue, it is in their best interest.

Please guys, I love the products… But if they don’t work… No reason to recommend or use anymore.

---

<div class="post-metadata">

**Author:** ![maholio](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/9f8e36/32.png) [@maholio](https://forum.gl-inet.com/u/maholio)\
**Post date:** [May 13, 2024, 2:56pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/2 "2024-05-13T14:56:51Z")

</div>

Look at my post please 🙂

> [@Using GLinet Opal on MSC Cruise](https://forum.gl-inet.com/t/using-glinet-opal-on-msc-cruise/39814/6):
>
> Maybe your devices (phones) uses MAC randomisation. When you connect to new WiFi new MAC generated. If you connect to your GL router and use “clone” option your router clones another MAC. Solution: Use “Custom” option and enter MAC from menu with main network you are connecting to. On many devices it can be seen by click on main network to which you want to connect router. Try this out. Hope it will help!

---

<div class="post-metadata">

**Author:** ![KalEl](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/kalel/32/17269_2.png) [@KalEl](https://forum.gl-inet.com/u/KalEl)\
**Post date:** [May 13, 2024, 3:31pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/3 "2024-05-13T15:31:19Z")

</div>

I appreciate it… Yeah I made sure I was using my Phone MAC… not private/randomization

---

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [May 13, 2024, 4:03pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/4 "2024-05-13T16:03:52Z")

</div>

To be honest, I highly doubt that they “find out” how to block devices like Travel routers. It’s nearly impossible (at least very difficult) to detect NATting devices.

One big issue is that testing this requires at least a holiday on a cruise ship. 😃  
I could imagine that they detect TTL changes and setting a correct TTL might solve the mystery already. But it’s hard to say from my side, sitting in front of a PC 1000km away from any cruise ship.

> [@KalEl](#):
>
> People have tried everything in terms of a networking solution and it doesn’t work.

Nah, people tried only the stuff you can reach by pressing a button. Nothing of this was like _everything in terms of networking_

---

<div class="post-metadata">

**Author:** ![packetmonkey](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/packetmonkey/32/16711_2.png) [@packetmonkey](https://forum.gl-inet.com/u/packetmonkey)\
**Post date:** [May 13, 2024, 5:04pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/5 "2024-05-13T17:04:27Z")

</div>

> [@admon](#):
>
> To be honest, I highly doubt that they “find out” how to block devices like Travel routers. It’s nearly impossible (at least very difficult) to detect NATting devices.

I will disagree with this one a little. User-agent in browsers often give away client information. For instance, if you clone an iPhone MAC address, and they see a UA string showing a Windows machine running Firefox, that could be an indicator of misuse. And all it takes is injecting an http tracker or even perhaps a cookie, that notifies them of the UA.

There are ways around that, but most folks are not going to do that. This is where using a VPN behind the router may help out so that the internet provider does not get a clear look at the UA passing through it.

---

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [May 13, 2024, 5:16pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/6 "2024-05-13T17:16:57Z")

</div>

> [@packetmonkey](#):
>
> And all it takes is injecting an http tracker or even perhaps a cookie, that notifies them of the UA.

If the operators do something like this, it’s best to forget about the WLAN. It’s almost like an integrated Trojan. The only thing missing is that you have to accept a CA certificate so that they can read all the traffic.

---

<div class="post-metadata">

**Author:** ![packetmonkey](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/packetmonkey/32/16711_2.png) [@packetmonkey](https://forum.gl-inet.com/u/packetmonkey)\
**Post date:** [May 13, 2024, 5:51pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/7 "2024-05-13T17:51:36Z")

</div>

It isn’t all that nefarious, though. Most websites do this nowadays, they use pixel tracking or some other method to try to track you. Not saying it is desirable, but it is happening almost everywhere you browse. Cruise lines stand to lose a lot of money if folks are using travel routers, and to that end, I expect they will do whatever they can to try to prevent their use.

---

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [May 13, 2024, 6:06pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/8 "2024-05-13T18:06:06Z")

</div>

> [@packetmonkey](#):
>
> Cruise lines stand to lose a lot of money if folks are using travel routers,

Poor cruise line companies. We should start a fundraising campaign 🤑

---

<div class="post-metadata">

**Author:** ![maholio](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/9f8e36/32.png) [@maholio](https://forum.gl-inet.com/u/maholio)\
**Post date:** [May 13, 2024, 6:42pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/9 "2024-05-13T18:42:19Z")

</div>

After some testing (via virtual machine with DPI) this should help:

1. Change your User Agent to your actual user agent of your phone.

- Use [this](https://whatmyuseragent.com) website to check your user agent
- Use [this](https://addons.mozilla.org/en-US/firefox/addon/random_user_agent/) addon (with custom mode) to change User Agent

1. It is better hide your referer via [this](https://addons.mozilla.org/en-US/firefox/addon/referer-modifier/) addon
2. Change TTL to 64.

- Login via SSH and run `nano /etc/config/firewall`
- Add this:

```auto
config rule
        option name 'Set TTL to 64'
        option src 'wan'
        option proto 'ip'
        option target 'ACCEPT'
        option ttl '64'

```

## Important information:

- Save copy of configuration before editing it
- It is tested using DPI on virtual machine. I cannot guarantee that this will work in your case.

## If not worked:

- Try to use VPN directly on router
- Try ProtonVPN on phone connected to router with “Stealth” mode or “WebTunnel” bridge in Tor
- Your phone must be disconnected from main WiFi before connecting it to router

P.S: No, I can’t share DPI config. Personal reasons, sorry.

---

<div class="post-metadata">

**Author:** ![KalEl](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/kalel/32/17269_2.png) [@KalEl](https://forum.gl-inet.com/u/KalEl)\
**Post date:** [May 13, 2024, 7:11pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/10 "2024-05-13T19:11:00Z")

</div>

True… Agree with that point

---

<div class="post-metadata">

**Author:** ![9b9e69c2-4b75-4420](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/9/a587f6/32.png) [@9b9e69c2-4b75-4420](https://forum.gl-inet.com/u/9b9e69c2-4b75-4420)\
**Post date:** [July 22, 2025, 8:52pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/11 "2025-07-22T20:52:23Z")

</div>

> [@maholio](#):
>
> `Set TTL to 64`

Here's the corresponding `uci` commands. No `nano`/text editing needed:

```auto
uci batch <<- __EOF
	add firewall rule
	rename firewall.@rule[-1]='custom_ttl'
	set firewall.custom_ttl.name='Set TTL to 64'
	set firewall.custom_ttl.src='wan'
	set firewall.custom_ttl.proto='ip'
	set firewall.custom_ttl.target='ACCEPT'
	set firewall.custom_ttl.ttl='64'
	reorder firewall.custom_ttl='1'
	set firewall.custom_ttl.enabled='1'
__EOF
uci commit firewall && service firewall restart

```

It also bumps the rule to the top of the firewall chain (via `reorder`).

```auto
uci set firewall.custom_ttl.enabled='0' && \
uci commit firewall && service firewall restart

```

... will disable it.

> [@maholio](#):
>
> Save copy of configuration before editing it

Excellent point. See the below link. One should always have a backup:

> [@Issue resolving hosts by name](https://forum.gl-inet.com/t/issue-resolving-hosts-by-name/61547/7):
>
> Weird. I hate to say it but I'd nuke it all & start over. It ain't much but here's something handy to help save states as you build up a clean config: #!/bin/sh HOST="$(uci show system.@system[0].hostname | cut -d "'" -f '2')" DOMAIN="$(uci show dhcp.@dnsmasq[0].domain | cut -d "'" -f '2')" timestamp="$(env TZ=UTC date +'%Y%m%dT%H%M%Z')" sysupgrade --create-backup /tmp/backup-"${HOST}"."${DOMAIN}"-"${timestamp}".tar.gz exit 0 Throw that into a script file & run it as a check point any time …

---

<div class="post-metadata">

**Author:** ![9b9e69c2-4b75-4420](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/9/a587f6/32.png) [@9b9e69c2-4b75-4420](https://forum.gl-inet.com/u/9b9e69c2-4b75-4420)\
**Post date:** [July 22, 2025, 9:12pm UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/12 "2025-07-22T21:12:31Z")

</div>

Line go up. /s

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [November 5, 2025, 9:34am UTC](https://forum.gl-inet.com/t/psa-to-gl-inet-regarding-cruise-ships/42219/13 "2025-11-05T09:34:30Z")

</div>