GL.iNet travel routers differ in VPN protocol and firmware controls. A profile that works on a laptop may need different router settings.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
Do you need a router VPN client, inbound server, device app or site-to-site link?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Client will not connect | Check profile, protocol and model firmware without sharing keys. |
| Server cannot be reached | Classify WAN addressing, CGNAT and firewall before port changes. |
| Tunnel connects without traffic | Check route, DNS and overlapping LAN subnet ranges. |
Decision after the first test
Confirm model, firmware and the service's supported protocol, then test captive-portal access separately from the VPN tunnel.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- GL.iNet Brume 2 GL-MT2500/MT2500A (web_text; checked 2026-11-01)
- GL.iNet Brume 2 user guide (web_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.