SFP HALNY HL-GSFP GPON not connecting - Turris Omnia HBS [6.2.4]

Omnia hardware Omnia HW help
#1

Cheers
I have the “black” Omnia. I’m currently using CETIN (for CZ/SK readers) FTTH connection with media convertor to copper. So I bought the HALNY SFP module. However I cannot make it work even though I went through the forum.
Because of the connection I have another device eth2.848 on which I created another WAN PPoE interface (keeping the WAN in case I need to fall back). On copper, everything is working just fine.

ethtool

[ 1.816570] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:6a:93
[ 13.117706] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[ 13.127510] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode
[ 16.247135] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 16.256693] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 16.266486] IPv6: ADDRCONF(NETDEV_CHANGE): eth2.848: link becomes ready

So I created symlink
root@omnia:~# readlink /boot/dtb

/boot/armada-385-turris-omnia-sfp.dtb

and rebooted
SFP seems to be recognized (?)
root@omnia:~# dmesg | grep sfp

[ 7.806825] sfp sfp: Host maximum power 3.0W
[ 8.147917] sfp sfp: module HALNy HL-GSFP rev V1.0 sn HALN10104289 dc 20150525

but eth2 is still using the MAC of copper and not MAC of SFP → link is down and connection is not working :frowning:
root@omnia:~# dmesg | grep eth

[ 1.784676] mvneta f1070000.ethernet eth0: Using device tree mac address d8:58:d7:00:6a:93
[ 1.794218] mvneta f1030000.ethernet eth1: Using hardware mac address d8:58:d7:00:6a:92
[ 1.803503] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:6a:93
[ 8.156307] mvneta f1034000.ethernet eth2: switched to inband/1000base-x link mode
[ 12.186663] mvneta f1030000.ethernet eth1: configuring for fixed/rgmii link mode
[ 12.194611] mvneta f1030000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 12.206830] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 12.322665] device eth1 entered promiscuous mode
[ 13.085949] mvneta f1034000.ethernet eth2: configuring for inband/1000base-x link mode
[ 13.146811] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 13.154868] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 13.161384] IPv6: ADDRCONF(NETDEV_CHANGE): eth2.848: link becomes ready
[ 38.571629] mvneta f1034000.ethernet eth2: Link is Down
[ 38.584332] mvneta f1034000.ethernet eth2: configuring for inband/1000base-x link mode
[ 38.627455] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 38.635540] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 38.642136] IPv6: ADDRCONF(NETDEV_CHANGE): eth2.848: link becomes ready

#2

I am using Halny stick and it works. The WAN connection on eth2 is one of the two. Try disconnecting copper and rebooting. The MAC address could be the same for copper and fiber. Also try soft rebooting two times in a row to be sure. I got a problem that link was not getting up after power failures and I had to reboot again to get it to work

#3

Also try to ask your ISP to register the stick on their side. I got mine from my ISP already configured. You have to set some GPON specific parts for it to work.