WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

RUTX09: was this product ready for market ?

0 votes
2,093 views 12 comments
by anonymous
RUTX09 is a massive piece of crap.

We have all the major issues when trying to set it up.

Changing the LAN IP is a nightmare.

Imposible to upgrade the firmware from 1.01 to 1.04 from the Cloud or locally. Each time it manages to load the file, and after reboot, the firmware is unchanged.

I finally tried to upgrade from 1.01 to 1.02 and now the router HTTP port displays a LUA error.

If that is an attempt to destroy your repuation, that's a success.
by
Last update: sometimes, we get it working after several reboots (when it fails, all signal LEDs keep blinking every 0.5s indefinitely).

When it works, it seems the first attempt of GUI access through RMS kills it.

Again, this is after a RMA.

I don't think this gear is ok and I don't think Teltonika tech support took the issue seriously.

2 Answers

0 votes
by anonymous
Hello,

Sorry to hear these troubles, but these are clearly not the typical ones.

Also most likely you got one of the very first devices, so new firmwares and units can not have such issues.

If you reset the device, do you still get the same HTTP issue ?
by
If I reset the device, I manage to access it again. Then I try to upgrade to 1.04: dead again.

I read in other threads that other people had similar issues.

Any known issues with firmware 1.01 that could explain those troubles ?

Any way out of it ?

Thank you
by anonymous
Hi, David,

Most likely new FW version with FW upgrade instuctions will be provided today or in the beginning of the next week.

At the same time could you PM me the backup and troubleshoot files from the device ?
by anonymous
Last news: one more attempt successfully upgraded the device.

The LAN IP management is now working correctly.

But the status page show NO MOBILE connection, despite it is connected.

If I try to edit MOB1S1A1 settings, it fails after 30 seconds with gateway timeout.

I tried to remove the MOB1S1A1 interface and re-create it: the device is now not accessible anymore though HTTP (ping OK).

SSH also is not working despite enabled.

Also, I was unable to get a working WEB CLI (through WEBGUI or through RMS).

Also, the switch management page seems broken (I loose connectivity with the device if I remove pre-existing VLAN 2).

That's a really long list of non-working features.

I recommend you reach us with some level of transparency about this matter, because I have the gut feeling that you perfectly know that the product was not ready for market, and we are about to blacklist Teltonika. After all, Sierra Wireless or CraddlePoint are more expensive, but they work flawlessly.

Thank you
by anonymous
Thank you for coming back.

I have sent you a PM with a request for a remote session. Please see if that could be arranged.
by anonymous
Last news: after a hard reboot, we managed to access the RUTX09 and this time, it seemed to work perfectly.

Mobile settings was accessible, GUI was responsive, etc...

I even managed to setup a L2TP tunnel as OpenVPN is buggy (password auth mode requires a certificate to be uploaded...).

And suddenly after some minutes doing nothing, we got this trying to access the WEB GUI:

/usr/lib/lua/luci/dispatcher.lua:261: /etc/config/luci seems to be corrupt, unable to find section 'main'

stack traceback:

[C]: in function 'assert'

/usr/lib/lua/luci/dispatcher.lua:261: in function 'dispatch'

/usr/lib/lua/luci/dispatcher.lua:129: in function </usr/lib/lua/luci/dispatcher.lua:128>

Seriously, that device is going to be sent back to the distributor.
by anonymous
by anonymous
We are going to send back this piece of crap.

It's unusable.

Perhaps it's this one which is broken, but we wasted hours on it, so I am not sure we will buy Teltonika again.
by anonymous
Hello,

We did asked for a remote session to check the device ourselves a few times without any success, this unit will be checked after receiving it back. If there really are issues that could be reproduced with more than one device these will be definitely fixed with the new FW release after detailed analysis of the cause.

Can you PM me the serial number so we could track it in case this device is sent back ?
by

Serial is 1102206147.

It came back from RMA, and at first it seemed ok. We tested it for several hours.

We sent it to the customer and the weird behaviour started to appear: lost 4G, lost cloud link and no local access to the GUI.

David

by

Last update: sometimes, we get it working after several reboots (when it fails, all signal LEDs keep blinking every 0.5s indefinitely).

When it works, it seems the first attempt of GUI access through RMS kills it.

Again, this is after a RMA.

I don't think this gear is ok and I don't think Teltonika tech support took the issue seriously.

by anonymous

Hello! I can not create a new question, so I am writing in a similar topic.

After updating the firmware to RUTX_R_00.02.01.1, RUTX09 worked for me for a couple of days and after rebooting it stopped loading at all. It does not distribute DHCP, with my static address I also can’t connect to it, Just flashing the signal every 1s indefinitely.

How else can I connect to the device? through USB?

0 votes
by anonymous
It seems you're having the same issue I had.

I had to RMA the unit.

It happened twice, on a total of 3 RX-09, which is quite a high ratio to say the least.

Also, a RMA takes like 2/3 months because it seems Teltonika tries to deny the hardware issue.

So it's likely we will move to other vendors (Mikrotik, Sierra or Huawei).