Setting up a GL.iNet travel router: VPN, DNS and guest network

A GL.iNet router comes with OpenWrt and its own admin panel. This guide sets up a VPN for all your devices, encrypted DNS, DNS filtering and a separate guest network.

Setting up a GL.iNet travel router: VPN, DNS and guest network

Setting up a GL.iNet travel router: VPN, DNS and guest network

A GL.iNet router comes with OpenWrt and its own admin panel. This guide sets up a VPN for all your devices, encrypted DNS, DNS filtering and a separate guest network.

Who this guide is for: Anyone who has or is considering a GL.iNet router — as a travel router for hotels and public networks, or at home as a more privacy-friendly replacement for a basic ISP router.

A GL.iNet router comes with OpenWrt pre-installed and its own admin panel. After basic setup you have a VPN connection that works for all connected devices, encrypted DNS, DNS filtering and an isolated guest network.

This guide works for GL.iNet models on the 4.x firmware: Beryl AX (MT3000), Flint 2 (MT6000), Slate 7, Brume 3 and others. The settings are the same, but some menus moved between firmware versions, and not every model gets the newest version at the same time (stable versions in November 2026: 4.11 on the Beryl AX and Flint 2; 4.10 on the Slate 7, Mudi 7 and Flint 3; 4.9 on the Beryl 7, Brume 3 and Flint 4; 4.8 on the Slate 7 Pro and Puli AX; 4.7 on the Brume 2 and Spitz Plus). The steps follow 4.11; where a menu moved or a setting differs, each step says so. Your version is under System → Upgrade (Current Firmware).

Already have a setup? Nothing below needs a reset: skip to the steps you are missing. The only step that can cut devices off is the stricter VPN option in step 3; switch it on last, once the VPN works.

What you gain, and what it costs

You gain central control. Instead of configuring VPN, DNS filtering, or guest access on every device separately, you do it once on the router and everything behind it benefits. That is especially useful while travelling or in homes with lots of devices.

The cost is extra management. You are adding a network layer you have to understand, update, and troubleshoot when something breaks. A badly configured router can also make it harder to tell where your traffic is really going.

When this is overkill

If you only want to protect your own laptop and phone on public Wi-Fi, a normal VPN app may be enough. A GL.iNet router becomes more worthwhile when you want this for multiple devices, want to enforce a guest network, or want more control at home than your ISP router gives you.


What you need

  • A GL.iNet router
  • A laptop or phone to configure it
  • A VPN subscription with WireGuard support (Mullvad, ProtonVPN or your own server)
  • About 30 minutes

Step 1 — First connection

Plug the router into power. Connect your laptop or phone via wifi to the network the router broadcasts — the name is on the bottom of the device, along with the default wifi password. The Brume 2 and Brume 3 have no wifi: connect by cable, and skip the wifi parts of this guide.

Open a browser and go to:

192.168.8.1

You’ll see the GL.iNet admin interface. Set a strong admin password. Store it in your password manager.


Step 2 — Internet connection

As a travel router (hotel, Airbnb, office):

Go to Internet and, under Repeater, open the list of nearby networks (Join Network). Select the wifi network at the location and enter its password. The router connects and shares the connection.

All devices you connect to the GL.iNet router afterwards go through this connection — with all the settings you configure below.

At home:

Connect the WAN port to your existing router or modem via a network cable. The GL.iNet router then works as a second router behind your first.


Step 3 — Set up VPN (WireGuard)

This is the most important step. Once configured, all traffic from all connected devices automatically goes through VPN — without configuring anything per device.

It takes two places in the admin panel: you add the configuration file under VPN → VPN Client Profile (on firmware before 4.9: VPN → WireGuard Client), and you start it in VPN → VPN Dashboard.

Get a configuration file from your provider:

  • Mullvad: log in at mullvad.net, open the WireGuard configuration file generator, choose your platform (Mullvad’s own router guide uses Linux), click Generate key, pick a server (nearest to you) and click Download file.
  • ProtonVPN: sign in at account.protonvpn.com and go to Downloads → WireGuard configuration. Give the configuration a name, choose a platform and a server, click Create, then Download.
  • Your own WireGuard server: export the client configuration from your server.

Add it to the router:

  1. Go to VPN → VPN Client Profile, choose WireGuard at the top and add your configuration (Upload Configuration File for a .conf file)
  2. Go to VPN → VPN Dashboard and click Add VPN Tunnel. Select that configuration, choose All Clients as the source and All Targets as the destination, then Apply. Any other choice leaves some traffic outside the VPN. The screens differ before 4.9, but the same two choices count
  3. Check that Kill Switch is on in the tunnel’s options (see below), then switch the tunnel on

Check that VPN is active: Go to ip.me from a connected device. The IP address should match the VPN server, not your own internet connection.

Kill switch: Since firmware 4.8 every VPN tunnel has a Kill Switch setting, on by default for a new tunnel: if the tunnel drops, its traffic is blocked instead of going out unprotected. With it off, that traffic falls back to the normal connection. On 4.7 firmware there is no per-tunnel switch, and the one that exists, Block Non-VPN Traffic, is off by default: switch it on once the VPN works.

A tunnel that is switched off protects nothing: by default (Allow Non-VPN Traffic), traffic then goes out over the normal connection. For a stricter setup, go to All Other Traffic in the VPN Dashboard and choose Enhanced Kill Switch instead: then nothing reaches the internet outside a VPN tunnel. Do this last, once the VPN works, or your devices lose internet while you are still setting up.


Step 4 — DNS-over-TLS

Without encrypted DNS, DNS requests often still travel in readable form over the local network or to the router’s upstream resolver. With DNS-over-TLS they are sent encrypted.

Whether this also applies to traffic through the VPN depends on one switch on the same page: Apply Manual DNS to VPN tunnels on 4.11, Allow Custom DNS to Override VPN DNS before that. Off: VPN traffic uses your VPN provider’s DNS, and the setting below covers everything outside the VPN. On: the DNS you set here is used for VPN traffic too. The default differs per firmware (on in 4.7, off in 4.11), so check it.

Go to DNS (a menu of its own since firmware 4.11; before that, Network → DNS).

Enable DNS Rebinding Attack Protection, which is off by default (on 4.11 it is under Options, at the top of the page). GL.iNet warns that it can get in the way of hotel and airport login pages; switch it off if one won’t load.

On 4.11 the page has separate cards for WAN DNS, VPN DNS and Manual DNS. Enable the Manual DNS card, set Type to Encrypted DNS, pick a DNS Provider and click Apply. Before 4.11, choose Encrypted DNS as the mode and pick a provider:

Provider How to choose it Blocks malware?
Quad9 In the provider list Yes
Cloudflare In the provider list No (privacy only)

Quad9 is the recommended choice: blocks known malware domains, records no IP addresses, based in Switzerland. Set up Mullvad DNS under Manual earlier? Mullvad set 2 November 2026 as its end date; switch to Quad9. Travelling to France? Quad9 stops serving users there on 24 November 2026; pick another resolver for that trip (see the DNS guide).

On firmware 4.8 and earlier (Slate 7 Pro and Brume 2, for example) the DNS over TLS list only has Control D, NextDNS and Cloudflare, and there is no manual entry for an encrypted server. To use Quad9 encrypted there, set it in AdGuard Home (step 5).

If you install AdGuard Home (step 5), configure DNS-over-TLS there instead of here.


AdGuard Home is a DNS filtering tool that blocks ads, trackers and malware domains for all devices on your network. It runs directly on the router.

Go to Applications → AdGuard Home and switch on AdGuard Home. It comes with the firmware; there is nothing to install. Leave Apply AdGuard Home to VPN tunnels on (the default), so traffic through the VPN is filtered too.

Then open AdGuard Home’s own interface via the Settings Page link (port 3000).

No separate login (our reading): firmware 4.11 ships AdGuard Home with an empty user list, but GL.iNet starts it in AdGuard Home’s GL.iNet mode (--glinet). In that mode AdGuard Home only lets in a browser that is logged in to the router and sends others to the router’s own login page. That is our reading of the firmware and AdGuard Home’s source; we haven’t tested it on a device. So your router’s admin password also guards your filtering: keep it strong, and keep visitors on the guest network.

Set DNS in AdGuard Home: Go to Settings → DNS settings → Upstream DNS servers. GL.iNet’s default there is 8.8.8.8 and 9.9.9.9, both unencrypted. Replace them with:

tls://dns.quad9.net

Then click Apply.

Add filter lists: Go to Filters → DNS blocklists. The AdGuard DNS filter is already active. Add if desired (Add blocklist → Choose from the list, then Save):

  • OISD Blocklist (Small or Big) — broad filter list; oisd says it “prioritizes functionality over blocking”
  • HaGeZi’s Normal Blocklist — extended tracker blocking

Check it’s working: Go to adblock-tester.com from a connected device. You should get a high score.


Step 6 — Guest network

A guest network is completely separated from your main network. Devices on the guest network cannot communicate with devices on your main network.

Use this for:

  • Smart home devices (TV, speaker, thermostat)
  • Visitors’ devices
  • IoT devices whose software you don’t trust

Go to Wireless and find the Guest Network section. Enable it, give it a different name than your main network and set a separate password. On some models guest wifi is not available while Repeater is on; the Wireless page then says so.

GL.iNet’s defaults already keep guest devices apart from each other (client isolation) and from the admin panel. One option worth switching on: Block WAN Subnet, under Network → LAN → Guest Network → WAN Access Control on firmware 4.11 (on 4.10: Network → Subnet → Guest Network → WAN Access Control; on 4.8 and 4.9: Network → Guest Network → Block WAN Subnets). Then guests can reach the internet but not the network above your router (the hotel’s network, or your ISP router’s at home).

If you want multiple separated zones such as work, IoT, and private, a guest network is only one extra segment. See network segmentation with VLANs for multiple isolated zones via LuCI.


Step 7 — Change wifi password and network name

The default wifi password is on the bottom of the router. Change it to something stronger.

Go to Wireless. Choose a network name (SSID) that doesn’t reveal anything about the device or location. Set a password of at least 16 characters.


Verification

After setup check four things:

What How Expected result
VPN active ip.me IP of VPN server
DNS goes through AdGuard Home AdGuard Home → Query Log Requests from your devices visible
Ads and trackers blocked adblock-tester.com High score
Guest network isolated Connect via guest, try 192.168.8.1 No access to router

Using it as a travel router

The advantage of a travel router: you set everything up once, and every location works the same.

In a hotel you connect the router to hotel wifi via Repeater. All devices you connect automatically go through VPN — your phone, tablet and laptop. You don’t need to configure anything separately on each device.

Some hotels require a login page (captive portal) before you get internet. GL.iNet handles this with Login Mode for Public Hotspots, on the Internet page under Repeater: the router pauses the VPN and custom DNS so you can open the login page from one of your devices. While that mode is on, your traffic does not go through the VPN, and the hotspot’s provider can see it. Log in, then check that the router has left the mode and the VPN is back before you use anything else. There is also an option to enter this mode automatically (Auto-Enable Login Mode for Public Hotspots). It is off by default; leave it off, so you decide when the VPN pauses.


Keep firmware updated

GL.iNet releases regular firmware updates with security patches. Check occasionally via System → Upgrade.

Scheduled Tasks is meant for things like reboot schedules and Wi-Fi timing, not as a general auto-update feature. For a travel router you do not use often, it is better to check manually for firmware updates before each trip.

Older OpenWrt base: the firmware we read for the Beryl AX (4.11), Brume 3 (4.9), Flint 4 (4.9), Slate 7 Pro (4.8) and Brume 2 (4.7) builds on OpenWrt 21.02, which OpenWrt itself lists as End of Life since May 2023. GL.iNet maintains its own firmware and publishes security advisories; we didn’t check which fixes it carries over, so keep the firmware up to date.


Next step

Go further