I am experiencing a critical issue with the Teltonika Mobile App (specifically “Camper Mode”). When I use the app to scan for and join a new WiFi network (Station Mode), the router successfully connects to the AP, but the actual WAN Interface (the logical “pipe”) is deleted from the system.
The symptoms:
I use the app to connect to a new WiFi.
In the WebUI under Network → Wireless, the radio shows “Connected” to the new SSID.
CRITICAL: In the WebUI under Network → WAN, the previously existing WiFi WAN interface (e.g., ‘wifi0’) is completely gone/deleted from the list.
Because the interface is deleted, there is no routing, no firewall assignment, and no internet access, even though the WiFi link itself is active.
I have to manually “Add” a new WAN interface in the WebUI and bind it to the wireless radio every single time I change the SSID via the app.
Question:
Why does the Mobile App / Camper Mode delete the logical WAN interface instead of just updating the SSID within the existing interface? Is there a way to “lock” the WAN interface so the App cannot delete it, but only change the connection parameters?
Suggested Feature Improvement for Teltonika Mobile App:
To avoid the current issue where joining a network via the app deletes the logical WAN interface, the app should be updated with a simple “Mapping Prompt”:
Proposed Workflow:
User clicks “Join Network” in the App (Camper Mode).
App scans and finds the SSID.
NEW STEP: App asks: “Which WAN Interface should this network use?”
Currently, the app seems to default to a “clean slate” approach that nukes the existing configuration. Giving the user the choice to bind the new SSID to an existing WAN interface would solve the routing and firewall issues permanently for travelers.
Thank you for the detailed report. I was able to reproduce the issue on my end as well. I have forwarded it to our research and development team, and I will update you as soon as I receive their feedback.
That definitely sounds more like a bug in the “Camper Mode” handling than a normal config change on the Teltonika RUTM11. The app seems to recreate the client connection every time you switch SSID instead of reusing the existing WiFi WAN interface, and in the process it drops the actual WAN binding.
Since the radio still shows “Connected”, the wireless side is clearly fine — it’s the logical interface/firewall/routing part that gets wiped.
I don’t think there’s currently a proper way to “lock” the WAN interface against the mobile app. Most likely the safest workaround for now is avoiding SSID changes through Camper Mode and doing them directly in the WebUI, where the existing interface stays intact.
The way that this functionality currently works is not how it’s supposed to be, the feature also does not properly handle several edge cases, such as IP conflicts.
A minor overhaul of the feature is planned in the near future to address the following:
IP conflicts between connected STA and existing network interfaces
Ability to choose an existing eligible WAN network interface for a new STA connection (if there is any)
Ability to replace existing STA configuration in case router radio already has one configured (router limitation: one radio = one STA configuration)
Connection validation/verification UI after joining the STA, including guidance for resolving any encountered issues (ex.: phone loses Wifi connection to the router, IP conflict resolution, etc.)
WAN network interface naming issues: in case user chooses NOT to use existing network interface - app will create one automatically with unique name so user can identify that it was created by the app (ex.: instead of “wan“ app will create “app_camper_wan“) and when creating a new one, any prior WAN network interfaces that are not associated with any STA and were created by the app will be cleaned up.