RUT240 Vs RUT241

Hi! My first post on here.
I’m planning to deploy RUT240 or RUT241 in remote site powered with solar.
There is several things that I want to achieve.

One of them is to be able access network remotely, since it will be behind CGNAT will have to be WG client or site to site.

Second thing is to be able route only two client devices back to WG server network.

Third thing would be to send SMS from HA.

So what would be your recommendations in regarding which device to choose and how to configure.


Both devices are very similar, but RUT241 is the predecessor of RUT240. RUT240 is (and has been for over a year) in an End of Life stage.
Additionally, RUT241 has twice the amount of RAM which will help when running multiple services at the same time. I’d highly suggest considering RUT241 or RUT200 over RUT240 to future-proof your setup and ensure latest firmware updates are available for a long period of time.
All of the aforementioned devices are running RutOS - an OpenWRT-based operating systems and all of them support WireGuard.
As for SMS sending from HA - could you clarify if you’re referring to Home Assistant or something else?

Best regards,

Thank You for quick reply!
So I will be getting RUT241.

Yes for HA it is HomeAssitant.


Great to hear that!
As for Home Assistant, SMS can be sent using HTTP POST requests, so that would most likely be the easiest way to send SMS. More information and detailed instructions can be found here: RUT241 Mobile Utilities - Teltonika Networks Wiki

Best regards,

Thank You! Strange that RUT241 is stil cat4.

Speaking about RUT200 some sites claims that it is replacing RUT241.
So what is difference between them, I know different LTE module, but what it means for performance? And RUT200 seems to be cheaper.

Oh well i bet soon you will hear from me again when I receive device…

By browsing to get more information I found this:

It is for TRB devices, not sure how different they are compared to RUT.

Is NTRIP package available for RUT200/241?
If yes, is it possible to run it as NTRIP server?
If yes, that would be huge bonus!
Not sure how to access serial interface, to connect external GNSS receiver.

This actually would be worth to investigate further even if it requires different device.

I received my RUT241 and getting problem after problem…

First is that it didn’t recognise SIM! After googling around I found similar issues with RUT240, bad solder on SIM reader.
What you know, same issue un RUT241, visually looks ok, but no continuity…

Now that it is finally operational, updated firmware, checked WG and there is no option to connect it to existing server as client… There is some descriptions available to do it but it is really confusing, there should be only six lines but made so complex. At the end managed to successfully connect to my UNIFI WG server. Now I need to set rules for only some clients to use VPN, currently all traffic goes through VPN.
Still can’t ping rut lan from main lan, I can ping rut itself on WG IP only.

OpenVPN config file from UNIFI doesn’t work…

Checking packages no NTRIP available, tried to upload manually it says not supported…

No Tailscale…

It all sounded good initially but now seems disappointing…

Now trying to install VPN policy routing getting this error

I did factory reset and even firmware update in bootloader mode, still command doesn’t work.

I have now opened different tread
to make it more relevant to the issue.


I’ll answer you concerns one by one one for clarify:

NTRIP on our devices works as a gateway between rover device and NTRIP caster. It does not interfere with or parse the data sent from the caster, but rather forwards it to rover via serial connection transparently. This means that the NTRIP package is only available on devices with serial connections, which RUT241 does not have.

If that is the case, I’d sightly suggest exchanging the device. We haven’t experienced any issues with SIM slots on RUT241 (at least any that I’m aware of).

WireGuard, as a protocol, does not have a “server” or a “client” role. The only difference is whether the remote host is specified, the same way as in IPsec. So I would suggest referring to this article for more help with configuration: Wireguard Peer To Peer Configuration example - Teltonika Networks Wiki

Currently we only add our own OPKG repositories by default to avoid any compatibility issues. To overcome this limitation, you can use:

opkg update --force_feeds /etc/opkg/openwrt/distfeeds.conf
opkg install vpn-policy-routing --force_feeds /etc/opkg/openwrt/distfeeds.conf

We apologize if your first experience with our devices did not meet your expectations. If you experience any further issues, let me know here or in a separate thread.

Best regards,

So, this is first 241 with SIM issue that you know now!
Well, for me it was much easier and quicker just resolder SIM socket.

There seems to be two different packages for policy routing VPN policy routing, and PBR
On newest openwrt it is supported only PBR.
So not sure how far is rutos.

I think it would be better to continue on the other tread, will be more related to name.

This topic was automatically closed after 15 days. New replies are no longer allowed.