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.

RUT240 eth0 sudden autonegotiation problems

0 votes
629 views 5 comments
by anonymous

I am running a RUT 240 (firmware 7.2.7) to hook up a MOBOTIX IP camera to the internet via mobile.

The camera is connected to LAN (eth0) via a PoE injector. This has worked without problems for quite exactly two months.

Yesterday morning connection to the camera was lost. Inspection in place showed that the router is online, the camera is working (when connected to a laptop instead of the RUT240 for example). But the camera is not getting to the internet, and cannot be pinged from the router anymore.

The logs is clearly showing that there is a problem on the ethernet interface somehow:

Tue Dec 13 17:23:05 2022 kern.warn kernel: [ 5429.026270] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

Tue Dec 13 17:23:06 2022 kern.warn kernel: [ 5430.050288] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

Tue Dec 13 17:23:33 2022 kern.warn kernel: [ 5457.969475] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

Tue Dec 13 17:23:34 2022 kern.warn kernel: [ 5458.978220] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

Tue Dec 13 17:23:36 2022 kern.warn kernel: [ 5460.002842] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

Tue Dec 13 17:24:03 2022 kern.warn kernel: [ 5487.968696] br-lan: received packet on eth0 with own address as source address (addr:00:1e:42:42:dc:0d, vlan:0)

and

2022-12-13 09:16:55 Switch Events Port speed for port LAN 1 changed to 10 baseT
2022-12-13 09:16:55 Switch Events Port link state of port LAN 1 changed to UP
2022-12-13 09:16:48 Switch Events Port link state of port LAN 1 changed to DOWN
2022-12-13 09:16:47 Switch Events Port speed for port LAN 1 changed to 100 baseT
2022-12-13 09:16:47 Switch Events Port link state of port LAN 1 changed to UP
2022-12-13 09:16:46 Switch Events Port link state of port LAN 1 changed to DOWN
2022-12-13 09:16:45 Switch Events Port speed for port LAN 1 changed to 100 baseT
2022-12-13 09:16:45 Switch Events Port link state of port LAN 1 changed to UP
2022-12-13 09:16:44 Switch Events Port link state of port LAN 1 changed to DOWN

 

The link state is changing up/down constantly, and the speed is also inconsistent.
Ethtool then is showing this:
root@Teltonika-RUT240:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes
It only is showing 1 GBit/s a supported speed?
Trying to set it to a fixed 100 MBit/s full-duplex link (which is what should be auto-negotiated) just gives a 10 mbit half duplex link that's not working:
root@Teltonika-RUT240:~# ethtool -s eth0 speed 100 duplex full autoneg off
root@Teltonika-RUT240:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: off
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes
Is this interface somehow dead?
Of course I:
  • rebooted the router (several times, incl. pulling the power completely)
  • rebooted the camera
  • switched the network cable
This is the same router where I had massive problems getting it to work LAN-wise at all, see here: 
I had the first device replaced on warranty, and this one here is the replacement I got.
Makes me wonder if I'm the only one with such problems, or is the device quality just bad?
Christian

1 Answer

0 votes
by anonymous

Hello,

eth0 is actually a switch and the switch driver doesn't support manually setting link speeds. The switch hardware itself does support the feature, but making use of it would require modifying the switch driver, which is planned but not available at the moment.

To query for port details, you can try the following commands:

  • ubus call port_events show
  • swconfig dev switch0 show

As previously, it seems to be a hardware failure. Could you provide more details about the PoE injector used?

Best regards,

by anonymous

Hello,

here's the corresponding output:

root@Teltonika-RUT240:~# ubus call port_events show

{

        {

                "state": "up",

                "speed": 1000

        },

        {

                "state": "down",

                "speed": 0

        },

        {

                "state": "up",

                "speed": 10

        },

        {

                "state": "down",

                "speed": 0

        },

        {

                "state": "down",

                "speed": 0

        }

}

and
root@Teltonika-RUT240:~# swconfig dev switch0 show
Global attributes:
        enable_vlan: 0
        ar8xxx_mib_poll_interval: 500
        ar8xxx_mib_type: 0
        enable_mirror_rx: 0
        enable_mirror_tx: 0
        mirror_monitor_port: 0
        mirror_source_port: 0
        arl_table: address resolution table
Port 2: MAC 00:1e:42:42:dc:0d
        soft_reset: ???
Port 0:
        mib: MIB counters
RxGoodByte  : 832708 (813.1 KiB)
TxByte      : 832708 (813.1 KiB)
        pvid: 0
        link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
Port 1:
        mib: No MIB data
        pvid: 0
        link: port:1 link:down
Port 2:
        mib: MIB counters
RxGoodByte  : 832708 (813.1 KiB)
TxByte      : 832708 (813.1 KiB)
        pvid: 0
        link: port:2 link:up speed:10baseT full-duplex auto
Port 3:
        mib: No MIB data
        pvid: 0
        link: port:3 link:down
Port 4:
        mib: No MIB data
        pvid: 0
        link: port:4 link:down
I'm not sure about the concrete model of the PoE injector used, I would have to look this up on location. It's a "run of the mill" standard 802.3af brick-type mid-span injector.
Is there any sense in trying to put a dumb switch between the RUT 240 and the PoE injector?
Or is this clearly a hardware fault and I need to replace the device?
by anonymous
Right now the system rebooted without obvious reasons. Power failure is very unlikely (UPS), nothing in the logs with any hint to a reason.

I'll open another case with the seller to replace this unit. I'm more than hesitant to make to planned switch to Teltonika for those projects. We NEED a stable device that can run unattented for months or often years. That's not what it looks like to me.
by anonymous

Also, are you sure about the switch chip thing?

I was on location today, and the second ethernet port (labeled WAN, but both are in the LAN bridge) seems to work.

Ethtool eth1 also does give much more sensible results:

root@Teltonika-RUT240:~# ethtool eth0

Settings for eth0:

        Supported ports: [ TP MII ]

        Supported link modes:   1000baseT/Full

        Supported pause frame use: Symmetric Receive-only

        Supports auto-negotiation: Yes

        Supported FEC modes: Not reported

        Advertised link modes:  1000baseT/Full

        Advertised pause frame use: Symmetric Receive-only

        Advertised auto-negotiation: Yes

        Advertised FEC modes: Not reported

        Speed: 1000Mb/s

        Duplex: Full

        Port: MII

        PHYAD: 0

        Transceiver: external

        Auto-negotiation: on

        Current message level: 0x000000ff (255)

                               drv probe link timer ifdown ifup rx_err tx_err

        Link detected: yes

root@Teltonika-RUT240:~# ethtool eth1

Settings for eth1:

        Supported ports: [ TP MII ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric Receive-only

        Supports auto-negotiation: Yes

        Supported FEC modes: Not reported

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric Receive-only

        Advertised auto-negotiation: Yes

        Advertised FEC modes: Not reported

        Link partner advertised link modes:  10baseT/Half 10baseT/Full

                                             100baseT/Half 100baseT/Full

        Link partner advertised pause frame use: Symmetric Receive-only

        Link partner advertised auto-negotiation: Yes

        Link partner advertised FEC modes: Not reported

        Speed: 100Mb/s

        Duplex: Full

        Port: MII

        PHYAD: 4

        Transceiver: external

        Auto-negotiation: on

        Current message level: 0x000000ff (255)

                               drv probe link timer ifdown ifup rx_err tx_err

        Link detected: yes

The supported link modes on eth1 look correct, and as I said I do get a link there and can use the interface.
It seems like "just" eth0 died or has some kind of defect.
by anonymous

eth1 has separate hardware, it is not displayed by either of the commands (ubus call port_events show, swconfig dev switch0 show)  and you can configure it with ethtool.

by anonymous
OK, then this seems to be a clear case of eth0 begin dead.

I already opened a case with my distributor.