GL-MV1000 (Brume without WLAN) often 'link is down'

Hi there,

For some time I have used the Brume as an access point. Streams and downloads over the internet have frozen over and over again.
Now I have reset everything and the Brume is in factory settings (WITHOUT VPN). Even in this state I have ‘link is down’ all the time. I have tested with

wget -O /dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip

My configuration: Brume (IP 192.168.8.1) via wan connection to lan connection of a DSL Fritzbox (IP 192.168.100.1).

Maybe someone knows this problem and can help.
Thanks

Blockquote
Log extract:
Mon Mar 7 12:51:08 2022 daemon.notice netifd: Interface ‘wan’ is now up
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: reading /tmp/resolv.conf.auto
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain test
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain onion
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain localhost
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain local
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain invalid
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain bind
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using local addresses only for domain lan
Mon Mar 7 12:51:08 2022 daemon.info dnsmasq[12557]: using nameserver 192.168.100.1#53
Mon Mar 7 12:51:10 2022 user.info mwan3rtmon[2697]: Detect rtchange event.
Mon Mar 7 12:51:10 2022 user.notice firewall: Reloading firewall due to ifup of wan (wan)
Mon Mar 7 13:26:15 2022 daemon.notice netifd: Network device ‘wan’ link is down
Mon Mar 7 13:26:15 2022 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Mon Mar 7 13:26:15 2022 kern.info kernel: [11723.839194] mv88e6085 d0032004.mdio-mii:01 wan: Link is Down
Mon Mar 7 13:26:15 2022 daemon.notice netifd: wan (24539): udhcpc: received SIGTERM
Mon Mar 7 13:26:15 2022 daemon.notice netifd: Interface ‘wan’ is now down
Mon Mar 7 13:26:15 2022 daemon.notice netifd: Interface ‘wan’ is disabled
Mon Mar 7 13:26:15 2022 daemon.notice netifd: Interface ‘wan’ is enabled
Mon Mar 7 13:26:15 2022 daemon.warn dnsmasq[12557]: no servers found in /tmp/resolv.conf.auto, will retry
Mon Mar 7 13:26:15 2022 kern.info kernel: [11723.931037] IPv6: ADDRCONF(NETDEV_UP): wan: link is not ready
Mon Mar 7 13:26:17 2022 daemon.notice netifd: Network device ‘wan’ link is up
Mon Mar 7 13:26:17 2022 daemon.notice netifd: Interface ‘wan’ has link connectivity
Mon Mar 7 13:26:17 2022 daemon.notice netifd: Interface ‘wan’ is setting up now
Mon Mar 7 13:26:17 2022 kern.info kernel: [11726.004667] mv88e6085 d0032004.mdio-mii:01 wan: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Mar 7 13:26:17 2022 kern.info kernel: [11726.013745] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
Mon Mar 7 13:26:17 2022 daemon.notice netifd: wan (6991): udhcpc: started, v1.30.1
Mon Mar 7 13:26:17 2022 daemon.notice netifd: wan (6991): udhcpc: sending discover
Mon Mar 7 13:26:17 2022 daemon.notice netifd: wan (6991): udhcpc: sending select for 192.168.100.2
Mon Mar 7 13:26:17 2022 daemon.notice netifd: wan (6991): udhcpc: lease of 192.168.100.2 obtained, lease time 8640000
Mon Mar 7 13:26:17 2022 daemon.notice netifd: Interface ‘wan’ is now up
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: reading /tmp/resolv.conf.auto
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain test
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain onion
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain localhost
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain local
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain invalid
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain bind
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using local addresses only for domain lan
Mon Mar 7 13:26:17 2022 daemon.info dnsmasq[12557]: using nameserver 192.168.100.1#53
Mon Mar 7 13:26:19 2022 user.info mwan3rtmon[2697]: Detect rtchange event.
Mon Mar 7 13:26:19 2022 user.notice firewall: Reloading firewall due to ifup of wan (wan)
Mon Mar 7 13:27:26 2022 kern.info kernel: [11795.693610] mv88e6085 d0032004.mdio-mii:01 wan: Link is Down
Mon Mar 7 13:27:26 2022 daemon.notice netifd: Network device ‘wan’ link is down
Mon Mar 7 13:27:26 2022 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Mon Mar 7 13:27:26 2022 daemon.notice netifd: wan (6991): udhcpc: received SIGTERM
Mon Mar 7 13:27:26 2022 daemon.notice netifd: Interface ‘wan’ is now down
Mon Mar 7 13:27:26 2022 daemon.notice netifd: Interface ‘wan’ is disabled
Mon Mar 7 13:27:26 2022 daemon.notice netifd: Interface ‘wan’ is enabled
Mon Mar 7 13:27:26 2022 daemon.warn dnsmasq[12557]: no servers found in /tmp/resolv.conf.auto, will retry
Mon Mar 7 13:27:26 2022 kern.info kernel: [11795.770489] IPv6: ADDRCONF(NETDEV_UP): wan: link is not ready
Mon Mar 7 13:27:29 2022 kern.info kernel: [11797.837675] mv88e6085 d0032004.mdio-mii:01 wan: Link is Up - 100Mbps/Full - flow control rx/tx
Mon Mar 7 13:27:29 2022 kern.info kernel: [11797.846885] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
Mon Mar 7 13:27:29 2022 daemon.notice netifd: Network device ‘wan’ link is up
Mon Mar 7 13:27:29 2022 daemon.notice netifd: Interface ‘wan’ has link connectivity
Mon Mar 7 13:27:29 2022 daemon.notice netifd: Interface ‘wan’ is setting up now
Mon Mar 7 13:27:29 2022 daemon.notice netifd: wan (9643): udhcpc: started, v1.30.1
Mon Mar 7 13:27:29 2022 daemon.notice netifd: wan (9643): udhcpc: sending discover
Mon Mar 7 13:27:29 2022 daemon.notice netifd: wan (9643): udhcpc: sending select for 192.168.100.2
Mon Mar 7 13:27:29 2022 daemon.notice netifd: wan (9643): udhcpc: lease of 192.168.100.2 obtained, lease time 8640000
Mon Mar 7 13:27:29 2022 daemon.notice netifd: Interface ‘wan’ is now up
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: reading /tmp/resolv.conf.auto
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain test
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain onion
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain localhost
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain local
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain invalid
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain bind
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using local addresses only for domain lan
Mon Mar 7 13:27:29 2022 daemon.info dnsmasq[12557]: using nameserver 192.168.100.1#53
Mon Mar 7 13:27:31 2022 user.info mwan3rtmon[2697]: Detect rtchange event.
Mon Mar 7 13:27:31 2022 user.notice firewall: Reloading firewall due to ifup of wan (wan)

Does this only happen when you test speed or even not testing speed?

Seems that MV1000 has some problem with your DSL modem.

I know a case that the modem does not want to accept the mac address of the router and causing continuous disconnect.

So when the above happens you may need to reboot the modem so that it accept new router. Or if you have a working old router you need to clone the mac address to the new router.

Not sure if this the case but can you give me some update.

It happens all the time. Downloads crashes and streams freezes.
Indeed the router is an older one (Fritzbox 7320) and a reboot didn’t help. Cloning the mac address didn’t help either.

I have read about a similar problem of someone else. He changed the MTU to 1412 (with wireguard). I have insert it in Brume’s LUCI (WAN MTU) and the connection seems a little bit stable but the problem still exists.

Sorry but stupid question, have you tried another Ethernet cable? I cannot think of a reason.

Now I have changed cables and it’s still the same behavior.
My thoughts: my old DSL-router is a 100 Mb/s device and the BRUME 1000 Mb/s. Maybe the DSL-Router can’t manage data packages. Is it possible to decrease the WAN socket of the BRUME to 100 Mb/s ?
When all fails I try another DSL-Router in the next days.

It is automatic so this is not necessary.

I have a solution:
I connected a simple switch between Brume an DSL-Router and there are no more link-downs or droppings.
Strange but solved.

2 Likes

Most unmanaged switches even have 802.3x flow control.

I do not work for and I do not have formal association with GL.iNet