Problems connecting to DSL router via WAN port

Turris Omnia
1

Hello all,

I have some problems connecting my turris omnia to my network.
My network topology looks like this
PC — WRT160NL — DSL Router — Internet

I’d like to replace the WRT160NL (which is running OpenWRT) with the Turris Omnia. Somehow I can’t get a link on Turris WAN interface to the DSL router.
I checked the settings on the WRT and they match the settings on the Turris Omnia.

But for a reason that I can’t figure out Turris Omnia keeps telling me WAN has no link and connecting to WAN on the WRT works without a problem.

Any suggestions?
Thanks in advance :slight_smile:

1 Like
2

Hi guys,
I have a similar problem. The wan port (eth1) doesn’t go up when I connect it to my ISP switch (guess it’s a TP-Link 100Mbps switch). Other devices works correctly with that switch.

I have done a bit of troubleshooting and discover that:

root@turris:~# ip link show dev eth1
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 532
link/ether d8:58:d7:00:52:12 brd ff:ff:ff:ff:ff:ff

root@turris:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Half
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Link detected: no

Ethernet autonegotiation doesn’t work correctly and port on Turris side never comes up because ISP switch doesn’t support 1000BaseT/Half.
In my case was enough to set Ethernet manually:

root@turris:~# ethtool -s eth1 autoneg off
root@turris:~# ethtool -s eth1 speed 100
root@turris:~# ethtool -s eth1 duplex full

root@turris:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: off
Link detected: yes

Eth1 port have gone up and traffice started to pass trough, but what surprise I’ve found in dmesg :slight_smile:

[ 789.920268] mvneta f1034000.ethernet eth1: bad rx status 0f810000 (crc error), size=171
[ 790.003317] mvneta f1034000.ethernet eth1: bad rx status 0fa10000 (crc error), size=1078
[ 790.018413] mvneta f1034000.ethernet eth1: bad rx status 0f810000 (crc error), size=467
[ 790.257909] mvneta f1034000.ethernet eth1: bad rx status 0fa10000 (crc error), size=190
[ 790.266241] mvneta f1034000.ethernet eth1: bad rx status 0fa10000 (crc error), size=1133
…

That probably means, that many packets are dropped by kernel mvneta implementation. I’ve already tested Ethernet cable to ISP switch and I have also tried two different devices connect to ISP switch. Everything was ok in those tests.

Does anybody meet with this?
Thanks in advance.

1 Like
3

Hello vojuv,

thank you for your post.
The manual configuration solved my connection problems.
However I have no messages about dropped packets in dmesg.

4

Hi there,

I got my Turris Omnia this week and have the same problem: eth1 is not coming up and not connecting to the WAN.

Also, I can’t find the ethtool package in opkg. I’m new to OpenWRT. Where can I find the packages and what architecture do I have to look for? I suppose armv7l.

Also, is this a known bug which will be resolved? I didn’t have problems connecting any other device to my provider’s DSL modem, so I guess it’s the Turris eth port.

5

I had the same issue just after receiving Turris Omnia, no link with ISP hardware.
ethtool showed me almost the same info vojtuv posted above: no 1000BaseT/Half advertised from link partner. Suggested manual reconfiguration allowed to link devices on 100Mbps.

Good thing is, I also have a standby ethernet cable from another ISP (100Mbps only) which I use in rare cases of primary ISP network downtime. Because of that I was certain that WAN port of Turris Omnia disfunction is unlikely and I could update the opkg repository and install ethtool.

The issue was resolved by ISP technician who made the diagnostics, ascertained that their cable is defective and replaced it with the new one.