The Secret to Cheaper Cruise Wi-Fi with a GL.iNet Travel Router — Updated for 2026
Updated: Sep 2
A few years ago, my family and I took an Alaska cruise.
Great trip.
Beautiful scenery.
Icebergs. Mountains. All of that.
Then I looked at the price of the internet.
Man.
The Wi-Fi package started at around $179 per device for the week. Between my wife, my daughter and me, we had about five devices we wanted to use.
Phones. iPads. Computers. You know how this goes.
Depending on how many devices we wanted connected, that internet bill could get ridiculous pretty quickly.
So, of course, I started looking at the network.
Because that's what I do.
And that little GL.iNet travel router I had with me ended up being one of the most useful pieces of equipment I packed for the entire trip.
But there is something important you need to know before you follow the exact process I used back then.
The way GL.iNet handles captive portals has gotten easier.
So let me explain what I did, what has changed, and what I would do today.
First, What Is a Captive Portal?
You've used one even if you didn't know what it was called.
You connect to Wi-Fi at a hotel, airport, Starbucks, cruise ship, maybe a hospital. Your phone says it's connected to Wi-Fi, but you still don't have internet.
Then a page pops up asking you to agree to some terms, enter your room number, type in an email address, pay for access, or otherwise authenticate yourself.
That page is the captive portal.
Think of it as the gatekeeper between the local Wi-Fi network and the actual internet. Until you get through that gate, you don't really have internet access.
Simple enough.
Where things get interesting is when you add a travel router.
Why I Wanted the Travel Router on the Cruise
I didn't want to configure every device separately.
I wanted my devices connected to my router. Then I wanted my router connected to the cruise ship's Wi-Fi.
That way, my phones, tablets and computers could stay connected to a network I controlled while the travel router handled the connection to the ship.
That is one of the reasons I've used GL.iNet travel routers for years. They give you a lot of flexibility when you're dealing with hotel, airport, cruise-ship and other public Wi-Fi.
On that Alaska cruise, though, getting through the captive portal required a little more work.
Okay.
A lot more work.
The Way I Did It in 2024
The cruise network remembered the device that had authenticated to the network. I first got one device online, then used the GL.iNet router's advanced networking tools to make the router work with that connection.
That involved MAC-address handling and, in my case, manually working with network information from the authenticated device.
Once everything was correct, the router got internet access. Then the devices behind my router could use that connection.
And because my Personal VPN was configured on the travel router, once the router got online it established the VPN connection back to my server in Atlanta.
So there I was.
Sailing through Alaska.
Connected to cruise ship Wi-Fi, with my devices sitting behind my travel router and my Personal VPN running back through Atlanta.
It worked.
But I'm going to tell you right now:
That was expert mode.
You Probably Don't Need to Start There Anymore
This is the part of the original article that needs updating.
Newer GL.iNet firmware has made connecting to captive portals much easier.
If you're using a current GL.iNet router and current firmware, there are now built-in tools designed to help you get through public-hotspot login pages without immediately jumping into the kind of manual networking work I had to do on that Alaska cruise.
That's a big improvement.
And it changes how I would teach this today.
The first thing I tell people now is: start with the normal captive-portal process.
If that works, you're done.
There is no prize for making networking harder than it needs to be.
Personal VPN Users Have an Extra Consideration
If you're using one of the Personal VPN systems I set up, your starting point is a little different.
Those systems include protections designed to make sure your traffic behaves the way we intended when the VPN is in use.
The problem is that a captive portal has to be reached before the VPN can do its job.
So there is a specific order of operations that matters when a Personal VPN user connects at a hotel, airport, cruise ship, or other public network.
That process is different from what a regular GL.iNet owner would follow.
Same router.
Different starting point.
And that's one of the reasons I maintain a separate step-by-step guide instead of trying to cram every possible configuration into an article like this.
So What About MAC Cloning?
MAC cloning is still useful.
I just no longer treat it as the first thing everybody should try.
If the normal captive-portal process doesn't work, that's when we may have to look deeper at how the network is identifying your device.
That can involve MAC addresses, private or randomized Wi-Fi addresses, MAC cloning, manual network settings, and other troubleshooting.
Those tools haven't disappeared.
They've moved further down the troubleshooting ladder.
The process I used on the Alaska cruise still matters. It just isn't where I would tell everybody to start today.
One More Thing About Private Wi-Fi Addresses
Apple and Android devices can use changing or private MAC addresses as a privacy feature.
That can become relevant when a public Wi-Fi system is trying to remember a particular authenticated device.
In the older process I used, this was a much bigger part of the setup.
Today I treat it as something to investigate when a captive portal isn't behaving the way I expect—not something every traveler should automatically go change.
Again: simple first. Troubleshoot only when necessary.
Cruise Ships Have Changed Too
There is another reason I don't want to oversell the original trick.
Cruise lines have changed their Wi-Fi systems and policies over the years.
So I would not buy a travel router today with the assumption that you are definitely going to buy one device package and share it with everybody in your cabin.
Maybe your particular ship and package will allow the setup you want.
Maybe it won't.
Policies change. Technology changes. The way devices are counted can change. And the cruise line gets to make the rules for its network.
What I can tell you is that a GL.iNet travel router remains one of the most useful tools I carry when I'm dealing with public Wi-Fi—not just cruises, but hotels, airports, coffee shops, and other places where I want more control over how my devices connect.
The Bigger Benefit Isn't Just Saving Money
The original reason I made the video was saving money on cruise Wi-Fi.
And yes, that got my attention.
But after using these routers for years, the bigger benefit for me is control.
I can connect my devices to the same network I know. I can manage the connection in one place. I can run my Personal VPN from the router when appropriate. And I can troubleshoot one router instead of five different devices.
When I move from a hotel to an airport to a cruise ship, my devices don't have to know anything changed. They stay connected to my travel router. The router deals with everything upstream.
That is a big part of why I still use them.
What I Would Do Today
If I walked onto a cruise ship tomorrow with my current GL.iNet router, I would not immediately start duplicating everything I did in 2024.
I'd start with the current captive-portal tools built into the router.
If it works?
Done.
Go enjoy the ship.
If it doesn't work, then I start asking questions.
Is the captive portal actually loading? Is something in my VPN configuration affecting the login process? Is the network remembering a specific device? Is the problem related to the way the network identifies my hardware? Do I need to move into the more advanced troubleshooting process?
That's the progression.
Simple first. Expert mode when necessary.
Need the Step-by-Step Process?
If you're sitting in a hotel room, airport or cruise cabin trying to figure all of this out, I realize knowing why it works isn't necessarily enough.
You probably want to know what to click, what you should expect to see, what to try if the normal method doesn't work, and what changes if you're using a Personal VPN.
That's exactly why I created my Captive Portal Guide.
The article explains the problem.
The guide walks you through the process.
It covers the current connection method as well as the troubleshooting path when the simple approach isn't enough.
And if you need broader help understanding your GL.iNet router or Personal VPN system, that's where my Personal VPN training and support come in.
The Bottom Line
That GL.iNet travel router absolutely saved the day for me on our Alaska cruise.
The story hasn't changed.
The technology has.
What I did back then worked, but today I would start with the easier captive-portal tools built into newer GL.iNet firmware and only move into MAC cloning and manual network configuration when I need them.
That's actually good news.
Because the goal isn't to become a network engineer every time you check into a hotel.
The goal is to get connected.
And then go do whatever you actually traveled there to do.
Until next time,
MexitPlans Monte
“I'm Out.”
Comments