RUTC50 on EE UK: native 464XLAT/CLAT, and concurrent 2.4GHz AP + WiFi-as-WAN?

Hello all,

I’m a huge fan of the RUT devices having deployed them in a number of remote locations, and so I want to move a motorhome over to one. It was running a Cradlepoint IBR900 but it has a high power drain and runs incredibly hot, so I put in an RUT955 I had around as a test before committing to an RUTC50 as the permanent 5G upgrade (I also want to run Docker locally). Before I buy, I want to confirm whether two problems I hit on the RUT955 are also present on the RUTC50.

  1. Native 464XLAT / CLAT on EE UK

EE runs an IPv6-only mobile core with 464XLAT, so the client device has to implement CLAT to present working IPv4 to the LAN. On the RUT955, selecting IPv4/IPv6 gives me an IPv6 address only, no v4 gateway and no v4 DNS, so IPv4-only LAN devices and IPv4-only sites are dead. Multi APN (with a separate IPv4-only PDP context) was dire, as EE clearly de-prioritise the second PDP session. (Frustratingly, their PAYG SIMs use normal CGNAT so side-step this issue, but their helpdesk are clueless about it and just parrot the “well it works in your phone so it’s your issue” line.)

Does current RUTOS on the RUTC50 implement 464XLAT/CLAT natively, so a single bearer serves both v4 and v6 LAN clients on an IPv6-only carrier like EE? Or is the position still “no native CLAT, use Multi APN or roll your own clatd/Jool”?

  1. Concurrent 2.4GHz AP and 2.4GHz WiFi-as-WAN

On the RUT955, enabling WiFi-as-WAN with Multi AP causes the WiFi to cycle constantly and it becomes unusable. If I do the Client approach it does work, but its performance is very poor (and well below that of the IBR900 doing the same thing).

Heading off the obvious answer before it comes up: “put the AP on one band (5GHz) and WiFi-as-WAN on the other (2.4GHz)” does not work for me. A lot of the in-van kit is 2.4GHz only so the 2.4GHz AP has to stay up, and most campsite and public WiFi I’d want to use as an uplink is 2.4GHz only anyway.

To be clear, I’m not asking for a second 2.4GHz radio. A single 2.4GHz radio can run AP and STA concurrently as long as both sit on the same channel. The IBR900, Robustel, DrayTek and TP-Link all do this: the client associates upstream and the AP follows it to that channel. I was quite shocked the RUT955 struggled so much when every other device I’ve tried manages this no problem.

So, two parts: (a) does current RUTOS on the RUTC50 do stable same-channel concurrent 2.4GHz AP + WiFi-as-WAN, following the upstream channel without the AP flapping, and (b) is the Multi AP cycling a known bug (maybe fixed as I know RUT955 is very end of life), or is single Client mode the only reliable approach? And if it is Client mode, why is same-radio throughput so much lower than comparable single-radio hardware achieves?

Thanks

Ben

Hello, @benjicx ,

Apologies for a delayed response and thank you for your detailed questions regarding the RUTC50.

Before we escalate this to our R&D team, could you please provide some additional information about your testing with the RUT955? This will help us determine whether the behavior is reproducible on the current RutOS platform.

Regarding the EE UK / 464XLAT concern:

  • Which RUT955 firmware version did you test?

  • What EE APN was configured?

  • Was the mobile interface configured as IPv4/IPv6, and did it receive only an IPv6 address?

  • Have you tested this with both EE contract and PAYG SIMs, and does the behavior differ?

Regarding the 2.4 GHz AP + WiFi-as-WAN concern:

  • Which RUT955 firmware version exhibited the WiFi cycling issue?

  • Were you using Multi AP or Client mode when the issue occurred?

  • Does the WiFi start cycling immediately after enabling Multi AP, or only after connecting to the upstream WiFi network?

  • What is the model of the upstream WiFi access point (if known), and is it using a fixed or automatic 2.4 GHz channel?

Once we receive this information, we will review the findings and, if necessary, escalate the case to our R&D team for further investigation.

Kind regards,
V.

Thanks V, and no problem on the delay. Answers below in your order.

Both issues were on the same unit: RUT955, firmware RUT9_R_00.07.06.21, modem EC25EUGAR06A11M4G_01.200.01.200.

EE UK / 464XLAT

  1. Firmware: RUT9_R_00.07.06.21.
  2. APN: EE’s standard consumer APN, “everywhere”.
  3. Yes. Set to IPv4/IPv6 it came up with an IPv6 address only, a /128 plus a /64 PD, and no usable IPv4. Set to IPv4-only it gave a working CGNAT IPv4 but then no IPv6.
  4. Yes, and it differs by SIM. It started when I moved from an EE PAYG SIM to an EE monthly contract SIM. The PAYG SIM gave native IPv4. The contract SIM comes up IPv6-only under IPv4/IPv6, which is in line with EE running 464XLAT on their pay monthly.

I got it working with the Multi-APN suggestion I found on the forum.

2.4GHz AP + WiFi-as-WAN

  1. Firmware: same, RUT9_R_00.07.06.21.
  2. Client mode (WiFi-as-WAN), sharing the single 2.4GHz radio with the LAN AP.
  3. Only after connecting to the upstream. Enabling it was fine. The AP started cycling once the client associated.
  4. The upstream was a 2.4GHz SSID served by several APs on automatic channels. The client was roaming between those APs, and each roam moved the shared radio to the new AP’s channel, which took my local AP down and back up each time. So it was not a one-off channel change, it cycled continuously.

I realise a single radio has to put the AP on the STA’s channel, but a full cycle of the AP going away for >1 min each time doesn’t work.

One extra finding:

With Multi APN up, the secondary IPv6 context shows much more latency jitter than the primary IPv4 one. Interleaved ping from the router to the same Cloudflare anycast node over a minute: IPv4 averaged 48ms with a tight spread, IPv6 averaged 93ms with occasional spikes to around 590ms, zero loss on both. Same latency floor, so not routing or destination. It looks like the second PDN context is scheduled less favourably than the first. I could not tell from here whether that is the modem, RutOS, or EE’s radio side.

464XLAT/Native-CLAT:

It was not covered in the reply, does the current RutOS platform on, for example, the RUTC50, support native 464XLAT/CLAT, so a single IPv6 bearer with the carrier’s NAT64 can serve IPv4-only LAN devices without the Multi APN workaround? If not, is it on the roadmap?

Thanks again.
Ben

Hello Ben,

Thank you for the detailed follow-up and the additional test results.

Regarding 464XLAT / native CLAT, the current RUTC50 documentation confirms support for NAT64 (Jool). However, the documentation does not state that RUTC50/RutOS provides native 464XLAT/CLAT for IPv4-only LAN clients over an IPv6-only cellular bearer. Since NAT64 and CLAT are separate functions, I need to clarify with our R&D team whether the current RUTC50 platform supports this use case without requiring Multi APN. I will also ask them whether native CLAT/464XLAT is planned for a future RutOS release.

For more information regarding NAT64, please refer to this wiki article:

Regarding the concurrent 2.4 GHz AP + Wi-Fi WAN, It was previously confirmed in this topic: Teltonika Community – RUTC50 simultaneous AP and Client, for the RUTC50, that when the same Wi-Fi hardware performs scanning while also providing an AP, the AP can be temporarily shut down and connected clients can disconnect. The stated workaround is to use separate 2.4 GHz and 5 GHz radios for the AP and Client functions.

The RUTC50 Multi AP function also performs periodic scans, with a default scan interval of 60 seconds and a minimum of 30 seconds. Please refer to this wiki article for more information:

The current RUTC50 firmware 00.07.24.5 includes a fix for STA-to-AP latency spikes during wireless scanning. However, the public changelog does not state that the underlying same-radio AP interruption limitation has been removed. Therefore, whether the current firmware can support your specific requirement - a continuously available 2.4 GHz AP while the 2.4 GHz STA follows different upstream channels during roaming - also requires clarification with our R&D team. Here you can find RUTC50 firmware changelog:

Regarding your Multi APN latency measurements, we noted the approximately 48 ms average latency on the IPv4 context versus 93 ms on the IPv6 context, with occasional spikes to approximately 590 ms and no packet loss. These are your reported test results; the cause cannot be determined from the available public documentation, so I will also ask R&D to clarify whether this behavior is known or expected with simultaneous PDP contexts.

We will clarify these points with R&D and provide you with the confirmed information.

Kind regards,
V.

Hello, @benjicx ,

I have an update from our R&D team.

  • Currently RutOS/RUTC50 does not natively support a complete router-side 464XLAT/CLAT solution, although a working proof of concept using Jool SIIT confirmed that it is technically feasible. Production support would require back-end, firewall, API, WebUI, NAT64 prefix discovery, and testing work, while modem-native CLAT remains as a possibility

  • To answer the question if adding this is in the future is being planned - yes, but I do not have an exact ETA for its arrival.

Hope this helps!
V.

Just a note that I’m also seeing this issue. I initially tested my TRB140 with the EE PAYG SIM from my phone, which seemed to function. I then bought a pay-monthly data-only SIM and hit this issue - once I eventually worked out what was going on, which took a while as I’m far from expert at all this. With the WAN PDP Type set to IPv4/iPv6, I only get an IPv6 address and the TRB140 doesn’t implement the required translation to make IPv4 work on the LAN.

While trying to understand the issues I found the following:

That says that in 2017, default Android already had the required support for 464XLAT:

So it’s a bit disappointing that almost a decade later Teltonika does not have this.

Greetings,

Thank you for your feedback and for taking the time to describe your experience with the TRB140. Your input helps us identify where we can improve the user experience.

We’ve forwarded your feedback to the product team for consideration.

Best regards,
T.