SFP+ TL-SM410U 2.5 Gb Copper RJ45 [Turris OS 6.0.3]

Hi All

Just wanted to play around with the SFP+ port of the Omnia.

When using a 1 Gb Copper SFP it works out of the box:
1G SFP
[ 9.101853] sfp sfp: Host maximum power 3.0W
[ 9.434774] sfp sfp: module OEM ES-T2-R rev A sn EM2TX45506 dc 221104
[ 19.845365] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:16] driver [Marvell 88E1111] (irq=POLL)

When I try to use the 2.5 Gb TL-SM410U Copper SFP it does not work.
2.5G TP-Link SFP
[ 9.082425] sfp sfp: Host maximum power 3.0W
[ 9.414731] sfp sfp: module TP-LINK TL-SM410U rev 2.0 sn 12260M4000825 dc 220621

Any ideas?

Anybody using the Huawei GPON SFP MA5671A ?

Which version of TurrisOS are you using?

OpenWRT 22.03 but I can try with the latest turris FW

OpenWrt 22.03 uses a different kernel than we do, but we are not going to provide any support for OpenWrt. You should ask on the OpenWrt forum unless you are using Turris OS.

It is EXACTLY the same with Turris OS.

Turris OS version 6.0.3
Turris OS branch HBS
Kernel version 5.15.78

1GB Copper SFP (works)
[ 8.118857] sfp sfp: Host maximum power 3.0W
[ 8.447957] sfp sfp: module OEM ES-T2-R rev A sn EM2TX45506 dc 221104
[ 13.759049] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:16] driver [Marvell 88E1111] (irq=POLL)

2.5GB Copper SFP (does not work)
[ 7.873821] sfp sfp: Host maximum power 3.0W
[ 8.197929] sfp sfp: module TP-LINK TL-SM410U rev 2.0 sn 12260M4000825 dc 220621

It is the same with the latest turris OS.
So any news on that??

Sfp is a bit complicated, and there is two sides o a link to mess up things. And a eprom to program more or less standrardized data, working in some device but not others.

There is a number of threads to read here in the forum.

There is a list of known working modules you should check out if you like a smooth sail

https://wiki.turris.cz/doc/en/public/sfp

And I guess the turris branded copper one will give you best support from turris team

in my case even 1G does not work :confused:

ethtool -m eth2
        Identifier                                : 0x03 (SFP)
        Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)
        Connector                                 : 0x07 (LC)
        Transceiver codes                         : 0x00 0x00 0x00 0x00 0x00 0x00 0x40 0x00 0x00
        Transceiver type                          : FC: Twisted Pair (TP)
        Encoding                                  : 0x01 (8B/10B)
        BR, Nominal                               : 3100MBd
        Rate identifier                           : 0x00 (unspecified)
        Length (SMF,km)                           : 0km
        Length (SMF)                              : 0m
        Length (50um)                             : 0m
        Length (62.5um)                           : 0m
        Length (Copper)                           : 0m
        Length (OM3)                              : 0m
        Laser wavelength                          : 0nm
        Vendor name                               : TP-LINK
        Vendor OUI                                : 30:b5:c2
        Vendor PN                                 : TL-SM410U
        Vendor rev                                : 2.0
        Option values                             : 0x00 0x18
        Option                                    : TX_FAULT implemented
        Option                                    : TX_DISABLE implemented
        BR margin, max                            : 0%
        BR margin, min                            : 0%
        Vendor SN                                 : 12260M4000639
        Date code                                 : 220621
root@turris:/usr/share/diagnostics#  ethtool -m eth2 raw on | hexdump -vC
00000000  03 04 07 00 00 00 00 00  00 40 00 01 1f 00 00 00  |.........@......|
00000010  00 00 00 00 54 50 2d 4c  49 4e 4b 20 20 20 20 20  |....TP-LINK     |
00000020  20 20 20 20 00 30 b5 c2  54 4c 2d 53 4d 34 31 30  |    .0..TL-SM410|
00000030  55 20 20 20 20 20 20 20  32 2e 30 20 00 00 00 1b  |U       2.0 ....|
00000040  00 18 00 00 31 32 32 36  30 4d 34 30 30 30 36 33  |....12260M400063|
00000050  39 20 20 20 32 32 30 36  32 31 20 20 00 00 00 93  |9   220621  ....|
00000060  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000070  ff ff ff ff ff ff ff ff  53 46 50 2d 54 0c 64 ff  |........SFP-T.d.|
00000080  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000090  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000a0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000b0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000c0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000d0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000e0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000f0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000100
root@turris:/usr/share/diagnostics#  ethtool eth2
Settings for eth2:
        Supported ports: [ FIBRE ]
        Supported link modes:   2500baseX/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: FIBRE
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

What do you have on the otherside of the link?

Not sure - it is ISP owned device, however with regular WAN omnia port it works fine on 1G:

    Link partner advertised link modes:  1000baseT/Half 1000baseT/Full
    Link partner advertised pause frame use: Transmit-only
    Link partner advertised auto-negotiation: Yes
    Link partner advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair

Oh, I’m glad to hear that you tried it with kernel 5.15 instead of kernel 5.10! :wink: That’s why I asked it in the first place that you should try it with Turris OS.

Anyway, you can, and you should raise the issue with OpenWrt main repository that this SFP module is not supported.

YES! You should be able to provide more logs because from the three rows, it is incredibly hard to guess what is wrong, but that’s what @b_bezak provided, and once we have time, we could look into it, but we have other priorities right now. We can not and we are not going to provide support for every SFP module, which you can find on the market.

Feel free to check Supported SFP modules [Turris wiki].

Many thanx to all of you.
Problem is sitting probably before the router (me).
I assumed it can do auto neg, and revert back to 1Gb.
It seems it can only do 2.5 Gb.
Will try it tomorrow in the office.

I will also buy a MA5671A and try it on a GPON line in the office.
Thank you all for your input, I will report back here.

1Gb Copper
root@turris:~# dmesg |grep sfp
[    8.363630] sfp sfp: Host maximum power 3.0W
[    8.687930] sfp sfp: module OEM              ES-T2-R          rev A    sn EM2TX45506       dc 221104
[   14.548978] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:16] driver [Marvell 88E1111] (irq=POLL)
root@turris:~# ethtool eth2
Settings for eth2:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                1000baseX/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                1000baseX/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 22
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

root@turris:~# ethtool --module-info eth2
        Identifier                                : 0x03 (SFP)
        Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)
        Connector                                 : 0x22 (RJ45)
        Transceiver codes                         : 0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x00 0x00
        Transceiver type                          : Ethernet: 1000BASE-T
        Encoding                                  : 0x01 (8B/10B)
        BR, Nominal                               : 1300MBd
        Rate identifier                           : 0x00 (unspecified)
        Length (SMF,km)                           : 0km
        Length (SMF)                              : 0m
        Length (50um)                             : 0m
        Length (62.5um)                           : 0m
        Length (Copper)                           : 100m
        Length (OM3)                              : 0m
        Laser wavelength                          : 0nm
        Vendor name                               : OEM
        Vendor OUI                                : 00:00:00
        Vendor PN                                 : ES-T2-R
        Vendor rev                                : A
        Option values                             : 0x00 0x10
        Option                                    : TX_DISABLE implemented
        BR margin, max                            : 0%
        BR margin, min                            : 0%
        Vendor SN                                 : EM2TX45506
        Date code                                 : 221104

2.5Gb Copper
root@turris:~# dmesg |grep sfp
[    8.224570] sfp sfp: Host maximum power 3.0W
[    8.557952] sfp sfp: module TP-LINK          TL-SM410U        rev 2.0  sn 12260M4000825    dc 220621
root@turris:~# ethtool eth2
Settings for eth2:
        Supported ports: [ FIBRE ]
        Supported link modes:   2500baseX/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

root@turris:~# ethtool --module-info eth2
        Identifier                                : 0x03 (SFP)
        Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)
        Connector                                 : 0x07 (LC)
        Transceiver codes                         : 0x00 0x00 0x00 0x00 0x00 0x00 0x40 0x00 0x00
        Transceiver type                          : FC: Twisted Pair (TP)
        Encoding                                  : 0x01 (8B/10B)
        BR, Nominal                               : 3100MBd
        Rate identifier                           : 0x00 (unspecified)
        Length (SMF,km)                           : 0km
        Length (SMF)                              : 0m
        Length (50um)                             : 0m
        Length (62.5um)                           : 0m
        Length (Copper)                           : 0m
        Length (OM3)                              : 0m
        Laser wavelength                          : 0nm
        Vendor name                               : TP-LINK
        Vendor OUI                                : 30:b5:c2
        Vendor PN                                 : TL-SM410U
        Vendor rev                                : 2.0
        Option values                             : 0x00 0x18
        Option                                    : TX_FAULT implemented
        Option                                    : TX_DISABLE implemented
        BR margin, max                            : 0%
        BR margin, min                            : 0%
        Vendor SN                                 : 12260M4000825
        Date code                                 : 220621

This is a module that works with Turris Omnia on OS 6.0 and OpenWrt snapshot if compiled with 5.15 kernel: 2.5G Sfp + Naar RJ45 moduł Koper 2.5Gb Sfp moduł RJ45 Sfp Sfp + T 2.5 gbase t Koper sfp 100M dla Cisco Mikrotik tp link d link| | - AliExpress

For unknown reasons I only on OS 6.0 had to copy -sfp.dtb and overwrite the -phy.dtb as it failed to auto-detect.

The auto-detection works fine on OpenWrt though.

1 Like

I tried my TL-SM410U connected to a 2.5 GBit copper Ethernet port (on a 2.5 Gb CPE).
Still no link :frowning:
Strange thing is the TP-Link 2.5 Gb SFP+ is shown as
root@turris:~# ethtool eth2
Settings for eth2:
Supported ports: [ FIBRE ]

Ports should be
Supported ports: [ TP MII ]
I assume.

No clue why this is detected like this.
Any ideas?

I have 2 Omnias and both have TL-SM410Us using Turris OS 6.03 with no issues running at 2.5 Gigs! One ot the TL-SM410Us reports as Rev. 1 and the other Rev. 2 fwiw.
Both initially were tested using CAT7 cable into a switch (referenced here: Are there any 2.5Gbase-T SFP modules compatible with Omnia - #50 by crapbasket]) but both also now work using CAT5e going through Motorola MoCa adapters.
Others have described issues with negotiation down to 1 Gig but it may be very much dependent upon the switch/router used. I have no need to do so myself.
But 1-Gig SFPs are a dime a dozen online!
Can you verify that you aren’t holding a defective TL-SM410U? Sometimes changing cables helps also! Have you tried connecting a PC direct to the Omnia? What version Omnia are you using?

Edit: Both show as Fibre ports - makes no diference here so far!
2nd edit: finished sentence

Thanx, very interesting that the TL-SM410U works for you.

Can you try to install ethtool and check the command below?
For me it shows port type FIBRE which is wrong, and I think this is the reason why it is not working for me.
So I would really like to compare the ethtool output.
Maybe my devices has wrong parameters in the eeprom?
I am quite new to SFP modules, so I am learning as I go.

My screen:

BusyBox v1.33.2 (2022-10-19 16:21:10 UTC) built-in shell (ash)

  ______                _         ____  _____
 /_  __/_  ____________(_)____   / __ \/ ___/
  / / / / / / ___/ ___/ / ___/  / / / /\__
 / / / /_/ / /  / /  / (__  )  / /_/ /___/ /
/_/  \__,_/_/  /_/  /_/____/   \____//____/

TurrisOS 6.0.3, Turris Omnia

root@turris:~# ethtool eth2
Settings for eth2:
Supported ports: [ FIBRE ]
Supported link modes: 2500baseX/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: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Link detected: yes
root@turris:~#

As I already mentioned I doubt that the [ FIBRE ] matters to the Omnia, or at least not mine! It might matter on the other end of the cable perhaps? Are you getting all the same output as me except for link detection?

Be aware that while my 1st Omnia was set up with the TL-SM410U using HBL status OS v6, both it & my newer unit rec’d couple days ago were flashed with fresh (USB loaded) OS installs with HBS OS 6.0.3. Everything auto-configured without issue. If you can afford to start fresh it might be worthwhile to rule out oddball setting quirks. Also I so far only have my units set up as WiFi access points each using only AW7915-NP1 cards and the SFPs. All of the other interfaces are disabled.
I’d say unless your TL-SM410U has a hidden defect then your issue likely lies elsewhere!

Many, many thanx.
I reflashed a few days ago from OpenWRT to Turris 6.0.3.

Yes, the output is exactly identical except for the link detected.
So the good news is it SHOULD work.
Might indeed be that my SFP is defective, but it is great to know that the exact same setup is working for others.