Ethtool issues with eth2

Software SW tweaks
1

Hi,

I am trying to connect a TO (6.5.2, firmware not yet updated; eth2-switch set to SFP) via fibre to fibre switch (TP-Link SX3008F). The switch does not allow autoneg (no idea why - only fixed 1000M or 10G; I will contact their support tomorrow), I therefore set the switch to speed 1000/full duplex. When plugging in the DAC-cable, I get no connectivity.

root@turris:~# ethtool eth2
Settings for eth2:
        Supported ports: [ ]
        Supported link modes:   2500baseX/Full
                                1000baseX/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  2500baseX/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

Syslog:
Feb 22 21:49:00 turris kernel: [15889.570350] sfp sfp: module FS               SFPP-PC01        rev A    sn G2330438860-1    dc 231010  
Feb 22 21:49:00 turris kernel: [15889.579710] mvneta f1034000.ethernet eth2: switched to inband/2500base-x link mode

With the switch in 1000M and the TO in 2500M-mode and autoneg not working it is clear why it does not work.
I therefore tried to change the speed manually, but get the following error:

root@turris:~# ethtool -s eth2 speed 1000
Cannot advertise speed 1000

I tried other modules but it seems I can not set speed at all (autoneg off and duplex half neither work). The only module, that does work, is the Turris SFP (with speed 2500 obviously).
Do others have this problem as well? What to do here to bring up the link between switch and TO?

Best,
ssdnvv

2

Ok, then this seems to be a bug. I will file an issue at gitlab.

3

Possibly related to This?

4

No, I doubt that it is related - I can set speeds on other modules, but not on this one (even though it reports to support link rate 1000.
Created gitlab-issue: Ethtool - cannot connect DAC cable in 1000baseX-mode (#950) · Issues · Turris / Turris OS / Turris OS packages · GitLab

1 Like
5

@mbehun maybe you could have a look into this as well (maybe linked to FS 2.5GBase-T SFP not working with Turris Omnia (2024) ?)

6

Instead of this, could you try

ethtool -s eth2 autoneg on advertise 0x20000000000

?

7

From the knowledge i gained the sfp works as wan only.

8

Naaah you can reconfigure it and for example add to br-lan and use one of lan ports as wan. Imagination is your limit. Its separate interface. What would you do with it belongs to you.

9

If thats the case I will have to use it like that to incease my hapiness gained from more efficient network topology

10

Any port can be used for WAN or LAN, depends on the configuration. You can also put a copper SFP module capable of 2.5G into the SFP cage (for example Turris SFP) and have one 2.5G capable ethernet port. Or even two 2.5G capable ethernet ports, the second one via USB…

11

Took me a while until I found the hex-codes - thanks for that. But unfortunately it still doesn’t work:

root@turris:~# ethtool -s eth2 autoneg on advertise 0x20000000000
Cannot set new settings: Invalid argument
  not setting autoneg
root@turris:~# ethtool eth2
Settings for eth2:
        Supported ports: [ ]
        Supported link modes:   2500baseX/Full
                                1000baseX/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  2500baseX/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

I didn’t dig into the version-changes for ethtool, but

root@turris:~# ethtool -h
ethtool version 5.16

whereas

grafik
grafik705×75 5.55 KB

→ does this have to do something with the old version installed on our TOS v7?

12

I don’t know, sending you a chat message.

1 Like
13

@mbehun I’ve sent the details per chat some days ago - I’ll turn off the device until you give me an heads up when you are ready (to save some energy).