Hello Folks.
Please I need assistance in setting up slate Ax (GL-AX1800) and Beryl Ax(GL-MT3000). Is there a step by step guide please. Also when I access admin panel via 192.168.8.1 right after logging in on either router, I inmidiately get kicked out. This has happened several times. Any assistance will be greatly appreciated 
Also ensure you have cleared any browser cache.
1 Like
This one is more specific:
2 Likes
Panel Issue:
Make sure to change the router-Ip of the travelrouter so: ( network -> Lan -> Router IP Adress)
192.168.8.1 GL-Homerouter f.e. Slate (no change needed)
192.268.8.7 GL-Travelrouter f.e. Beryl (from the moment you changed the Beryl AdminPanel will be reached with this IP)
Make bookmarks for the different log ins and be aware you may need to replug the Lancable connection depending the router you are configuring)
WireGuard
Then make sure the Beryl is tether with your mobil (they must use different "Internets" !)
And the Slate is connected to your homerouter (HomeISP) via Ethernet -> WAN input of Slate
Start to setup the Wireguardserver on the Slate you can create a configuration-file and need to import this config file on the beryl. (WireGuardClient)
Then your Beryl will connect to the Slate and all devices connected to Beryl will have the IP-Adress of your Home.
pay attention to the endpoint in the configfile you use on the Beryl
Example
(For that most people need to have a puplic IP4 and forward the neccesary Ports from the
HomeISP -which is a fritzbox in the example -> to the GL-Homerouter
ConfigFile
[Interface]
Address = 10.0.0.5/24
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
DNS = 64.6.64.6,10.0.0.1
MTU = 1420
[Peer]
AllowedIPs = 0.0.0.0/0,::/0
Endpoint = xxxx.selfhost.co:51820
PersistentKeepalive = 25
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
DDNS // selfhost or GL-inet DDNS ?
in my case i used a selfhost DDNS instead the DDNS of GL-iNet
Webhosting und DynDNS von selfHOST - selfhost selfhost free will do it
you will need to tell your homerouter that it is also reachable under the selfhost DDNS
(DDNS Settings of your HomeRouter)
explaination: Most HomeRouters are getting a new IP4-Adress all 24 hours from the ISP.
The EndPoint-Adress the GL-Inet VPN/WireGuard-Configfile is grabbing is the actual IP-Adress or the DDNS from GL-Inet is this works for you)
IF you use DDNS selhost f.e. the EndPoint will point to the DDNS of selfhost - and if you configure this on your mainrouter - then it doesent matter that this ip adress is changing all 24 hours because the config is pointing to the Selfhost-DDNS and the DDNS is pointing to actual IP of the Homerouter whatever it is) Because many don´t pay attention to this - they are suprised that next day the connection fails) But maybe you are good with DDNS of GL-Inet. Then you do not need to change tje Config-File manually. Just try it with activated GL-Inet DDNS first if you want.
Portforwarding on Homerouter (ISP) can be AT&T, Telecom, Vodafone
This are the TCP and UDP Ports that should be forwarded on the Homerouter
to the Slate
Static IP for Slate
Look what IP-Adress have your Slate in the Settings of your Homerouter and tell
the Homerouter(ISP) to use a static IP for the Slate
and tell the slate to have this static IP under Admin-Panel: Ethernet 1 -> Modify Internet -> DHCP -> Static
maybe you need to check some other installations to find what is fitting for you
For OpenVPN ist very similair just the configfiles look a bit different
keep in mind:
HomeISP -> portforwarding -> Slate (GL-inetHomerouter) <- Beryl (Travelrouter)
public IP4 vs CGNAT-Issue
If you cant portforwarding on your Mainrouter (ISP) check if you are behind a CGNAT
Port Forwading not working - #5 by j2zero If you dont have a public IP4
you may need to give a Call to your Provider and decalre them you need IP4 and not CGNAT.
took in my case 24 hours and they changed it.
If you understood the upper steps and possible issues to handle - it will work.
Otherwise you can also take a look into the suggestion of the following post regarding tailscale
Good Luck !
and yes - this are all points you have to reconsider - just switching ON/OFF switches within the GL-Inet Adminpanels will mostly not bring you to the goal. You need access to your Main-Home-Router and get familiar with the settings there- especially DDNS and Portforwarding. If your Homerouter can run a Wireguardserver natively you can also activate and run WireGuardserver on your HomeMainrouter and use its configfile on your Travelrouter - then you do not need the Slate inbetween
1 Like
A couple of others have posted about DDNS and opening ports on your home router, but you may want to look into setting up a tailscale network with your routers.
Tailscale will allow you to remote access your home network without opening ports on your router or relying on DDNS. I use this method to access networks at my home and on a boat that I own.
Tailscale howto gl-inet
Good luck
1 Like
In my case i needed WireGuard for working abroad - and tailscale (even it is based on wireguard)
gave me some jitter on phonecalls - now i can even activate VPN-Cascading without Jitter)
This is also a good read regarding the topic "working abroad" Digital Nomad VPN Tutorial using Wireguard or Tailscale
1 Like
Thank you so much @Tagor would you be kind enough to help me set it up? Please let me know what it'll cost me. I'm stuck at trying to change the ip. I see IPV4 and IPV6. Will I be be changing both on the 1800. Please let me know.
1 Like
Please make sure you are not behind a CGNAT
For me it was the same - i had IPV4 and IPV6 - but it was CGNAT
so i called my InternetServiceProvider on Sunday and opend a Ticket.
At Monday it was solved and i got "real Internet" with IPV4
if you made sure your ISP is not using CGNAT the community here will be for sure able to help you for free getting your routers running.
there is a thing called "NAT-Bridge" where you can rent a vserver, but i am not familiar with the process. Homelab trotz IPv6/CGNAT - Wireguard & NAT sind die Lösung maybe you need to translate this article