-
Version4.0
-
Firmware Type0704release5
-
Update Time2025-03-17 09:47:44 (UTC+00:00)
Thanks for the quick response! Is this sufficient?
Version4.0
Firmware Type0704release5
Update Time2025-03-17 09:47:44 (UTC+00:00)
Thanks for the quick response! Is this sufficient?
Worked great, thanks. I must have had formatting issues copying and pasting the script. The one line format without rollover worked perfectly.
Can anyone confirm if using this script method will result in the public wan ip from the sim card service provider being presented to the device plugged into the lan port? or, will it still be double natted?
@bruce What IP address does the admin GUI (web) page respond to when the device is in pass through mode? I can’t seem to access it.
@jamster it is 192.168.8.1. if you did not change the default ip adress in the router mode.
Thanks - I’ve had a further look at this. I did change the default IP address, but cannot access it from behind my router (which is admittedly set up in a quite complex way).
However, I’ve found that the Spitz also responds on its gateway address:
I use multiple routing tables on my Mikrotik router, so I have to update them all with the new gateway IP address via a script.
I’ve also noticed that my carrier occasionally updates the IP address but it does not look like this is picked up by the Mikrotik, and is causing the routing to fail an therefore my WAN failover to kick in to my other (non-Spitz) connection. Cycling the interface to cause (1) new IP and (2) route refresh seems to do the trick but I’ve not debugged this in detail yet.
Present the IP (public or CG-NAT) provided by the operator to the device plugged into the LAN port. no double NAT.
Hello, Is it possible to add the IP passthrough option in the next firmware version? It would be easier to enable this option with no questions...
Just wanted to reply here and say I was able to enable IP passthrough with zero issues.
It seems like most/all of the caveats/issues people were experiencing in this thread have been fixed at this point, save yourself the trouble of reading the entire thread as most of those are irrelevant.
Puli AX: plugged Puli LAN into Unifi gateway’s WAN port, visit 192.168.8.1, click to auto setup 5G (T-Mobile Business SIM), updated to latest firmware from the web UI, SSH’d in and ran the one line command from bruce’s latest message. SSH terminal will show lost connection, this is normal, wait ~30 seconds or so and check your router (Unifi in my case) and you should have the WAN IP from your ISP. I did not need to set manual DNS on my Unifi setup but I read that others may need to before they can load pages on their devices.
I am still able to access the GL.iNet interface from the original 192.168.8.1 with zero issues, and I can also still SSH into it at the same IP without any changes in the UI or Luci.
Big thanks to the GL.iNet team for all your firmware work and for helping people out in the thread.