Page 1 of 1
Connection Disconnect - ZBT-WG1608 issues
Posted: Sun Aug 28, 2022 12:56 pm
by ςЯaʒyн0ʁ§ëto
Hi everyone!
I'm running a ZBT-WG1608 (16M) / MediaTek MT7621 /GoldenOrb_2022-08-25 (OpenWrt 21.02 SNAPSHOT
I have been doing some searching on this forum and could find nothing that might be comparable to my issue. I love to tinker when it comes to technology, however I am no technology specialist. I'd consider myself a borderline newbie still. So please go easy on me.
The issue I am having is my wan0 drops connection, which forces the external IP to drop. This forces a reboot of the modem. Also I have a box connected that overrides other device's assigned IP addresses...
Attached is a system log file.
Thank you in advance for any help!
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Mon Aug 29, 2022 9:36 am
by Didneywhorl
There may be a hardware watchdog present that is not seeing the connection, causing the wan0 to ifdown/ifup.
Does your wg1608 have the watchdog enabled?
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Mon Aug 29, 2022 9:50 am
by ςЯaʒyн0ʁ§ëto
Didneywhorl wrote: ↑Mon Aug 29, 2022 9:36 am
There may be a hardware watchdog present that is not seeing the connection, causing the wan0 to ifdown/ifup.
Does your wg1608 have the watchdog enabled?
Hi,
Thank you for the reply, may I know where I need to go to locate this "watchdog"?
Thank you
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Mon Aug 29, 2022 10:06 am
by Didneywhorl
WG1608-Watchdog-Jumper.png
If this 0 Ohm resistor isn't there as a jumper, then you have the hardware watchdog turned ON. If the resistor is there, you're good.
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Mon Aug 29, 2022 12:10 pm
by ςЯaʒyн0ʁ§ëto
Hi,
Thank you for the update, is there a way to check through the router settings to see instead of having to open the unit?
Thank you
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Mon Aug 29, 2022 7:38 pm
by Didneywhorl
Nope.
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Sun Sep 04, 2022 11:43 am
by ςЯaʒyн0ʁ§ëto
Attached is an updated system/kernal log... recently disconnected... Seems to be condensed and easier, perhaps to find issue.
Thank you
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Tue Sep 06, 2022 12:25 pm
by ςЯaʒyн0ʁ§ëto
Didneywhorl wrote: ↑Mon Aug 29, 2022 10:06 am
WG1608-Watchdog-Jumper.png
If this 0 Ohm resistor isn't there as a jumper, then you have the hardware watchdog turned ON. If the resistor is there, you're good.
Just confirming I have the 0 Ohm resistor.
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Thu Sep 08, 2022 8:49 am
by ςЯaʒyн0ʁ§ëto
Any suggestions, since I determined that the jumper is installed?
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Thu Sep 08, 2022 9:12 am
by Didneywhorl
Give us more details if you would. Not everyone will read the kernel log file unfortunately, though I do.
What I see is a ton of dhcp server errors and a software watchdog (ping tests) resetting the modem.
I would remove all the extra features (base factory defaults) and setup one new thing at a time until you find the breakdown.
You have too much going on to simply ask why your having disconnects.
The reboots are from the ping tests/watchdog failing. It cant send out icmp checks to 1.1.1.1 and so its resetting the interface.
Re: Connection Disconnect - ZBT-WG1608 issues
Posted: Thu Sep 08, 2022 2:10 pm
by mtl26637
If you sort through the 2nd log you will find :
Code: Select all
Sun Sep 4 12:33:46 2022 user.info mwan3track[12895]: Check (ping) failed for target "1.1.1.1" on interface wan1 (wwan0). Current score: 10\
Sun Sep 4 12:33:50 2022 user.info mwan3track[12895]: Check (ping) failed for target "1.0.0.1" on interface wan1 (wwan0). Current score: 10\
Sun Sep 4 12:33:50 2022 user.notice mwan3track[12895]: Interface wan1 (wwan0) is disconnecting\
Sun Sep 4 12:33:50 2022 user.notice URL-DEBUG: hotplug (iface): action='disconnecting' interface='wan1'\
Sun Sep 4 12:33:56 2022 daemon.info dnsmasq-dhcp[7796]: DHCPREQUEST(br-lan) 192.168.1.208 00:1a:79:74:62:1a\
Sun Sep 4 12:33:56 2022 daemon.info dnsmasq-dhcp[7796]: DHCPNAK(br-lan) 192.168.1.208 00:1a:79:74:62:1a address in use\
Sun Sep 4 12:33:59 2022 user.info mwan3track[12895]: Check (ping) failed for target "1.1.1.1" on interface wan1 (wwan0). Current score: 9\
Sun Sep 4 12:34:01 2022 kern.warn kernel: [22385.663612] ------------[ cut here ]------------\
Sun Sep 4 12:34:01 2022 kern.warn kernel: [22385.668299] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:473 dev_watchdog+0x2fc/0x304\
Sun Sep 4 12:34:01 2022 kern.info kernel: [22385.676602] NETDEV WATCHDOG: wwan0 (qmi_wwan): transmit queue 0 timed out\
The watchdog (mwan3 ping test) seems to be working normal but looks like your device is freezing up while sending data (transmit queue timeout). I've seen this on various quectel modems. It can be caused by various things such as overheating or not enough power, etc. What mode is it running in? If QMI, might try MBIM or something different, might get lucky.