WAN port does not work with ISP (BT Home Hub 5.0)

my thinking about this is maybe the other end is only 100M and or
the HH5 has a bug in it openwrt that is untested relating to speed or Nway
that adding a dump switch as diagnostic tool to find a possible problem

ISP is claiming 1Gb/s on port. I have tested speed with Mikrotik and definitely got more than 100Mb/s.
What is Nway?

Just tried to test speed. Wifi AC connection with openwrt showed about 50Mb/s to the test server.
Wired connection with Mikrotik showed 500Mb/s.
So probably this is really about OpenWrt port speed.

it's just the old name for Autonegotiation
in the early days when it was an option on 100M switches with NWay could use any cable

1 Like

Found a log with connectivity trace

connecting to ISP ending with SIGTERM :smiley:
Tue Apr  6 18:16:24 2021 daemon.notice netifd: Interface 'wan' is enabled
Tue Apr  6 18:16:25 2021 daemon.notice netifd: Network device 'eth0' link is up
Tue Apr  6 18:16:25 2021 kern.info kernel: [ 1757.633996] lantiq,xrx200-net 1e108000.eth eth0: port 5 got link
Tue Apr  6 18:16:25 2021 kern.info kernel: [ 1757.639904] br-lan: port 1(eth0.1) entered blocking state
Tue Apr  6 18:16:25 2021 kern.info kernel: [ 1757.644053] br-lan: port 1(eth0.1) entered forwarding state
Tue Apr  6 18:16:25 2021 daemon.notice netifd: VLAN 'eth0.1' link is up
Tue Apr  6 18:16:25 2021 daemon.notice netifd: VLAN 'eth0.2' link is up
Tue Apr  6 18:16:25 2021 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Apr  6 18:16:25 2021 daemon.notice netifd: Interface 'wan' is setting up now
Tue Apr  6 18:16:25 2021 kern.info kernel: [ 1757.650874] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Tue Apr  6 18:16:26 2021 daemon.notice netifd: wan (3296): udhcpc: started, v1.30.1
Tue Apr  6 18:16:26 2021 daemon.notice netifd: wan (3296): udhcpc: sending discover
Tue Apr  6 18:16:29 2021 daemon.notice netifd: wan (3296): udhcpc: sending discover
Tue Apr  6 18:16:30 2021 daemon.notice netifd: Network device 'eth0' link is down
Tue Apr  6 18:16:30 2021 kern.info kernel: [ 1761.733879] lantiq,xrx200-net 1e108000.eth eth0: port 5 lost link
Tue Apr  6 18:16:30 2021 kern.info kernel: [ 1761.741411] br-lan: port 1(eth0.1) entered disabled state
Tue Apr  6 18:16:30 2021 daemon.notice netifd: VLAN 'eth0.1' link is down
Tue Apr  6 18:16:30 2021 daemon.notice netifd: VLAN 'eth0.2' link is down
Tue Apr  6 18:16:30 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Apr  6 18:16:30 2021 daemon.notice netifd: wan (3296): udhcpc: received SIGTERM
Tue Apr  6 18:16:30 2021 daemon.notice netifd: Interface 'wan' is now down
Tue Apr  6 18:16:30 2021 daemon.notice netifd: Interface 'wan' is disabled
Tue Apr  6 18:16:30 2021 kern.info kernel: [ 1761.906231] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Connecting to mikrotik
Tue Apr  6 18:16:30 2021 daemon.notice netifd: Interface 'wan' is enabled
Tue Apr  6 18:16:34 2021 daemon.notice netifd: Network device 'eth0' link is up
Tue Apr  6 18:16:34 2021 kern.info kernel: [ 1765.825819] lantiq,xrx200-net 1e108000.eth eth0: port 5 got link
Tue Apr  6 18:16:34 2021 kern.info kernel: [ 1765.832482] br-lan: port 1(eth0.1) entered blocking state
Tue Apr  6 18:16:34 2021 kern.info kernel: [ 1765.836545] br-lan: port 1(eth0.1) entered forwarding state
Tue Apr  6 18:16:34 2021 kern.info kernel: [ 1765.843266] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Tue Apr  6 18:16:34 2021 daemon.notice netifd: VLAN 'eth0.1' link is up
Tue Apr  6 18:16:34 2021 daemon.notice netifd: VLAN 'eth0.2' link is up
Tue Apr  6 18:16:34 2021 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Apr  6 18:16:34 2021 daemon.notice netifd: Interface 'wan' is setting up now
Tue Apr  6 18:16:34 2021 daemon.notice netifd: wan (3496): udhcpc: started, v1.30.1
Tue Apr  6 18:16:34 2021 daemon.notice netifd: wan (3496): udhcpc: sending discover
Tue Apr  6 18:16:35 2021 daemon.notice netifd: wan (3496): udhcpc: sending select for 192.168.0.100
Tue Apr  6 18:16:35 2021 daemon.notice netifd: wan (3496): udhcpc: lease of 192.168.0.100 obtained, lease time 122
Tue Apr  6 18:16:35 2021 daemon.notice netifd: Interface 'wan' is now up

Was not able to find any info related to the speed settings. Weird.

This is the problem. Link started up, then 5 seconds later link failure at layer 1. (I assume you did not unplug the cable). That causes the whole networking system to reset, including killing udhcpc in preparation for the restart.

Try reconfiguring the switch to make one of the other Ethernet ports the wan (remove from VLAN 1, and move it into VLAN 2 untagged). Sometimes a used router has hardware damage to one of the ports from lightning or power surge resulting in degraded performance.

There is generally no user accessible configuration to force a port to a lower speed.

ethtool, where available.

Did you read the OpenWrt/LEDE Installation Guide for BT Home Hub 5A? The (ethernet-) WAN port is working fine on my device.

Just tried. all the same.
I was able to receive dhcp from mikrotik, and no connection with wan cable.

I took a look.
I can't see any special things I have not tried during the last 24 hours.
It seems I got the damaged one. Will try to give it back.

Roll back to the NAND backup, see if the WAN works there.

Somehow it start works normally after another hard reset.

I did a small test speed

speedtest Mikrotik rb750
Download: 588.64 Mbit/s
Upload: 786.87 Mbit/s

speedtest bthh5a
Download: 59.02 Mbit/s
Upload: 38.05 Mbit/s

speedtest TP-Link WR940N
Download: 92.05 Mbit/s
Upload: 97.00 Mbit/s

1Gb Ethernet productivity looks very poor comparing even to 100Mbit/s tp-link
No sense to continue, I'll return thi bt home asap.

Thanks everyone for intention to help.

Sounds a little slow...

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.