FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

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.
0 votes
241 views 9 comments
by anonymous
I have two RUT955 with the same firmware RUT9_R_00.07.02_WEBUI and the same configuration, but different hardware revision.

I connect to RUT955 LANs an Industrial Linux Computer with static address 192.168.1.127 and a Cam with static address 192.168.1.129.

Using the RUT955 with HW revision 1714 I never didn't have connection problem with the Industrial Linux Computer (ping on 192.168.1.127 is always OK) , but when I use the RUT955 with HW revision 2017 the connection with Industrial Linux Computer is totally random.

With both routers, the connection to the cam always goes.

When the connection between the RUT955 with HW rev.2017 is OK, if I try to disconnect and reconnect the LAN cable, the RUT955 router can no more see the industrial PC. Whereas if I repeat the operation with the RUT955 with HW rev.1714, the RUT955 router can always see the industrial PC.

1 Answer

0 votes
by anonymous

Hello,

Which firmware version your 2017 revision device has installed?

Have you noticed if this is specific to a certain physical port or happens with any connected LAN port?

Is the cable itself not damaged? 

Could you login to the router via SSH and execute the command:

  • logread -f

Then connect RUT955 to the industrial Linux computer and check if any log entries are generated?

For a deeper inspection you may download TCP dump from Services -> Package manager page in router's WebUI and enable monitoring for br-lan interface in System -> Administration -> Troubleshoot section. 

Extract capture file from the router after several unsuccessful attempts to connect devices.

Also, you to attach a troubleshoot file to your question. Please, replicate the issue, then access router's WebUI, go to System -> Administration -> Troubleshoot section and download troubleshoot file from there. The logs in the file might provide more insight into the issue.

Best regards,

by anonymous

Hello,

My 2017 HW revision has the FW version RUT9_R_00.07.02

-The problem happens for all LAN port, I tried changing cable and/or port, but nothing changes.

- If I try to disconnect and reconnect the LAN cable (from industrial PC), the RUT955 router sometimes does not see the industrial PC.

Sometimes router recognises the industrial PC (after connecting the LAN cable) only after about 30/60 seconds but if router does not 

recognises the industrial PC when all the system is power-on, it never recognises it.

- If I try to disconnect and reconnect the LAN cable (from Cam), the RUT955 router always (and istantly) sees the Cam.

Please find attached the requested files (via message private)

Best Regards 

by anonymous

Hello,

A couple of things from troubleshoot file, though not sure if related:

The ARP entry of 192.168.1.127 is, for some reason, flagged as incomplete.

Could you login to the router via SSH and try adding it manually with the following command:

  • ip neighbor replace 192.168.1.127 lladdr <MAC_address> dev br-lan

Replace <MAC_address> with the MAC of you Linux computer interface's address.

There is also a notification of:

  • Port speed for port 4 changed to 10 baseT

Which is rather weird, as router's ports are named LAN1, LAN2, LAN3 and WAN. 

Also negotiation of 10baseT mode is unusual. What duplex modes does your industrial device support, could there be a mismatch?

As for packet capture, it only indicates that there are several APR requests from the router to figure out 192.168.1.127 MAC, but no reply is detected.

Best regards,

by anonymous

Hello,

I tried to adding the MAC manually, but nothing has changed.

My industrial linux PC is Artila Matrix 518 and support 10/100 Mbps Ethernet.

Please find attached the TCPdump and Thrubleshoot  files (via private message) extract from router RUT955

with hardware revision 1714 (same firmware and same configuration and connect to the same industrial linux PC). 

I have never had any problems on routers with this hardware revision, everything work fine.

From log, I see for LAN1 in both the router "Port link state of port 4 changed...", while for other LANs I see " Port link state of port LAN x changed...".

by anonymous

The below comes from your latest uploaded troubleshoot file:

Tue Feb 14 11:39:29 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:29 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:35 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:37 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:37 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:38 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:40 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:40 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:41 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:43 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:43 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:44 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:46 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:46 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:47 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:49 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:49 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:39:50 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:39:53 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:39:53 2023 kern.notice Port speed for port 4 changed to 10 baseT
Tue Feb 14 11:40:01 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:04 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:04 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:40:06 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:07 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:07 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:40:09 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:11 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:11 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:40:12 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:14 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:14 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:40:15 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:17 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:18 2023 kern.notice Port speed for port 4 changed to 100 baseT
Tue Feb 14 11:40:20 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:21 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:21 2023 kern.notice Port speed for port 4 changed to 10 baseT
Tue Feb 14 11:40:23 2023 kern.notice Port link state of port 4 changed to DOWN
Tue Feb 14 11:40:25 2023 kern.notice Port link state of port 4 changed to UP
Tue Feb 14 11:40:25 2023 kern.notice Port speed for port 4 changed to 100 baseT

All of the connects and disconnects happen within a minute.

Please check the cable and ethernet ports, whether this is not a hardware issue on both devices as there is clearly some physical contact issues.

Best regards,

by anonymous

Hello,

Those are the attempts I made, disconnecting and reconnecting the Ethernet cable repeatedly to show that the reconnection happens instantaneously. 

If I repeat this operation with the router with hardware revision 2017, the reconnection happens after 30-60 seconds or in some cases never happens at all.

I have tried changing different Ethernet cables, but nothing changes.

Best regards

by anonymous
I have forwarded your issue to the developers to look into.

Once there are updates, I will post them

Best regards,
by anonymous
Hello,

The issue seems to be related to hardware failure and your following course of action should be to return the devices to your reseller for a warranty repair or a replacement.

Could you detail, if this is happens on all 2017 revision devices?

Best regards,
by anonymous
Hello,

I tried three devices with hardware revision 2017, the problem happend on all three devices.

Do I have to refer to a particular code (or a specific indication) when returning devices to the reseller for repair or replacement under warranty?

Best regards
by anonymous
Hello,

No special codes to refer to other than that the device is defective. Such behavior has been observed by the testing team and it is their directive to send such devices for RMA.

Best regards,