Supported SFP modules

joining the select group of wan via sfp omnia operators - gpon via Technicolor AFM0002 module (thanks to @lucenera for documenting it)
connected via telnet/ssh to 192.168.2.1 (you need to add secondary ip ifconfig eth2:0 192.168.2.2 netmask 255.255.255.0) ssh u/p admin/system, telnet no u/p then via diag menu I’ve changed the S/N to my ZTE OLT’s one and after omnia reboot it automagically started pppoe

1 Like

Joining the SFP group as well - GPON FS GSFP-43-20B.

I am uncertain how to get the device to use the SFP port for WAN. Someone mentioned running an “SFP to WAN” command, but did not provide the command itself. Can anyone offer me some guidance here?

Would love to keep using this router, but if I can’t get the SFP port working I think I may be out of luck with my new ISP - their gateway refuses to be bridged.

Thanks in advance!

Hello, is the device detected by the router?
Can you please plug it in and send us the output of dmesg command?

The router is refusing to let me log in via SSH.

First I had to dump the old ECDSA key stored by my computer, now it’s giving me this message:

root@192.168.1.1's password:
channel 0: open failed: connect failed: open failed
stdio forwarding failed
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535

I’m at a loss what to do here…

Do you run the minipot service? Are you able to log in through the web?

I used to, but gave the router a full factory reset,

I can log into the web interface (Foris 100.5) normally.

Hello!

Here is my experience:
Visual Online (Luxembourg ISP) installed a FTTH service with TP-Link MC220L which has a SBU35020GE0B / SFP / 1000Base-BXU .

Reboot, and the inbuilt netmetr confirms that everything works as expected:

Measurement detail

Download 605.314 Mb/s
Upload 322.000 Mb/s

Here is the log:

root@turris:~# dmesg | grep sfp
[ 12.805078] sfp sfp: module Skylane Optics SBU35020GE0B493 rev A sn 2AF2B10171 dc 30-04-21
[ 12.814422] sfp sfp: LC connector, encoding 8b10b, nominal bitrate 1.3Gbps +0% -0%
[ 12.822234] sfp sfp: 1000BaseSX- 1000BaseLX+ 1000BaseCX- 1000BaseT- 100BaseTLX- 1000BaseFX- BaseBX10- BasePX-
[ 12.832350] sfp sfp: 10GBaseSR- 10GBaseLR- 10GBaseLRM- 10GBaseER-
[ 12.838631] sfp sfp: Wavelength 1310nm, fiber lengths:
[ 12.843959] sfp sfp: 9µm SM : 20000m
[ 12.848237] sfp sfp: 62.5µm MM OM1: unsupported/unspecified
[ 12.853998] sfp sfp: 50µm MM OM2: unsupported/unspecified
[ 12.859756] sfp sfp: 50µm MM OM3: unsupported/unspecified
[ 12.865518] sfp sfp: 50µm MM OM4: unsupported/unspecified
[ 12.871278] sfp sfp: Options: txdisable, txfault, los+
[ 12.876605] sfp sfp: Diagnostics: ddm, intcal, rxpwravg

root@turris:~# cat /etc/openwrt_*
DISTRIB_ID=‘TurrisOS’
DISTRIB_RELEASE=‘5.3.0’
DISTRIB_REVISION=‘r11382+91-5e8b9624f1’
DISTRIB_TARGET=‘mvebu/cortexa9’
DISTRIB_ARCH=‘arm_cortex-a9_vfpv3-d16’
DISTRIB_DESCRIPTION=‘TurrisOS 5.3.0 5e8b9624f1791d193e8d5e007ce4c873454f014a’
DISTRIB_TAINTS=‘busybox’
5e8b9624f1791d193e8d5e007ce4c873454f014a

root@turris:~# cat /etc/os-release
NAME=“TurrisOS”
VERSION=“5.3.0”
ID=“turrisos”
ID_LIKE=“lede openwrt”
PRETTY_NAME=“TurrisOS 5.3.0”
VERSION_ID=“5.3.0”
HOME_URL=“https://www.turris.cz/
BUG_URL=“Issues · Turris · GitLab
SUPPORT_URL=“https://www.turris.cz/support/
BUILD_ID=“r11382+91-5e8b9624f1”
OPENWRT_BOARD=“mvebu/cortexa9”
OPENWRT_ARCH=“arm_cortex-a9_vfpv3-d16”
OPENWRT_TAINTS=“busybox”
OPENWRT_DEVICE_MANUFACTURER=“CZ.NIC”
OPENWRT_DEVICE_MANUFACTURER_URL=“https://www.turris.cz/
OPENWRT_DEVICE_PRODUCT=“Turris Omnia”
OPENWRT_DEVICE_REVISION=“v0”
OPENWRT_RELEASE=“TurrisOS 5.3.0 5e8b9624f1791d193e8d5e007ce4c873454f014a”

1 Like

With a little bit of delay, it’s a pleasure to let you know that Turris SFP+ module arrived and are available to buy! :wink:

4 Likes

Sweet!
Will that work in the mox as well?

Can you provide any details?

What details do you need? It is 2.5Gbit/s SFP module. Or am I missing something?

Yes. We tested our Turris SFP module on these following routers: Turris Omnia and Turris MOX.

5 Likes

Here you go!

dmesg

[    7.754303] sfp sfp: module Turris           RTSFP-10         rev A    sn 2009040047       dc 200928
[   42.382982] mv88x3310 i2c:sfp:11: Firmware version 0.2.8.0
[   43.063015] mvneta f1034000.ethernet eth2: interfaces=[mac=4,8-11,16,18-19 phy=4,18-22] selected 19 (2500base-x)
[   43.073225] mvneta f1034000.ethernet eth2: switched to inband/2500base-x link mode
[   43.080822] mv88x3310 i2c:sfp:11: selected MAC type: 4
[   43.682996] mvneta f1034000.ethernet eth2: PHY [i2c:sfp:11] driver [mv88x3310] (irq=POLL)
[   49.862214] mvneta f1034000.ethernet eth2: Link is Up - 2.5Gbps/Full - flow control rx/tx
[   49.870430] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

ethtool

root@turris:/# ethtool eth2
Settings for eth2:
        Supported ports: [ ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/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
                                2500baseT/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
                                             2500baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 17
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

iperf3 tests

root@turris:/# iperf3 -s
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 192.0.2.2, port 41204
[  5] local 192.0.2.1 port 5201 connected to 192.0.2.2 port 41206
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   277 MBytes  2.32 Gbits/sec
[  5]   1.00-2.00   sec   278 MBytes  2.33 Gbits/sec
[  5]   2.00-3.00   sec   280 MBytes  2.35 Gbits/sec
[  5]   3.00-4.00   sec   276 MBytes  2.32 Gbits/sec
[  5]   4.00-5.00   sec   277 MBytes  2.33 Gbits/sec
[  5]   5.00-6.00   sec   280 MBytes  2.35 Gbits/sec
[  5]   6.00-7.00   sec   279 MBytes  2.34 Gbits/sec
[  5]   7.00-8.00   sec   279 MBytes  2.34 Gbits/sec
[  5]   8.00-9.00   sec   278 MBytes  2.33 Gbits/sec
[  5]   9.00-10.00  sec   280 MBytes  2.35 Gbits/sec
[  5]  10.00-10.01  sec  2.08 MBytes  2.31 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.01  sec  2.72 GBytes  2.34 Gbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------
Accepted connection from 192.0.2.2, port 41208
[  5] local 192.0.2.1 port 5201 connected to 192.0.2.2 port 41210
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   282 MBytes  2.36 Gbits/sec    0    956 KBytes
[  5]   1.00-2.01   sec   279 MBytes  2.32 Gbits/sec    0   1.09 MBytes
[  5]   2.01-3.00   sec   280 MBytes  2.37 Gbits/sec    0   1.15 MBytes
[  5]   3.00-4.00   sec   281 MBytes  2.35 Gbits/sec    0   1.21 MBytes
[  5]   4.00-5.00   sec   280 MBytes  2.35 Gbits/sec    0   1.27 MBytes
[  5]   5.00-6.00   sec   280 MBytes  2.35 Gbits/sec    0   1.34 MBytes
[  5]   6.00-7.00   sec   276 MBytes  2.32 Gbits/sec    0   1.34 MBytes
[  5]   7.00-8.00   sec   279 MBytes  2.34 Gbits/sec    0   1.40 MBytes
[  5]   8.00-9.00   sec   279 MBytes  2.34 Gbits/sec    0   1.40 MBytes
[  5]   9.00-10.00  sec   279 MBytes  2.34 Gbits/sec    0   1.40 MBytes
[  5]  10.00-10.00  sec  1.25 MBytes  2.71 Gbits/sec    0   1.40 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  2.73 GBytes  2.34 Gbits/sec    0             sender

Testbed (sorry for the chaos on my desk)

6 Likes

Thank you @hagrid! Very good job! What exactly is the type of used chipset?

IPv6 is DA SHIT :pray: :love_you_gesture:

Nice

1 Like

New SFP support are coming!

1 Like

I have the Turris 2.5G SFP module but can’t change auto nego as 2500 is not in the supported and advertised lists
Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 10baseT/Full
100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Full
100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Full
Port: MII
PHYAD: 22
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Link detected: yes

Please bear with me, if I missed the relevant post, but how can I attach a TO or MOX to a SFP±port, for example a Intel 82599 or a Mikrotik CRS309 (so using fibre modules+cabling)?

  • are there any tested 2,5GBE-modules available (not stated in official wiki)?
  • which DAC (active or passive) could be used?

If buying a RTROM01-RTSF-10G (so using copper instead of fibre) one would

  • pay ~80€ + need to buy an additional S+RJ10 at ~60€ compared to ~20-40€ for a DAC-cable
  • have a worse power consumption + heat dissipation

So this obviously doesn’t seem the best solution…

only 2.5gbps is supported by current hardware.

1 Like

Thanks, I corrected that. The question stays the same - are there only considerations for using the full speed provided by the port with copper RJ45?