Any plans to introduce this feature also to v4.9?
It’s not enabled.
I have provided feedback and submitted the request to the relevant team. We will evaluate it. Thanks
1 Like
Please log in to the ssh terminal, enter the commands below and the share the result with me to check: /etc/init.d/passthrough status
Btw, may I ask which firmware version you upgraded from to V4.8.3?
Is there any information about IP Passthrough in firmware 4.9?
Thank you.
What is the command to reverse this? I want to use this as a backup to my UDD SE but also take it camping with me to use for cellular internet access over wifi as a router when doing so.
Looking forward to seeing this built into the GUI natively… Any hints at a timeline for this; is it on the roadmap?
You should still be able to access the 192.168.8.1 admin panel, right? If so, go in there and switch it back to Router mode, and that should restore things. If not, another option is to press and hold the reset button for 4 seconds to recover the network settings.
Since this is a beta feature, we need to finish full testing before we can add it to the GUI. Also, some cellular module models (in different router models) don’t support it, which is one of the headaches we’re dealing with at the moment.
1 Like
Appreciate the info, thank you.
Out of interest, I connected my WAN2 port of my UDM SE to the LAN port of my GL XE3000 (4.8.3) without applying the script and disconnecting my WAN1 cable made it fail over to the GL XE3000 and it worked! Should it have? I could access 192.168.8.1 after applying the policy someone else mentioned above as well.
Without applying the script you shared, is there a config issue that could cause me issues down the line?
That is actually normal behavior. Given the capabilities of your UDM SE, the XE3000 is really just acting as a gateway here, you don't even need to switch the XE3000 to IP Passthrough mode, and router mode should handle everything just fine.
For example, IP Passthrough is used in this scenario: the SIM card has a public IP, and the subordinates of XE3000 (clients, etc.) want to use this public IP directly without configuring port forwarding on XE3000.
There might be other use scenario, but this is definitely the most common one.
I am not sure about your specific setup, but I assume you are good to go—the UDM SE's failover and XE3000 current config should cover your needs perfectly.
Just a heads-up, the XE3000 also has built-in failover support if you ever need it.
1 Like
Coming back to this now a year later, when can we hope to see this in a production release? I want to add a data point in support of moving WAN IP Passthrough out of experimental status and into the supported/documented feature set for the X3000.
Our situation: GL-X3000 running 4.0.0704-release5, using the cellular modem (Quectel RM520N-GL, T-Mobile Business) as the sole WAN, with passthrough enabled via the undocumented RPC call (netmode set_mode passthrough) since there's no GUI toggle for it. We've been troubleshooting intermittent network drops and reconnects and pulled a full logread export to dig in. Root causes we found:
-
The modem's AT command channel stalls periodically (
modem_AT: AT_Read epoll reached timeout), which fully tears down and rebuilds the QMI/MHI interface, a 10–50 second outage each time, several times in a 30-minute window. This makes teleworking a major challenge. -
We also found an existing thread here (GL-X3000 modem upgrade for firmware v4.8.3) where another user reports the same category of 5G disconnection instability that's remained an open issue. We end up having to keep SA off and keep NSA enabled, which has its own challenges based on my location.
I understand this thread isn't the right place to address these challenges, but I wanted to close by saying that since this is becoming a useful feature for most, it really should make its way into the stable releases so I'm not trying to address one issue and causing another by upgrading firmware and some people finding the passthrough unstable.
Just out out my own curiosity I updated firmware to 4.8.3 yesterday morning, enabled WAN IP Passthrough, seemed good and connection was stable, came to find this morning that we are now receiving “The interface is connected, but the Internet can’t be accessed.” Same configuration we have had on 4.7.4 and have been running for quite some time with no issues. Rebooted and still no connection. Ended up having to revert to 4.7.4