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
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.
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
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! 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.
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
I tried my TL-SM410U connected to a 2.5 GBit copper Ethernet port (on a 2.5 Gb CPE).
Still no link
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.
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.
Addition:
I tried a Huawei MA5671A GPON SFP, and that works out of the box.
I have a 2500 MBit/s sync, and it works. (you need to whitelist the S/N of the SFP in the GPON system for it to connect.)
Might help some people who find this thread.
root@turris:~# ethtool eth2
Settings for eth2:
Supported ports: [ FIBRE ]
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: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Link detected: yes
That’s why I asked it in the first place that you should try it with Turris OS.