I’m having LAN issues with my Rutx50 (in my Motor home) when upgrading the firmware to version higher than 07.14.03.
The devices, whether Ethernet or Wi-Fi, receive a lease from DHCP and are reachable by each other.
No internet access.
No access to the Rutx web interface.
The SIM card LED isn’t lit.
I can access the LAN and the Rutx web interface with the mobile connection via openVPN.
I’ve upgraded and downgraded, with and without transferring the configuration. Always with the same result.
Now the only options are a setup from scratch or staying on the current firmware version.
Besides German, the only other option installed and therefore in the configuration is TravelMate (when it could only be installed via Packet Manager).
A Wireguard connection is configured from the Rutx to the home router. This is permanently active; a cron job (watchdog) was set up via script. There is also an OpenVPN connection via CloudConnexa to the home router for activation if required.
Browser cache isn’t the reason.
What could help?
This, I would assume, is regarding a physical (LAN) connection being present? Do the LAN port LEDs light up when plugging in the cable? Do you have passthrough or bridge mode set up on your mobile interface? Could you try accessing the device by setting a static IP on your PC?
What firmware versions did you try upgrading to that were causing issues? When upgrading, do you choose to keep the settings or not? Regarding your SIM card, does it require a PIN code to be inserted or a custom APN to be configured?
Thanks for your support.
Regarding the questions:
LAN is available and the LEDs are lit. I have several clients, including a Victron Cerbo, which I can access via LAN. However, the internet and the Routers UI is not available via LAN.
LAN is in bridge mode.
Regarding the mobile interface, I’m not sure what you mean. The connection is “UP” any way. I can access the router and the other devices from outside via the mobile interface and an OpenVPN connection.
This ultimately enabled me to downgrade using a saved firmware file and restore the backup.
All firmware versions above 17.04.3, stable and latest, are affected.
The initial upgrade was performed with keep settings.
I also tried to get the higher firmware versions to work without “keep settings” and instead with a backup restore.
However, without success. It only worked with 17.04.3.
It should be noted that in Passthrough and bridge modes, the device will not be reachable. In order to reach the WebUI, you’ll need to set a static IP address of the router’s LAN network.
Could you tell me why you’re using the bridge mode? Any particular reason?
The no internet issue sounds like it could be related to something else, possibly a custom APN being required? Could you confirm this?
You’re right. I’ve looked into it now. The interface mob1s1a1 is set to NAT!
The LAN interface, under physical settings > bridged interfaces, is enabled. From my point of view, everything looks fine on the mobile side.
Via the mobile interface and OpenVPN, I can access the LAN and the WebUI from outside.
Internally, when I connect my laptop to the router via Ethernet cable, I do get a DHCP lease with the newer firmware versions and can reach other clients in the LAN.
However, I don’t get any outgoing connection to the internet or access to the WebUI.
That’s what it’s supposed to be by default; that’s good.
This is also supposed to be the case, no issues.
Any possibility there’s an IP conflict? For example, you might have Wi-Fi enabled on your Laptop, which the router providing you with the Wi-Fi could also have the same IP address, 192.168.1.1. Ensure this is not the case. Any traffic rules under firewall settings that you’ve changed? Any port forwards that you might’ve set up?
So, back again, now from croatia and time to find out. No, wifi and LAN are different, that fits. There are only the default routes and the routes added automaticliy when my wireguard and openvpn were configured.
What if found out, back in firmware 7.14.3, in package Manager the “travelmate” package was in fail state. Retry wasn’t successful, a remove is not available.
I just tried 7.15.4, shortly I had access to the router, now, again, the router isn’t reachable by wifi or lan, even I have valid leases from DHCP. Access via internet using my openvpn tunnel is possible.
Thanks for getting back to us. There have been quite a few firmware updates released since 7.14.3 and 7.15.4, currently, the latest is 7.17.1, which I would suggest upgrading to to see if the issue still appears.
I would like to suggest starting fresh if that’s a possibility, in other words, I would like for you to reset your router back to its factory default state and then re-configure your OpenVPN configuration from scratch (you can take screenshots of your config, etc, so it’s a bit easier & faster to reconfigure). The reason for this suggestion is because not being able to access your device via its LAN ports (physically) is definitely not normal, and could even signal a hardware fault, resetting would allow us to ensure that this is not the case, and that perhaps it has to do something with some other configurations you might have done.
Indeed, after my last post, I performed a clean installation (last stable 7.15.4) from scratch.
I configured an OpenVPN connection to Cloudconnexa, as well as a Wireguard connection to my home router. Both connections are always up.
Furthermore, NMEA Forwarding and AVL are enabled and configured under GPS.
After that, everything worked as expected.
To my surprise, the same problems occurred after 14 days. Most recently, the day before yesterday. Sometimes restarting the router helps, sometimes the problem resolves itself after a certain amount of time (day?). Very ominous.
Hello,
As suggested, I upgraded to version 7.17.2 with a clean, from-scratch installation. I configured two permanent VPN connections: one using WireGuard to my home router and one using OpenVPN via CloudConnexa.
For over a month, it worked well, except for two brief interruptions of the mobile connection when crossing country borders.
Today, the RUTX router crashed while I was driving.
I’m having the same old problem: I can’t access the router’s web interface.
This time, I can’t even access it via VPN.
The three LEDs (3G-5G) are blinking. The reset button didn’t work, so I’m left with only a factory reset as an option.
This is starting to get really frustrating.
To clarify - after the crash occurs and the WebUI is no longer accessible, are you able to ping the device & perhaps even reach it through the SSH (CLI)? More details on how to access it via SSH can be found here: Command line interfaces - Teltonika Networks Wiki
If the above is possible in your scenario, we may be able to extract a troubleshooting file to see what’s happening exactly. If the above isn’t possible, I believe the best solution I would be able to offer is to reach out to your distributor or shop that you’ve purchased the device from, and proceed with an RMA (either the device gets repaired, or gets replaced by a new one, that decision is up to the reseller).
and time to find out. No, wifi and LAN are different, that fits. There are only the default routes and the routes added automaticliy when my wireguard and openvpn were configured.