I am barely new to Teltonika devices but already quite familiar with openwrt and Opnsense.
Therefor I should manage a Teltonika device.
I have got a RUTX 12.
I upgraded the Firmware to Version RUTX_R_00.07.09.3 and update all Modems as requested to the current state.
1st Issue.
When I use the 2.4 GHz Wifi as client to connect to an AP all 2.4 GHz clients connected to RUTX12 lose their connection. In AP Mode and Multi AP, too.
Therefor I switched back to 07.08.03 and this issue was solved (workarounded)
2nd issue
Answer to myself.
Please RTFM. I bought a used unit without all equipmment and Antennas.
Solution for modems is to connect the right Antennas.
The RUTX12 is distinctive for housing two CAT6 LTE mobile modules, each demanding one main and one AUX mobile antenna. These antennas can individually achieve speeds of up to 300 Mbps without bonding.
Today I inserted an active SIM. It works in a Mobile Phone.
On the RUTX it only complains about limited service.
It is a Sim from a german provider called Fraenk it is a sub from Deutsche Telekom.
I tried manual apn and selecting manual operators. Nothinng worked. Therefor I switched up to 07.09.3 again to see if the modems don’t work with the older version.
Same result. Does anyone have a clue where to look.
Hey Teltonika, are you really serious releasing firmwares with these bugs? I mean 2.4GHz is the main Network for IOT.
Regarding the first issue with 2.4 GHz Wi-Fi clients, I was unable to replicate the behavior on the RUTX12 with the latest firmware. In my tests, everything worked as expected – when using WWAN (Wireless WAN) to connect as a client, the 2.4 GHz clients connected to the router’s AP remained connected.
However, if I understand your description correctly, are you saying that after disconnecting and reconnecting to the WWAN, the wireless clients on AP lose their connection? If so, this behavior is normal. The 2.4 GHz radio needs to restart disconnecting current clients.
Now, regarding the mobile APN issue, I suggest checking if the SIM card requires a PIN, which can be entered under Network → Mobile → General. Also, ensure that the mobile interface is set to “IPv4 only” in Network → WAN. Verify that the router is not locked to a specific LTE/3G band, as this can affect connectivity. Additionally, try restarting the mobile connection in Status → Network → Mobile.
Could you also try selecting the auto APN to describe what happens? Also, try putting a SIM card in the second SIM slot.
If the issue persists, I would need to review a troubleshooting file. I have sent you a form to complete, for the ticket ID use “9496” and once submitted, I will contact you privately to move forward with the troubleshooting process.
The mobile connect is solved. The main reason was to connect the antennas correctly. That means both Main and Aux for Sim 1.
APN is on Auto now and it works fine.
The 2.4 GHz issue needs more explanation.
I connect to Wan with Wifi0 on the 2.4 GHz Radio. Configured as Multi AP.
Connection works. As soon as I connect to 2.4 GHz external WIFI through wifi0 I cannot connect to 2.4 GHz internally. That the internal connection could get interrupted is explainable to me, but it never gets up again. The 2.4 GHz is not advertised internally anymore, even after 10 Minutes or more.
I hope that explains it better.
When you’re connecting the RUTX12 to another 2.4 GHz AP as a client, it is normal that WLAN (wireless LAN) clients will not be able to connect to the RUTX12’s 2.4 GHz AP. In this configuration, most of the available options are dictated by the WiFi AP that the router is connected to, and making any changes could result in losing the connection to that external router.
To address this, I tested an alternative setup using Client mode (instead of Multi AP) to connect to another AP, and I was able to keep a wireless device connected to the local RUTX12 AP without disconnection. This might be a more stable option for your use case. Let me know if that helps.
If the issue persists, try factory resetting the device and configuring this setup from scratch and provide a screenshot from the Network → Wireless (SSID) and Network → WAN pages, ensuring that any sensitive information like MAC addresses and public IPs is hidden?
Feel free to reach out if you have any additional questions or need further assistance.
I have the impression we are going in circles or I don’t get your solution.
Scenario 1:
Old Firmware 7.8.3
RUTX12 is connected to a 2.4 GHz Wifi as Client in single Mode or in Multi AP Mode.
(Multi AP selects the best suitable AP and Wifi Configuration available IMHO. Helpful when you move your router in a Vehicle to two different Locations with different SSIDs you can connect to. Saves mobile Data.)
Client can see the 2.4 Radio and SSID that is distributed separately from the RUTX12 so that internal Wifi Clients can connect to the RUTX12 and use the WAN connect that is established as WiFi Client or Multi AP within the RUTX12.
Expected behaviour, every travel router does this.
Scenario 2.
Firmware 7.9.3.
I can connect the RUTX12 to an existing 2.4 GHz WiFi. This is the default internet breakout (same as in Scenario 1).
But then, no matter if I am connected to the 2.4 Wifi (internet breakout) as Client or as Multi AP (- Client), the RUTX12 stops to provide a 2.4 GHz Wifi itself.
It does not come up.
I think the Firmware 7.9.3 ( or the 7.9.4 now) should behave like 7.8.3 in Scenario 1, but it doesn’t.
Have you tested this, because other users complain the same.
Initially, I thought you were using two WANs (mobile and WWAN), but your setup is now clearer. In Scenario 2, with the latest firmware, please enable the relay option in Network → Wireless → Relayd as shown in the screenshot below. Additionally, disable DHCP on your LAN interface in Network → LAN. Please note that in this case, WiFi clients connected to the RUTX12 AP SSID will receive an IP address from the external DHCP server, not from the RUTX12 itself.
that won’t help, because it will fail.
Hence the Router does NATting and the relayd is solely for the DHCP Service.
In this case I would get an IP from let’s say
172.31.8.0/16 (Private range from the Far away router let’s say on a campground) and my Router won’t accept any forwarding at all, because in the internal interface (192.168.1.1/24) would reject the 172...* and neither route it.
Please try the test of Scenario 1 with your newest firmware in your Laboratory. I would be happy to assist.
The relayd leads to no success IMHO.
Thank you
Martin
