More back on topic: given the aforemetinoned netifd + WG aspect, does this Internet/VPN dropout occur when after all devices are connected first (eg: though the switch), then the Burme2 is rebooted w/ the VPN still engaged (read: set to automatically connect to WG on boot?):
(I’d like to point out I wouldn’t expect the whole network’s connected devices to be ‘bumped offline’ just because someone connected another bit of CAT to the switch. You may have discovered something ‘not quite right’ in the GL firmware.)
That could be a question of whatever VPN Policy you have set (eg: ‘Block All Non-VPN Traffic’) but I somehow suspect otherwise.
Cripes, this is maddening. Two questions:
Can you post the output of logread? It’s also available under GL GUI → System → Log → System Log (not the GL app itself).
Can you disconnect the VPN (removing it from the variables), reboot with all minus one connected device, reconnect said device after bootup & post those fresh logs?
What I’m looking for is a set of logs demonstrating the problem vs a ‘clean’ log (read: no VPN in the mix causing issues that I suspect may be a bug) so we can kick this up to GL. They’re in HK so there’s a time zone difference to say the least.
Nothing, as it stands, smells right to me. You’re doing everything I’d do but this… this… is a bit much.
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq-dhcp[23068]: DHCP, IP range 192.168.8.100 – 192.168.8.249, lease time 12h
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain test
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain onion
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain localhost
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain local
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain invalid
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain bind
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain lan
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain test
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain onion
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain localhost
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain local
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain invalid
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain bind
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using only locally-known addresses for domain lan
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using nameserver 162.252.172.57#53
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: using nameserver 149.154.159.92#53
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: read /etc/hosts - 4 addresses
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq[23068]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses
Thu Dec 14 16:30:10 2023 daemon.info dnsmasq-dhcp[23068]: read /etc/ethers - 0 addresses
Thu Dec 14 16:30:10 2023 user.notice mwan3[23070]: Execute ifdown event on interface wgclient (unknown)
Thu Dec 14 16:30:10 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Thu Dec 14 16:31:10 2023 daemon.notice netifd: Interface ‘wgclient’ is now down
Thu Dec 14 16:31:10 2023 user.notice mwan3[24947]: Execute ifdown event on interface wgclient (unknown)
Thu Dec 14 16:31:11 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Thu Dec 14 16:31:23 2023 kern.info kernel: [ 6154.691939] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Thu Dec 14 16:31:23 2023 kern.info kernel: [ 6154.697712] br-lan: port 1(eth1) entered disabled state
Thu Dec 14 16:31:23 2023 daemon.notice netifd: Network device ‘eth1’ link is down
Thu Dec 14 16:31:24 2023 daemon.notice netifd: bridge ‘br-lan’ link is down
Thu Dec 14 16:31:24 2023 daemon.notice netifd: Interface ‘lan’ has link connectivity loss
Thu Dec 14 16:31:25 2023 daemon.err eco: (gl-cloud:541) disconnected false 19 unexpected disconnect
Thu Dec 14 16:31:30 2023 daemon.debug eco: (gl-cloud:524) connected: true 0 connection accepted
Thu Dec 14 16:31:30 2023 daemon.debug eco: (gl-cloud:531) connected: 0 connection accepted
Thu Dec 14 16:31:35 2023 kern.info kernel: [ 6165.953344] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 100Mbps/Full - flow control off
Thu Dec 14 16:31:35 2023 kern.info kernel: [ 6165.961808] br-lan: port 1(eth1) entered blocking state
Thu Dec 14 16:31:35 2023 kern.info kernel: [ 6165.967036] br-lan: port 1(eth1) entered forwarding state
Thu Dec 14 16:31:35 2023 daemon.notice netifd: Network device ‘eth1’ link is up
Thu Dec 14 16:31:35 2023 daemon.notice netifd: bridge ‘br-lan’ link is up
Thu Dec 14 16:31:35 2023 daemon.notice netifd: Interface ‘lan’ has link connectivity
Thu Dec 14 16:33:30 2023 daemon.err eco: (gl-cloud:541) disconnected false 19 unexpected disconnect
Thu Dec 14 16:33:38 2023 daemon.err eco: (gl-cloud:249) fetch server fail: connect fail: connect: timeout
Thu Dec 14 16:33:38 2023 daemon.err eco: (gl-cloud:509) reconnect mqtt in 5s…
