Fiber7 (Switzerland) SFP Compatibility


#1

Hello

I’ve received my Turris Omnia on Friday and use it for Fiber7 by Init7, a Swiss ISP which offers symmetric 1 GBit/s.

Unfortunately, I was not (yet) able to make the SFP work so I still have to rely on the TP-LINK MC220L Media Converter which I’ve used so far in conjunction with an Asus AC-RT66U router.

My current SFP Module reads as follows:

  • flexOptix
  • DDM
  • BIDI LX
  • S.B131.10.DL
  • TX 1310 / RX / 1550nm
  • 1.25GBit/s
  • 10km
  • 12dB

According to Fiber7, compatible customer equipment has to support the following:

1 Gigabit Singlefiber SFP Transceiver (10km / TX1310 / RX1550)

https://www.fiber7.ch/de/fiber7-technologie/fiber7-hardware/ (scroll all the way to the bottom of the page)

Is this module compatible with the Turris Omnia, and if so, what do I have to make it work in the router?

Thank you for your support
Mario


Flexoptic / Init7 - Fiber7
Flexoptic / Init7 - Fiber7
#2

I’m running into the same issue.

The symptom is that the link keeps flapping:

dmesg:
[ 37.073920] mvneta f1034000.ethernet eth1: Link is Down
[ 38.070734] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 45.073921] mvneta f1034000.ethernet eth1: Link is Down
[ 46.070726] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 48.073921] mvneta f1034000.ethernet eth1: Link is Down
[ 49.070726] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 51.073921] mvneta f1034000.ethernet eth1: Link is Down
[…]

/var/log/messages:
2016-10-10T19:34:22+02:00 emerg turris[]: Router Turris successfully started.
2016-10-10T19:34:22+02:00 info procd[]: - init complete -
2016-10-10T19:34:22+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-10T19:34:22+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-10T21:34:22+02:00 info kernel[]: [ 45.073921] mvneta f1034000.ethernet eth1: Link is Down
2016-10-10T19:34:22+02:00 notice netifd[]: wan (2440): Received SIGTERM
2016-10-10T19:34:23+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-10T19:34:23+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-10T19:34:23+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-10T21:34:23+02:00 info kernel[]: [ 46.070726] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-10T19:34:23+02:00 notice netifd[]: wan (2667): udhcpc (v1.23.2) started
2016-10-10T19:34:23+02:00 notice netifd[]: wan (2667): Sending discover…
2016-10-10T19:34:25+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-10T19:34:25+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-10T21:34:25+02:00 info kernel[]: [ 48.073921] mvneta f1034000.ethernet eth1: Link is Down
2016-10-10T19:34:25+02:00 notice netifd[]: wan (2667): Received SIGTERM
2016-10-10T19:34:26+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-10T19:34:26+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-10T19:34:26+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-10T21:34:26+02:00 info kernel[]: [ 49.070726] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-10T19:34:26+02:00 notice netifd[]: wan (2682): udhcpc (v1.23.2) started
2016-10-10T19:34:26+02:00 notice netifd[]: wan (2682): Sending discover…
2016-10-10T19:34:28+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-10T19:34:28+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
[…]


#3

Quick Question: Your SFP Transceiver gets eth1 assigned by the Turris Omnia software once plugged in?


#4

Yes, AFAICT the SFP transceiver is eth1.


#5

Could it be the other end is expecting some kind of authentication handshake? No authentication + traffic -> link reset? PPP required?


#6

Ok, I’m home now and ran some more tests to capture my log output:

  1. Unplug ethernet cable from Turris Omnia WAN port (the cable was connected to the TP-LINK MC220L)
  2. Unplug fibre cable from SFP transceiver
  3. Unplug SFP transceiver from TP-LINK MC220L (hot!)
  4. Plug SFP transceiver into Turris Omnia SFP port
  5. Plug fibre cable into SFP transceiver

Here’s the log output:

dmesg

[99329.680254] mvneta f1034000.ethernet eth1: Link is Down
[99352.349313] br-lan: port 2(eth2) entered disabled state
[99352.354578] br-lan: port 1(eth0) entered disabled state
[99352.371208] device eth0 left promiscuous mode
[99352.375609] br-lan: port 1(eth0) entered disabled state
[99352.390280] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[99352.397765] device eth2 left promiscuous mode
[99352.402188] br-lan: port 2(eth2) entered disabled state
[99352.416448] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[99352.424105] device br-lan left promiscuous mode
[99354.063461] device eth0 entered promiscuous mode
[99354.069203] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[99354.083984] device eth2 entered promiscuous mode
[99354.095605] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[99356.055885] mvneta f1030000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[99356.063754] br-lan: port 1(eth0) entered forwarding state
[99356.069192] br-lan: port 1(eth0) entered forwarding state
[99356.074725] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[99356.081342] mvneta f1070000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
[99356.089226] br-lan: port 2(eth2) entered forwarding state
[99356.094647] br-lan: port 2(eth2) entered forwarding state
[99358.065870] br-lan: port 1(eth0) entered forwarding state
[99358.085872] br-lan: port 2(eth2) entered forwarding state
[99361.095882] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[99361.103747] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[99376.099079] mvneta f1034000.ethernet eth1: Link is Down
[99380.095883] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off

/var/log/messages

2016-10-10T21:58:42+02:00 notice netifd[]: Network device 'eth1' link is down
2016-10-10T21:58:42+02:00 notice netifd[]: Network alias 'eth1' link is down
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan6' has link connectivity loss
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan6' is now down
2016-10-10T23:58:42+02:00 info kernel[]: [99329.680254] mvneta f1034000.ethernet eth1: Link is Down
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan6' is disabled
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan6' is enabled
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan' has link connectivity loss
2016-10-10T21:58:42+02:00 notice netifd[]: Interface 'wan6' is disabled
2016-10-10T21:58:42+02:00 notice netifd[]: wan (4784): Received SIGTERM
2016-10-10T21:58:42+02:00 notice root[]: stopping ntpclient
2016-10-10T21:58:43+02:00 warning ucollect[23612]: epoll_wait on 4 interrupted, retry
2016-10-10T21:58:43+02:00 info ucollect[23612]: Reconfiguring
2016-10-10T21:58:43+02:00 info ucollect[23612]: Loading plugin library libpluglib_ucollect_diffstore_1.2.so
2016-10-10T23:58:43+02:00 info ucollect[]: Last message 'Loading plugin libra' repeated 1 times, supressed by syslog-ng on TURRIS-OMNIA
2016-10-10T21:58:43+02:00 info ucollect[23612]: Closing both PCAPs on eth1
2016-10-10T21:58:43+02:00 info ucollect[23612]: Sending login credentials enabled
2016-10-10T21:58:43+02:00 info ucollect[23612]: Unloading plugin library
2016-10-10T23:58:43+02:00 info ucollect[]: Last message 'Unloading plugin lib' repeated 1 times, supressed by syslog-ng on TURRIS-OMNIA
2016-10-10T21:58:43+02:00 notice ddns-scripts[11388]: myddns_ipv4: PID '11388' terminated by 'SIGTERM' at 2016-10-10 23:58
2016-10-10T21:59:01+02:00 info cron[19474]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]: sfpflt change detected: 0
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]: sfpdet change detected: 0
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]: I2C read: 0x40
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]:
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]: Switching mode to phy-sfp.
2016-10-10T21:59:03+02:00 info sfpswitch.py[1444]: Switch success.
2016-10-10T21:59:05+02:00 info sfpswitch.py[1444]: Restarting net with command ip link set down dev eth1; /etc/init.d/network restart
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'lan' is now down
2016-10-10T23:59:05+02:00 info kernel[]: [99352.349313] br-lan: port 2(eth2) entered disabled state
2016-10-10T23:59:05+02:00 info kernel[]: [99352.354578] br-lan: port 1(eth0) entered disabled state
2016-10-10T21:59:05+02:00 err lcollect[23825]: Error reading packets from PCAP on br-lan (The interface went down)
2016-10-10T23:59:05+02:00 err lcollect[]: Last message 'Error reading packet' repeated 1 times, supressed by syslog-ng on TURRIS-OMNIA
2016-10-10T21:59:05+02:00 warning lcollect[23825]: epoll_wait on 5 interrupted, retry
2016-10-10T21:59:05+02:00 info lcollect[23825]: Reconfiguring
2016-10-10T23:59:05+02:00 info kernel[]: [99352.371208] device eth0 left promiscuous mode
2016-10-10T23:59:05+02:00 info kernel[]: [99352.375609] br-lan: port 1(eth0) entered disabled state
2016-10-10T23:59:05+02:00 info kernel[]: [99352.390280] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
2016-10-10T23:59:05+02:00 info kernel[]: [99352.397765] device eth2 left promiscuous mode
2016-10-10T23:59:05+02:00 info kernel[]: [99352.402188] br-lan: port 2(eth2) entered disabled state
2016-10-10T23:59:05+02:00 info kernel[]: [99352.416448] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
2016-10-10T23:59:05+02:00 info kernel[]: [99352.424105] device br-lan left promiscuous mode
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'lan' is disabled
2016-10-10T21:59:05+02:00 notice netifd[]: Network device 'eth2' link is down
2016-10-10T21:59:05+02:00 notice netifd[]: Network device 'eth0' link is down
2016-10-10T21:59:05+02:00 notice netifd[]: Bridge 'br-lan' link is down
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'lan' has link connectivity loss
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'loopback' is now down
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'loopback' is disabled
2016-10-10T21:59:05+02:00 notice netifd[]: Network device 'lo' link is down
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'loopback' has link connectivity loss
2016-10-10T21:59:05+02:00 notice netifd[]: Interface 'wan' is disabled
2016-10-10T21:59:06+02:00 emerg sfpswitch.py[1444]: 'radio0' is disabled
2016-10-10T21:59:06+02:00 emerg sfpswitch.py[1444]: 'radio1' is disabled
2016-10-10T21:59:06+02:00 emerg sfpswitch.py[1444]: 'radio0' is disabled
2016-10-10T21:59:06+02:00 emerg sfpswitch.py[1444]: 'radio1' is disabled
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'lan' is enabled
2016-10-10T23:59:07+02:00 info kernel[]: [99354.063461] device eth0 entered promiscuous mode
2016-10-10T23:59:07+02:00 info kernel[]: [99354.069203] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'lan' is setting up now
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'lan' is now up
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'loopback' is enabled
2016-10-10T23:59:07+02:00 info kernel[]: [99354.083984] device eth2 entered promiscuous mode
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'loopback' is setting up now
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'loopback' is now up
2016-10-10T23:59:07+02:00 info kernel[]: [99354.095605] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'wan' is enabled
2016-10-10T21:59:07+02:00 notice netifd[]: Network device 'lo' link is up
2016-10-10T21:59:07+02:00 notice netifd[]: Interface 'loopback' has link connectivity
2016-10-10T21:59:07+02:00 notice firewall[]: Reloading firewall due to ifup of lan (br-lan)
2016-10-10T21:59:07+02:00 err turris-firewall-rules[]: (v61) Unable to determine the WAN interface. Exiting...
2016-10-10T23:59:09+02:00 info kernel[]: [99356.055885] mvneta f1030000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
2016-10-10T23:59:09+02:00 info kernel[]: [99356.063754] br-lan: port 1(eth0) entered forwarding state
2016-10-10T23:59:09+02:00 info kernel[]: [99356.069192] br-lan: port 1(eth0) entered forwarding state
2016-10-10T23:59:09+02:00 info kernel[]: [99356.074725] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
2016-10-10T21:59:09+02:00 notice netifd[]: Network device 'eth0' link is up
2016-10-10T21:59:09+02:00 notice netifd[]: Bridge 'br-lan' link is up
2016-10-10T21:59:09+02:00 notice netifd[]: Interface 'lan' has link connectivity
2016-10-10T23:59:09+02:00 info kernel[]: [99356.081342] mvneta f1070000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
2016-10-10T21:59:09+02:00 notice netifd[]: Network device 'eth2' link is up
2016-10-10T23:59:09+02:00 info kernel[]: [99356.089226] br-lan: port 2(eth2) entered forwarding state
2016-10-10T23:59:09+02:00 info kernel[]: [99356.094647] br-lan: port 2(eth2) entered forwarding state
2016-10-10T23:59:11+02:00 info kernel[]: [99358.065870] br-lan: port 1(eth0) entered forwarding state
2016-10-10T23:59:11+02:00 info kernel[]: [99358.085872] br-lan: port 2(eth2) entered forwarding state
2016-10-10T21:59:12+02:00 info sfpswitch.py[1444]: sfplos change detected: 0
2016-10-10T23:59:14+02:00 info kernel[]: [99361.095882] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-10T23:59:14+02:00 info kernel[]: [99361.103747] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
2016-10-10T21:59:14+02:00 notice netifd[]: Network device 'eth1' link is up
2016-10-10T21:59:14+02:00 notice netifd[]: Interface 'wan' has link connectivity
2016-10-10T21:59:14+02:00 notice netifd[]: Interface 'wan' is setting up now
2016-10-10T21:59:14+02:00 notice netifd[]: wan (20015): udhcpc (v1.23.2) started
2016-10-10T21:59:14+02:00 notice netifd[]: wan (20015): Sending discover...
2016-10-10T23:59:20+02:00 notice netifd[]: Last message 'wan (20015): Sending' repeated 1 times, supressed by syslog-ng on TURRIS-OMNIA
2016-10-10T21:59:20+02:00 notice netifd[]: wan (20015): Sending discover...
2016-10-10T23:59:27+02:00 info dnsmasq[5091]: exiting on receipt of SIGTERM
2016-10-10T23:59:27+02:00 info dnsmasq[20062]: started, version 2.73 DNS disabled
2016-10-10T23:59:27+02:00 info dnsmasq[20062]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
2016-10-10T23:59:27+02:00 info dnsmasq[20062]: DNS service limited to local subnets
2016-10-10T21:59:28+02:00 info sfpswitch.py[1444]: sfplos change detected: 1
2016-10-10T21:59:29+02:00 notice netifd[]: Network device 'eth1' link is down
2016-10-10T21:59:29+02:00 notice netifd[]: Interface 'wan' has link connectivity loss
2016-10-10T23:59:29+02:00 info kernel[]: [99376.099079] mvneta f1034000.ethernet eth1: Link is Down
2016-10-10T21:59:29+02:00 notice netifd[]: wan (20015): Received SIGTERM
2016-10-10T21:59:31+02:00 info sfpswitch.py[1444]: sfplos change detected: 0
2016-10-10T21:59:33+02:00 notice netifd[]: Network device 'eth1' link is up
2016-10-10T21:59:33+02:00 notice netifd[]: Interface 'wan' has link connectivity
2016-10-10T21:59:33+02:00 notice netifd[]: Interface 'wan' is setting up now
2016-10-10T23:59:33+02:00 info kernel[]: [99380.095883] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-10T21:59:33+02:00 notice netifd[]: wan (20190): udhcpc (v1.23.2) started
2016-10-10T21:59:33+02:00 notice netifd[]: wan (20190): Sending discover...
2016-10-10T23:59:39+02:00 notice netifd[]: Last message 'wan (20190): Sending' repeated 1 times, supressed by syslog-ng on TURRIS-OMNIA
2016-10-10T21:59:39+02:00 notice netifd[]: wan (20190): Sending discover...
2016-10-10T22:00:01+02:00 info cron[20319]: (root) CMD (   /usr/bin/notifier)
2016-10-10T22:00:01+02:00 info cron[20323]: (root) CMD (nethist_stats.lua)
2016-10-10T22:00:01+02:00 info cron[20326]: (root) CMD (majordomo_db.sh downsize)
2016-10-10T22:00:01+02:00 info cron[20327]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-10-10T22:00:01+02:00 info cron[20315]: (root) CMD (/usr/bin/get-api-crl)
2016-10-10T22:00:01+02:00 info cron[20328]: (root) CMD (/usr/bin/updater-unstuck.sh >/dev/null 2>&1)
2016-10-10T22:00:01+02:00 info cron[20330]: (root) CMD (/usr/share/nikola/bin/nikola.sh)
2016-10-10T22:00:01+02:00 info cron[20331]: (root) CMD (/usr/share/firewall/turris-download)
2016-10-10T22:00:01+02:00 info cron[20334]: (root) CMD (/usr/bin/watchdog.sh)
2016-10-10T22:00:01+02:00 info cron[20339]: (root) CMD (/usr/sbin/squid -k rotate)
2016-10-10T22:00:01+02:00 warning watchdog[]: Restarted nethist
2016-10-11T00:00:03+02:00 info nikola[]: (v39) recognized WAN interfaces:
2016-10-10T22:00:06+02:00 err turris-firewall-rules[]: (v61) Failed to download https://api.turris.cz/firewall/turris-ipsets.gz.sign
2016-10-11T00:00:07+02:00 err nikola[]: (v39) Exception thrown: failed to initialize crypto library
2016-10-11T00:00:07+02:00 err nikola[]: (v39) Exception traceback: [('/usr/bin/nikola', 181, '<module>', 'server = WrappedServer(server_address, ssl_context=ssl_context)'), ('/usr/lib/python2.7/site-packages/nikola/rpc_wrapper.py', 30, '__init__', 'self.serial = binascii.hexlify(serial if serial else atsha204.get_serial())')]
2016-10-10T22:01:01+02:00 info cron[20513]: (root) CMD ((cat /tmp/nethist.stats | sort ; echo "uptime = $(cat /proc/uptime | cut -d. -f1)" ) | logger -p info -t nethist ; rm /tmp/nethist.stats)
2016-10-10T22:01:01+02:00 info cron[20514]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2016-10-10T22:01:01+02:00 info cron[20515]: (root) CMD (majordomo_db.sh genhour)
2016-10-10T22:01:01+02:00 info nethist[]: fs_avg = 508
2016-10-10T22:01:01+02:00 info nethist[]: fs_max = 508
2016-10-10T22:01:01+02:00 info nethist[]: fs_min = 508
2016-10-10T22:01:01+02:00 info nethist[]: fs_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: fs_sum = 731520
2016-10-10T22:01:01+02:00 info nethist[]: last_timestamp = 1476136787
2016-10-10T22:01:01+02:00 info nethist[]: load_avg = 0.015618055555556
2016-10-10T22:01:01+02:00 info nethist[]: load_max = 0.34
2016-10-10T22:01:01+02:00 info nethist[]: load_min = 0
2016-10-10T22:01:01+02:00 info nethist[]: load_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: load_sum = 22.49
2016-10-10T22:01:01+02:00 info nethist[]: mem_buffers_avg = 905664.76666667
2016-10-10T22:01:01+02:00 info nethist[]: mem_buffers_max = 911724
2016-10-10T22:01:01+02:00 info nethist[]: mem_buffers_min = 888176
2016-10-10T22:01:01+02:00 info nethist[]: mem_buffers_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: mem_buffers_sum = 1304157264
2016-10-10T22:01:01+02:00 info nethist[]: mem_cached_avg = 1472
2016-10-10T22:01:01+02:00 info nethist[]: mem_cached_max = 1472
2016-10-10T22:01:01+02:00 info nethist[]: mem_cached_min = 1472
2016-10-10T22:01:01+02:00 info nethist[]: mem_cached_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: mem_cached_sum = 2119680
2016-10-10T22:01:01+02:00 info nethist[]: mem_free_avg = 812060.35555556
2016-10-10T22:01:01+02:00 info nethist[]: mem_free_max = 818088
2016-10-10T22:01:01+02:00 info nethist[]: mem_free_min = 794568
2016-10-10T22:01:01+02:00 info nethist[]: mem_free_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: mem_free_sum = 1169366912
2016-10-10T22:01:01+02:00 info nethist[]: mem_total_avg = 1031660
2016-10-10T22:01:01+02:00 info nethist[]: mem_total_max = 1031660
2016-10-10T22:01:01+02:00 info nethist[]: mem_total_min = 1031660
2016-10-10T22:01:01+02:00 info nethist[]: mem_total_samples = 1440
2016-10-10T22:01:01+02:00 info nethist[]: mem_total_sum = 1485590400
2016-10-10T22:01:01+02:00 info nethist[]: temp_board_avg = nan
2016-10-10T22:01:01+02:00 info nethist[]: temp_board_max = 0
2016-10-10T22:01:01+02:00 info nethist[]: temp_board_samples = 0
2016-10-10T22:01:01+02:00 info nethist[]: temp_board_sum = 0
2016-10-10T22:01:01+02:00 info nethist[]: temp_cpu_avg = nan
2016-10-10T22:01:01+02:00 info nethist[]: temp_cpu_max = 0
2016-10-10T22:01:01+02:00 info nethist[]: temp_cpu_samples = 0
2016-10-10T22:01:01+02:00 info nethist[]: temp_cpu_sum = 0
2016-10-10T22:01:01+02:00 info nethist[]: uptime = 99470
2016-10-10T22:01:25+02:00 err ucollect[23612]: Too many pings not answered on api.turris.cz:5679, reconnecting
2016-10-10T22:01:25+02:00 info ucollect[23612]: Reconnecting to api.turris.cz:5679 now
2016-10-10T22:01:25+02:00 info ucollect[23612]: Socat started
2016-10-10T22:01:30+02:00 err ucollect[23612]: Failed to resolve uplink api.turris.cz:5679: Try again
2016-10-10T22:01:30+02:00 warning ucollect[23612]: Didn't get any V4 address in resolution of api.turris.cz
2016-10-10T22:01:30+02:00 warning ucollect[23612]: Didn't get any V6 address in resolution of api.turris.cz

Sfpswitch.py Error message
#7

No authentication required; when I use the media converter between Turris and Fiber Plug everything works just fine …


#8
2016-10-10T21:59:12+02:00 info sfpswitch.py[1444]: sfplos change detected: 0
2016-10-10T21:59:28+02:00 info sfpswitch.py[1444]: sfplos change detected: 1
2016-10-10T21:59:31+02:00 info sfpswitch.py[1444]: sfplos change detected: 0

Could you check if this loss of signal happens often?


#9

fiber7 writes that flexoptics (the vendor of the SFP) has prepared an update which should make it work with the turris omnia: https://twitter.com/fiber7_ch/status/785747481199939584


#10

wow, i want a such a cool provider like your one… that’s how things should work \o/


#11

This is interesting issue. The problem might be in the SERDES mode - there are basically two possibilities for SFP: SGMII or 1000BASE-X. The sfpswitch.py does basic detection based on few bytes in SFP EEPROM and because it finaly selected phy-sfp (according to your log) it means that it decided for 1000BASE-X.

The question is whether you receive some packets. Can you try running tcpdump on eth1 interface and report back whether you can see some packets comming through? (Especially received packets are the most interesting.)

Cheers, Tomas


#12

I have exactly the same issue with the same ISP (fiber7.ch) but a bit different SFP module: TP-Link TL-SM321B. It works perfectly fine through TP-Link MC220L convert but doesn’t work if inserted into Turris.

Log:
2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]: sfpdet change detected: 0
2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]: I2C read: 0x02
2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]:
2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]: Switching mode to phy-sfp.
2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]: Switch success.
2016-10-15T19:42:35+02:00 info sfpswitch.py[1845]: Restarting net with command ip link set down dev eth1; /etc/init.d/network restart

2016-10-15T19:43:05+02:00 info sfpswitch.py[1845]: sfplos change detected: 0
2016-10-15T19:43:15+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-15T19:43:15+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-15T19:43:15+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-15T21:43:15+02:00 info kernel[]: [ 298.410762] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-15T21:43:15+02:00 info kernel[]: [ 298.410783] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
2016-10-15T19:43:15+02:00 notice netifd[]: wan (7784): udhcpc (v1.23.2) started
2016-10-15T19:43:16+02:00 notice netifd[]: wan (7784): Sending discover…
2016-10-15T19:43:17+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-15T19:43:17+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-15T21:43:17+02:00 info kernel[]: [ 300.413952] mvneta f1034000.ethernet eth1: Link is Down
2016-10-15T19:43:17+02:00 notice netifd[]: wan (7784): Received SIGTERM
2016-10-15T19:43:18+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-15T19:43:18+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-15T19:43:18+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-15T21:43:18+02:00 info kernel[]: [ 301.410781] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-15T19:43:18+02:00 notice netifd[]: wan (7799): udhcpc (v1.23.2) started
2016-10-15T19:43:19+02:00 notice netifd[]: wan (7799): Sending discover…
2016-10-15T19:43:20+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-15T19:43:20+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-15T21:43:20+02:00 info kernel[]: [ 303.413956] mvneta f1034000.ethernet eth1: Link is Down
2016-10-15T19:43:20+02:00 notice netifd[]: wan (7799): Received SIGTERM

I tried tcpdump and looks like there are no incoming packets:
root@turris:~# tcpdump -pAe -n -i eth1
tcpdump: WARNING: eth1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
21:43:15.905650 d8:58:d7:00:50:a4 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
....L..................................:.................................P......................................... 21:43:15.955613 d8:58:d7:00:50:a4 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68…L…:…P…
21:43:16.135580 d8:58:d7:00:50:a4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.I…{…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:43:16.735595 d8:58:d7:00:50:a4 > 33:33:ff:00:50:a4, ethertype IPv6 (0x86dd), length 78: :: > ff02::1:ff00:50a4: ICMP6, neighbor solicitation, who has fe80::da58:d7ff:fe00:50a4, length 24
.....:...............................P...*..............X....P. 21:43:17.735658 d8:58:d7:00:50:a4 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 150: fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88...........X....P.................:.....................................................P......................................... 21:43:17.755578 d8:58:d7:00:50:a4 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28…$…X…P…:…p…
21:43:17.855571 d8:58:d7:00:50:a4 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
`…$…X…P…:…p…
21:43:19.115577 d8:58:d7:00:50:a4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…i…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…


#13

Wow amazing ISP support… and speed. Can you both share where you got your SFPs from? I’d love to try this here too in Austria.


#14

I am also with Fiber7, and I have also been waiting patiently for my 3 Turris Omnias to arrive, so I can test them out. :slight_smile:

However, I have had good experiences with the Lightwin LSFP-WDM-LA20-UNI SFP modules: They are also TX:1310nm, RX:1550nm. I used one in a Ubiquiti EdgeRouter X-SFP, and it worked okay (functionally perfect with IPv6-PD and the static IPv4 address I leased from Fiber7), but the routing hardware simply couldn’t keep up (it maxed out at around 500Mb/sec downstream and about 200Mb/sec upstream.)

The Lightwin modules are a bit more expensive, and they do have a 20Km range, rather than the standard 10Km of the TP-Link, but that doesn’t seem to have any effect on how well they work with Fiber7. For 20km, it’s a similar power class as for 10Km - it’s not until you start going to 40+ Km that you need an extended range device.

I would be grateful if someone could check if these modules will work in the Omnia. Since I’m still waiting for mine, there isn’t much I can do to test this! But if one of the Omnia development team would like loan of my Lightwin SFP module to make sure it’s supported, then PM me and I’ll see what I can do for you. As far as I’m concerned, it’s well worth my time. (I have three in boxes, waiting for their respective Omnias!)


#15

I’ve got my SFP from Fiber7 when ordering the TP-LINK MC220L media converter from them (110 CHF or ca. 100 EUR for the whole package of media converter, SFP and short fiber cable):

https://www.fiber7.ch/en/fiber7-technology/fiber7-hardware/ (scroll down all the way to the bottom)

You could also buy the SFPs directly from the producer, flexOptix (Germany) for 35 EUR (but don’t ask me which of the manyfold configurations you need; see dropdown):

https://www.flexoptix.net/en/sfp-bidi-transceiver-1-gigabit-sm-tx1310nm-rx1550nm-10km-12db-ddm-dom.html

Addendum: Nevermind, there you are, they already have a “Turris Omnia” configuration:


#16

I’ve bought my set here: https://www.digitec.ch/en/s1/product/fiber7-hardwarebundle-3m-glasfaserkabel-network-accessories-2759248
It was the cheapest option and I’m getting around 900Mbit/s from it.


#17

I just ordered a new FlexOptix SFP with Turris Omnia compatibility. I had hoped for a way to reconfigure my existing SFP, but it seems like the FlexOptix SFP programmer costs >> 1000 CHF, so it’s not cost-effective to buy one when all you have is 1 SFP :). Given that I wanted a second SFP for redundancy reasons anyway, I figured I’d just buy another one.

Will update the thread once I have the new SFP.


#18

AFAIK the programmer only (re)writes the i2c EEPROM in the SFP that contains the configuration data. You may do the programming in Turris Omnia, using i2c bus no. 5 that is connected to the SFP cage. The only problem is to have the EEPROM content.

Anyway, we read the EEPROM content in sfpswitch.py module just to decide on MII mode - SGMII vs. 1000BASE-X, which is electrically equivalent, but it uses different in-band signalling format for link up/down and speed signalling (in case of SGMII).

It seems that what may help with the modules is switching the mode manually. There is yet another problem - we need a bit more patched Kernel for more parameters to be set from sfpswitch.py. I am working on it and once it is finished, I will put testing repository links to this forum for you to test it.


#19

From the syslog, we can see that the current mode is phy-sfp:

2016-10-15T19:42:33+02:00 info sfpswitch.py[1845]: Switching mode to phy-sfp.

From the code, I gather that there are 3 modes: phy-def, phy-sfp and phy-sgmii-sfp.

Looking at http://www.tp-link.com/en/products/details/cat-4792_MC220L.html, there’s no mention of SGMII, so I think we need either phy-def or phy-sfp.

Given that phy-sfp is what the script currently detects, are you saying that we should try enforcing the phy-def mode? If yes, what would be the best way to do that?


#20

I unfortunately have bad news regarding the Lightwin SFP module (many thanks to Yorik for taking the time to test it). He has given me the following diagnostic information about the module:

/var/log/messages:
2016-10-18T19:43:18+02:00 info sfpswitch.py[1845]: sfpdet change detected: 0
2016-10-18T19:43:18+02:00 info sfpswitch.py[1845]: I2C read: 0x00
2016-10-18T19:43:18+02:00 info sfpswitch.py[1845]:
2016-10-18T19:43:18+02:00 info sfpswitch.py[1845]: Switching mode to phy-sfp.
2016-10-18T19:43:18+02:00 info sfpswitch.py[1845]: Switch success.
2016-10-18T19:43:20+02:00 info sfpswitch.py[1845]: Restarting net with command ip link set down dev eth1; /etc/init.d/network restart
2016-10-18T19:43:20+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Network alias ‘eth1’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘wan6’ has link connectivity loss
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘wan6’ is disabled
2016-10-18T19:43:20+02:00 err miniupnpd[5004]: Failed to get IP for interface eth1
2016-10-18T19:43:20+02:00 warning miniupnpd[5004]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
2016-10-18T19:43:20+02:00 notice netifd[]: wan6 (4889): Command failed: Permission denied
2016-10-18T21:43:20+02:00 info dnsmasq-dhcp[4953]: read /etc/ethers - 0 addresses
2016-10-18T19:43:20+02:00 notice netifd[]: wan (4774): Received SIGTERM
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘lan’ is now down
2016-10-18T21:43:20+02:00 info kernel[]: [259484.369870] br-lan: port 4(wlan0) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.369957] br-lan: port 3(wlan1) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.369992] br-lan: port 2(eth2) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.370008] br-lan: port 1(eth0) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.393270] device eth0 left promiscuous mode
2016-10-18T21:43:20+02:00 info kernel[]: [259484.393332] br-lan: port 1(eth0) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.409888] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
2016-10-18T21:43:20+02:00 info kernel[]: [259484.411557] device eth2 left promiscuous mode
2016-10-18T21:43:20+02:00 info kernel[]: [259484.411621] br-lan: port 2(eth2) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.428792] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
2016-10-18T21:43:20+02:00 info kernel[]: [259484.439835] device wlan0 left promiscuous mode
2016-10-18T21:43:20+02:00 info kernel[]: [259484.439899] br-lan: port 4(wlan0) entered disabled state
2016-10-18T21:43:20+02:00 info kernel[]: [259484.440365] device wlan1 left promiscuous mode
2016-10-18T21:43:20+02:00 info kernel[]: [259484.440419] br-lan: port 3(wlan1) entered disabled state
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘lan’ is disabled
2016-10-18T19:43:20+02:00 notice netifd[]: Network device ‘eth2’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Network device ‘eth0’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Bridge ‘br-lan’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘lan’ has link connectivity loss
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘loopback’ is now down
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘loopback’ is disabled
2016-10-18T19:43:20+02:00 notice netifd[]: Network device ‘lo’ link is down
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘loopback’ has link connectivity loss
2016-10-18T19:43:20+02:00 notice netifd[]: Interface ‘wan’ is disabled
2016-10-18T19:43:21+02:00 info sfpswitch.py[1845]: sfpflt change detected: 0
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘lan’ is enabled
2016-10-18T21:43:22+02:00 info kernel[]: [259486.785672] device eth0 entered promiscuous mode
2016-10-18T21:43:22+02:00 info kernel[]: [259486.787180] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘lan’ is setting up now
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘lan’ is now up
2016-10-18T21:43:22+02:00 info kernel[]: [259486.801739] device eth2 entered promiscuous mode
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘loopback’ is enabled
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘loopback’ is setting up now
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘loopback’ is now up
2016-10-18T21:43:22+02:00 info kernel[]: [259486.812837] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘wan’ is enabled
2016-10-18T19:43:22+02:00 notice netifd[]: Network device ‘lo’ link is up
2016-10-18T19:43:22+02:00 notice netifd[]: Interface ‘loopback’ has link connectivity
2016-10-18T19:43:23+02:00 notice netifd[]: radio0 (19012): command failed: Not supported (-95)
2016-10-18T19:43:23+02:00 err turris-firewall-rules[]: (v61) Unable to determine the WAN interface. Exiting…
2016-10-18T19:43:23+02:00 notice netifd[]: radio1 (19013): Configuration file: /var/run/hostapd-phy1.conf
2016-10-18T21:43:23+02:00 info kernel[]: [259487.346752] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
2016-10-18T19:43:23+02:00 notice netifd[]: radio0 (19012): Configuration file: /var/run/hostapd-phy0.conf
2016-10-18T19:43:23+02:00 notice netifd[]: Bridge ‘br-lan’ link is up
2016-10-18T19:43:23+02:00 notice netifd[]: Interface ‘lan’ has link connectivity
2016-10-18T19:43:23+02:00 notice netifd[]: radio1 (19013): wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
2016-10-18T21:43:23+02:00 info kernel[]: [259487.379984] device wlan1 entered promiscuous mode
2016-10-18T21:43:23+02:00 info kernel[]: [259487.380064] br-lan: port 3(wlan1) entered forwarding state
2016-10-18T21:43:23+02:00 info kernel[]: [259487.380089] br-lan: port 3(wlan1) entered forwarding state
2016-10-18T21:43:23+02:00 info kernel[]: [259487.380153] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
2016-10-18T21:43:24+02:00 info kernel[]: [259488.778286] mvneta f1030000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
2016-10-18T21:43:24+02:00 info kernel[]: [259488.788562] mvneta f1070000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
2016-10-18T19:43:25+02:00 notice netifd[]: radio0 (19012): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
2016-10-18T19:43:25+02:00 notice netifd[]: radio0 (19012): wlan0: interface state COUNTRY_UPDATE->HT_SCAN
2016-10-18T21:43:25+02:00 info kernel[]: [259489.374428] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
2016-10-18T21:43:25+02:00 info kernel[]: [259489.375607] device wlan0 entered promiscuous mode
2016-10-18T21:43:25+02:00 info kernel[]: [259489.375649] br-lan: port 4(wlan0) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.375665] br-lan: port 4(wlan0) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.385641] br-lan: port 3(wlan1) entered forwarding state
2016-10-18T19:43:25+02:00 notice netifd[]: Network device ‘eth0’ link is up
2016-10-18T21:43:25+02:00 info kernel[]: [259489.393974] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
2016-10-18T21:43:25+02:00 info kernel[]: [259489.394090] br-lan: port 1(eth0) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.394108] br-lan: port 1(eth0) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.394162] br-lan: port 2(eth2) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.394179] br-lan: port 2(eth2) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.394261] br-lan: port 4(wlan0) entered disabled state
2016-10-18T19:43:25+02:00 notice netifd[]: Network device ‘eth2’ link is up
2016-10-18T19:43:25+02:00 notice netifd[]: radio1 (19013): wlan1: interface state COUNTRY_UPDATE->ENABLED
2016-10-18T19:43:25+02:00 notice netifd[]: radio1 (19013): wlan1: AP-ENABLED
2016-10-18T19:43:25+02:00 notice netifd[]: Network device ‘wlan1’ link is up
2016-10-18T21:43:25+02:00 info kernel[]: [259489.774278] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
2016-10-18T21:43:25+02:00 info kernel[]: [259489.774358] br-lan: port 4(wlan0) entered forwarding state
2016-10-18T21:43:25+02:00 info kernel[]: [259489.774405] br-lan: port 4(wlan0) entered forwarding state
2016-10-18T19:43:25+02:00 notice netifd[]: radio0 (19012): wlan0: interface state HT_SCAN->ENABLED
2016-10-18T19:43:25+02:00 notice netifd[]: radio0 (19012): wlan0: AP-ENABLED
2016-10-18T19:43:25+02:00 notice netifd[]: Network device ‘wlan0’ link is up
2016-10-18T21:43:27+02:00 info kernel[]: [259491.388098] br-lan: port 2(eth2) entered forwarding state
2016-10-18T21:43:27+02:00 info kernel[]: [259491.388136] br-lan: port 1(eth0) entered forwarding state
2016-10-18T21:43:27+02:00 info kernel[]: [259491.768079] br-lan: port 4(wlan0) entered forwarding state
2016-10-18T19:43:55+02:00 info sfpswitch.py[1845]: sfplos change detected: 0
2016-10-18T19:44:29+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-18T19:44:29+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-18T19:44:29+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-18T21:44:29+02:00 info kernel[]: [259553.818110] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-18T21:44:29+02:00 info kernel[]: [259553.818131] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
2016-10-18T19:44:29+02:00 notice netifd[]: wan (19701): udhcpc (v1.23.2) started
2016-10-18T19:44:29+02:00 notice netifd[]: wan (19701): Sending discover…
2016-10-18T21:44:33+02:00 notice netifd[]: Last message ‘wan (19701): Sending’ repeated 1 times, supressed by syslog-ng on turris
2016-10-18T19:44:33+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-18T19:44:33+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-18T21:44:33+02:00 info kernel[]: [259557.821297] mvneta f1034000.ethernet eth1: Link is Down
2016-10-18T19:44:33+02:00 notice netifd[]: wan (19701): Received SIGTERM
2016-10-18T19:44:34+02:00 notice netifd[]: Network device ‘eth1’ link is up
2016-10-18T19:44:34+02:00 notice netifd[]: Interface ‘wan’ has link connectivity
2016-10-18T19:44:34+02:00 notice netifd[]: Interface ‘wan’ is setting up now
2016-10-18T21:44:34+02:00 info kernel[]: [259558.818118] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
2016-10-18T19:44:34+02:00 notice netifd[]: wan (19716): udhcpc (v1.23.2) started
2016-10-18T19:44:34+02:00 notice netifd[]: wan (19716): Sending discover…
2016-10-18T19:44:36+02:00 notice netifd[]: Network device ‘eth1’ link is down
2016-10-18T19:44:36+02:00 notice netifd[]: Interface ‘wan’ has link connectivity loss
2016-10-18T21:44:36+02:00 info kernel[]: [259560.821297] mvneta f1034000.ethernet eth1: Link is Down
2016-10-18T19:44:36+02:00 notice netifd[]: wan (19716): Received SIGTERM

root@turris:~# tcpdump -n -i eth1 -p -A
tcpdump: WARNING: eth1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
21:44:29.712240 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
…L…:…P…
21:44:29.812233 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
…L…:…P…
21:44:29.932201 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…S…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:44:30.362220 IP6 :: > ff02::1:ff00:50a4: ICMP6, neighbor solicitation, who has fe80::da58:d7ff:fe00:50a4, length 24
…:…P…
…X…P.
21:44:31.362288 IP6 fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88
…X…P…:…P…
21:44:31.382195 IP6 fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
…$…X…P…:…p…
21:44:31.882214 IP6 fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88
…X…P…:…P…
21:44:32.242206 IP6 fe80::da58:d7ff:fe00:50a4 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
`…$…X…P…:…p…
21:44:33.032193 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…S…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:44:34.902199 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.R…B.>W…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:44:37.872203 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.t…y…F…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:44:41.922199 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4X…L<N…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:44:45.002266 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4X…L<N…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:44:47.872207 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…(>.F…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:44:50.872229 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:44:54.882191 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.}…N…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:44:57.982195 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.z…N…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:45:00.882205 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.
…S…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:45:05.882208 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…y…T…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:45:10.912246 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4R1…b…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:45:14.032185 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4R…b…X…P…c.Sc5…9…@7.<.udhcp 1.23.2…
21:45:18.902192 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4.:…0.)5…X…P…c.Sc5…9…@7
.<.udhcp 1.23.2…
21:45:23.912204 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:50:a4, length 300
E…H…@.y…D.C.4…V.W…X…P…c.Sc5…9…@7…*.<.udhcp 1.23.2…
^C
23 packets captured
23 packets received by filter
0 packets dropped by kernel

root@turris:~# i2cdump 5 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-5, address 0x50, mode byte
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 03 04 07 00 00 00 00 12 00 01 01 01 0d 00 14 c8 ???..?.???.??
10: 00 00 00 00 54 52 49 4f 54 52 4f 4e 49 4b 20 20 …TRIOTRONIK
20: 20 20 20 20 00 00 00 00 4c 53 46 50 2d 57 44 4d …LSFP-WDM
30: 2d 4c 41 32 30 20 20 20 41 20 20 20 05 1e 00 6b -LA20 A ??.k
40: 00 1a 00 00 43 49 42 31 35 30 37 32 38 30 32 39 .?..CIB150728029
50: 20 20 20 20 31 35 30 37 32 39 20 20 68 90 01 ab 150729 h???
60: 2d 00 11 6a 0e 6a 83 71 9c 23 7d b0 b4 6f 5a 85 -.?j?j?q?#}??oZ?
70: 62 60 a9 00 00 00 00 00 00 00 00 00 7e eb 14 8d b`?..~???
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …