Omnia Turris 4.0.1 SFP doesn't work

Software SW help
41

It blinks when synchronising with the remote ATM, steady when synchronised. As per devices specification sheet it is labelled as LED 1 (CO / CPE indicator)

CO = Central Office
CPE = Customer Premises Equipment

indicates power status and traffic flow, as per devices specification sheet it is labelled as LED 2 (PWR / Link Status indicator)

There is no difference in the device setup, not sure about the subsciber line, as far as I know my end is all the way copper from the ATM to the TAE.

Curiously the latest boot log is now also exhibitng 802.3z on this node

kernel: [ 4.434370] mvneta f1034000.ethernet eth2: Using hardware mac address d8:58:d7:00:79:7b
kernel: [ 5.332663] sfp sfp: module ALLNET ALL4781 rev V3.4 sn 0000000FC9157640 dc 29-03-18
kernel: [ 5.342001] sfp sfp: unknown connector, encoding 8b10b, nominal bitrate 1.3Gbps +0% -0%
kernel: [ 5.350199] sfp sfp: 1000BaseSX+ 1000BaseLX- 1000BaseCX- 1000BaseT- 100BaseTLX- 1000BaseFX- BaseBX10- BasePX-
kernel: [ 5.360314] sfp sfp: 10GBaseSR- 10GBaseLR- 10GBaseLRM- 10GBaseER-
kernel: [ 5.366598] sfp sfp: Wavelength 0nm, fiber lengths:
kernel: [ 5.371663] sfp sfp: 9µm SM : unsupported
kernel: [ 5.376377] sfp sfp: 62.5µm MM OM1: unsupported/unspecified
kernel: [ 5.382137] sfp sfp: 50µm MM OM2: unsupported/unspecified
kernel: [ 5.387896] sfp sfp: 50µm MM OM3: unsupported/unspecified
kernel: [ 5.393658] sfp sfp: 50µm MM OM4: 2.540km
kernel: [ 5.398024] sfp sfp: Options: retimer
kernel: [ 5.401870] sfp sfp: Diagnostics:
kernel: [ 5.405457] mvneta f1034000.ethernet eth2: switched to 802.3z/1000base-x link mode
kernel: [ 40.922996] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
kernel: [ 41.231425] sfp sfp: module transmit fault indicated
kernel: [ 43.981411] sfp sfp: module transmit fault recovered
kernel: [ 43.981446] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
kernel: [ 44.207401] mvneta f1034000.ethernet eth2: Link is Down
kernel: [ 44.207416] sfp sfp: module transmit fault indicated
kernel: [ 45.581413] sfp sfp: module transmit fault recovered
kernel: [ 45.581440] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
netifd: Interface ‘wan’ is now down
kernel: [ 49.808007] mvneta f1034000.ethernet eth2: Link is Down
netifd: Interface ‘wan’ is disabled
netifd: Interface ‘wan’ is enabled
netifd: Interface ‘wan’ is setting up now
kernel: [ 49.816437] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
kernel: [ 49.817306] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
kernel: [ 49.817359] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
insmod: module is already loaded - slhc
insmod: module is already loaded - ppp_generic
insmod: module is already loaded - pppox
insmod: module is already loaded - pppoe
pppd[6730]: Plugin rp-pppoe.so loaded.
pppd[6730]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
pppd[6730]: pppd 2.4.7 started by root, uid 0
pppd[6730]: Timeout waiting for PADO packets
pppd[6730]: Unable to complete PPPoE Discovery
pppd[6730]: Exit.
netifd: Interface ‘wan’ is now down
kernel: [ 65.063964] mvneta f1034000.ethernet eth2: Link is Down
netifd: Interface ‘wan’ is disabled
netifd: Interface ‘wan’ is enabled
netifd: Interface ‘wan’ is setting up now
kernel: [ 65.074543] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
kernel: [ 65.075414] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
kernel: [ 65.075471] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
insmod: module is already loaded - slhc
insmod: module is already loaded - ppp_generic
insmod: module is already loaded - pppox
insmod: module is already loaded - pppoe
pppd[7797]: Plugin rp-pppoe.so loaded.
pppd[7797]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
pppd[7797]: pppd 2.4.7 started by root, uid 0
pppd[7797]: Timeout waiting for PADO packets
pppd[7797]: Unable to complete PPPoE Discovery
pppd[7797]: Exit.
netifd: Interface ‘wan’ is now down
kernel: [ 80.342706] mvneta f1034000.ethernet eth2: Link is Down
kernel: [ 80.354586] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
kernel: [ 80.355355] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
kernel: [ 80.355412] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
netifd: Interface ‘wan’ is disabled
netifd: Interface ‘wan’ is enabled
netifd: Interface ‘wan’ is setting up now
insmod: module is already loaded - slhc
insmod: module is already loaded - ppp_generic
insmod: module is already loaded - pppox
insmod: module is already loaded - pppoe
pppd[7934]: Plugin rp-pppoe.so loaded.
pppd[7934]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
pppd[7934]: pppd 2.4.7 started by root, uid 0
pppd[7934]: Timeout waiting for PADO packets
pppd[7934]: Unable to complete PPPoE Discovery
pppd[7934]: Exit.
netifd: Interface ‘wan’ is now down
netifd: Interface ‘wan’ is disabled
kernel: [ 95.651395] mvneta f1034000.ethernet eth2: Link is Down
kernel: [ 95.660530] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
kernel: [ 95.661515] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
kernel: [ 95.661581] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
netifd: Interface ‘wan’ is enabled
netifd: Interface ‘wan’ is setting up now
insmod: module is already loaded - slhc
insmod: module is already loaded - ppp_generic
insmod: module is already loaded - pppox
insmod: module is already loaded - pppoe
pppd[8060]: Plugin rp-pppoe.so loaded.
pppd[8060]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
pppd[8060]: pppd 2.4.7 started by root, uid 0
pppd[8060]: PPP session is 19718
pppd[8060]: Connected to e0:ac:f1:65:51:ba via interface eth2
kernel: [ 96.278783] pppoe-wan: renamed from ppp0
pppd[8060]: Renamed interface ppp0 to pppoe-wan
pppd[8060]: Using interface pppoe-wan
pppd[8060]: Connect: pppoe-wan ↔ eth2
pppd[8060]: PAP authentication succeeded
pppd[8060]: peer from calling number E0:AC:F1:65:51:BA authorized
pppd[8060]: local IP address xxx.101.215.xxx
pppd[8060]: remote IP address xxx.46.104.xxx
pppd[8060]: primary DNS address xxx.209.104.xxx
pppd[8060]: secondary DNS address xxx.209.104.xxx
netifd: Network device ‘pppoe-wan’ link is up
netifd: Interface ‘wan’ is now up

Appears to be working my end, maybe you need check the logs on you node again and compare to the log just posted above.

For more insight of what happens under the hood you may have a look here

42

Thank you very much for your detailed thoughts.

Unfortunately there is still no connection.

Could you post your /etc/config/network here would help a lot to understand where my error is.
If possible your LUCI interfaces overview

Thank you very much for your help and effort.

43

Could you check with ip -d -s -h l sh eth2 that the physical link is up indeed?

on this node prints 
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1024
    link/ether d8:58:d7:00:79:7b brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 9676 addrgenmode stable_secret numtxqueues 8 numrxqueues 8 gso_max_size 65536 gso_max_segs 100
    RX: bytes  packets  errors  dropped overrun mcast
    101M       150k     0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    24.5M      161k     0       0       0       0

Or with mii-tool -v eth2 (requires mii-tool package installed)

on this node prints 
eth2: 1000 Mbit, full duplex, link ok
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, full duplex
  basic status: autonegotiation complete, link ok
  capabilities:
  advertising:  1000baseT-HD 1000baseT-FD 100baseT4 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

If the physical link status is UP | OK then there might be indeed some issue with the network a/o firewall config but then it would be expected to show errors in the syslog - could you check for:

  • sfp: module transmit fault indicated
  • anything related to pppd

?

Also check that the firewall settings permit for proper exhange of data necessary with the ISP

What is the setup with the ISP subscriber line, aside from

  • PPPoE authentication?
  • VLAN tag required?
  • ipv4 only, ipv6 only, ipv4|6 tunnelling e.g. ds-lite?
  • dynamic or static ip?

Not sure whether it helps but here here you go:

wan conf 
config interface 'wan'
	option ifname 'eth2'
	option proto 'pppoe'
	option username 'user name'
	option password 'password'
	option peerdns '0'
	option keepalive '6 10'
	option ipv6 'auto'
LuCI screen shot

Untitled
Untitled1238×566 70.6 KB

44

Thank you very much for your hints. I tried it immediately.
ip -d -s -h l sh eth2 produced the following

node prints 
root@turris:~# ip -d -s -h l sh eth2
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 532
    link/ether d8:58:d7:00:ad:0b brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 8 numrxqueues 8 gso_max_size 65536 gso_max_segs 100
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    11.1k      118      0       0       0       0

mii-tool -v eth2 produced the following

node 
root@turris:~# mii-tool -v eth2
eth2: 1000 Mbit, full duplex, link ok
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, full duplex
  basic status: autonegotiation complete, link ok
  capabilities:
  advertising:  1000baseT-HD 1000baseT-FD 100baseT4 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

Your thoughts regarding the ISP subscriber line then led me to these specifications of ISP (1und1)

  • ISP: 1und1/versatel
  • They use VLAN ID 7.
  • ipv4 ipv6 Tunnel is ds-lite

Changed eth2 to vlan eth2.7 and ALLNET ALL4781-VDSL2-SFP starts connecting to the Internet.
I thought nice everything works as thought but after about 5min the connection breaks came as already described in user-experience-allnet-all4781-vdsl2-sfp-switch-modul

Somehow I suspect this ipv4/ip6 tunneling via ds-lite as cause for the errors.

/etc/config/network

config interface ‘wan’
option proto ‘pppoe’
option keepalive ‘6 10’
option ifname ‘eth2.7’
option password ’ ’
option delegate ‘0’
option peerdns ‘0’
option ipv6 ‘auto’
option username ’ ’

config interface ‘wan6’
option ifname ‘@wan’
option proto ‘dhcp’
option auto ‘0’

I think i have to change the ipv6-Settings to ds-lite but i am not quite sure how to do this.
@anon50890781 do you have kindly some further advices.

45

That can be deleted since the network manager is supposed to spawn the other ifaces - if you like please read this thread DSLite Issues after upgrade to 4.0.1 - SW help - Turris forum where it is explained. See also the LuCI screenshot I posted as per your request.

If the network is up with the those ifaces (see LuCI screenshot) and the IPs assigned from the ISP then you should have ds-lite connectivity.

You could run from the cli check_connection to check whether ipv4|6 is working.

It would require more information to troubleshoot that, e.g. what is the systemlog printing in the event of connectivity loss.

You could also try adding option keepalive '6 10' to the config of the WAN iface.