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.
- 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”?
- 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
