Mt 300 loose wifi connection randomly

Hello, I use the mt 300 with a wifi connection to my own wifi, provided by a huawei mini travelrouter. Everything what I describe is without using VPN!
So when I connect the mt 300 to my wifi everything works fine for a while. Then the connection drops and comes back after a short time then the game starts again…
Of course I surveilled that the original wifi is still providing internet during those dropouts.
How can I create a stable connection to my wifi?

Hi,

please share the log files of the Mango so a staff member of GL could assist you.

Which ones do you need and where do I find them?

More logs = better :wink:

Mon Dec 18 18:53:58 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Dec 18 18:54:01 2023 daemon.notice netifd: Network device ‘wgclient’ link is up
Mon Dec 18 18:54:01 2023 daemon.notice netifd: Interface ‘wgclient’ is now up
Mon Dec 18 18:54:02 2023 daemon.info procd: - init complete -
Mon Dec 18 18:54:03 2023 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Mon Dec 18 18:54:05 2023 daemon.err usbmuxd[5137]: [18:54:05.665][3] usbmuxd v1.1.1 starting up
Mon Dec 18 18:54:05 2023 daemon.err usbmuxd[5137]: [18:54:05.705][3] Using libusb 1.0.24
Mon Dec 18 18:54:05 2023 daemon.err usbmuxd[5137]: [18:54:05.712][3] Initialization complete
Mon Dec 18 18:54:05 2023 daemon.err usbmuxd[5137]: [18:54:05.728][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with “–exit” to trigger.
Mon Dec 18 18:54:09 2023 cron.err crond[2782]: time disparity of 1278 minutes detected
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: started, version 2.86 cachesize 150
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Mon Dec 18 18:54:10 2023 daemon.warn dnsmasq[1]: warning: ignoring resolv-file flag because no-resolv is set
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.7.100 – 192.168.7.249, lease time 12h
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using nameserver 127.0.0.1#5453
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses
Mon Dec 18 18:54:10 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Dec 18 18:54:10 2023 user.notice wgclient-up: env value:T_J_V_ifname=string J_V_address_external=1 USER=root ifname=wgclient ACTION=KEYPAIR-CREATED N_J_V_address_external=address-external SHLVL=2 J_V_keep=1 HOME=/ HOTPLUG_TYPE=wireguard T_J_V_interface=string J_V_ifname=wgclient T_J_V_link_up=boolean LOGNAME=root DEVICENAME= T_J_V_action=int TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin CONFIG_LIST_STATE= J_V_interface=wgclient K_J_V= action ifname link_up address_external keep interface J_V_link_up=1 J_V_action=0 T_J_V_address_external=boolean N_J_V_link_up=link-up T_J_V_keep=boolean PWD=/ JSON_CUR=J_V CONFIG_SECTIONS=global AzireVPN Mullvad FromApp group_7040 group_6 group_2973 group_8729 peer_2001 peer_2002 peer_2003 peer_2004 peer_2005 peer_2006 peer_2007 peer_2008 peer_2009 peer_2011 peer_2012 peer_2013 CONFIG_cfg030f15_ports=
Mon Dec 18 18:54:15 2023 user.notice mwan3[5809]: Execute ifup event on interface loopback (lo)
Mon Dec 18 18:54:15 2023 user.notice mwan3[5809]: Starting tracker on interface loopback (lo)
Mon Dec 18 18:54:19 2023 user.info mwan3rtmon[4536]: Detect rtchange event.
Mon Dec 18 18:54:21 2023 user.notice firewall: Reloading firewall due to ifup of loopback (lo)
Mon Dec 18 18:54:27 2023 user.notice mwan3[6296]: Execute ifup event on interface wwan (apcli0)
Mon Dec 18 18:54:28 2023 user.notice mwan3[6296]: Starting tracker on interface wwan (apcli0)
Mon Dec 18 18:54:32 2023 user.info mwan3rtmon[4536]: Detect rtchange event.
Mon Dec 18 18:54:34 2023 user.notice firewall: Reloading firewall due to ifup of wwan (apcli0)
Mon Dec 18 18:54:38 2023 user.notice mwan3[6917]: Execute ifup event on interface wgclient (wgclient)
Mon Dec 18 18:54:39 2023 user.notice mwan3[6917]: Starting tracker on interface wgclient (wgclient)
Mon Dec 18 18:54:42 2023 user.info mwan3rtmon[4536]: Detect rtchange event.
Mon Dec 18 18:54:43 2023 user.notice firewall: Reloading firewall due to ifup of wgclient (wgclient)
Mon Dec 18 18:58:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.7.155 b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.7.155 b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:17 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:17 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.7.155 b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.7.155 b8:f6:b1:1b:7c:79
Mon Dec 18 18:58:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.7.155 b8:f6:b1:1b:7c:79 TROXX
Mon Dec 18 19:01:52 2023 daemon.notice netifd: Network device ‘wgclient’ link is down
Mon Dec 18 19:01:52 2023 daemon.notice netifd: wgclient (15527): sh: 1: unknown operand
Mon Dec 18 19:01:53 2023 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Mon Dec 18 19:01:54 2023 user.notice mwan3[15526]: Execute ifdown event on interface wgclient (unknown)
Mon Dec 18 19:01:56 2023 daemon.notice netifd: Interface ‘wgclient’ is now down
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: started, version 2.86 cachesize 150
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.7.100 – 192.168.7.249, lease time 12h
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using nameserver 127.0.0.1#5453
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq[1]: read

System Log
/tmp/hosts/dhcp.cfg01411c - 3 addresses
Mon Dec 18 19:01:59 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Dec 18 19:02:05 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

inb4 keepalive.           

Here are todays logfiles which have any content.
Archiv.zip (19.7 KB)

I don’t know what you mean. I’m a 64 yrs old man without any computer Tech Skills, but need help!

Hello, is nobody out there to assist me with my problem?

Standby @stefa , @admon & I go in & out of this forum & its threads & often poke fun/make jokes, quips at each other & to our own determent.

Give me a couple hours to find the time to really read over the logs & try to see what’s going on. In the mean time tell your WireGuard client connection to send a ‘heartbeat’ to the Server. See GL GUI → VPN → WireGuard Client → […] → Add ‘PersistKeepalive = 25’ to the [Peer] section:

Restart your WG Client after doing so. That may help clear things up.

I’m not seeing much in the logs. Who’s your VPN provider for the WG service/link?

Its all without any VPN to rule out that the fault is due to the VPN.
When everything is done and work fine i will run a VPN over Windscribe.

Oh, well; I’ve been completely misreading this thread… but do add that keepalive directive once you get your VPN connected. As for the Wi-Fi dropping can you do a site survey/scan of your vicinity for congestion?