MS Teams drops connections (SLATE AX in Repeater mode + WG-Client)

Technical Support for Routers
1

Hi,

first of all, I see there are some topics about issues with MS Teams sessions using glinet products, but I do not see some generally accepted solution. Someone playing with MTUs, some updating firmware etc etc

So my situation.
I have following setup:
Laptop -> wired connection to SLATE AX with active WG client ---> wifi6 to INTERNET
---> Home WG server on a router (not glinet)
Firmware: * 4.6.11 release2

Periodically I am doing calls in MS Teams and every time I have strange connection drops.
Today had it twice during 20min call

  1. first time connection drops. Router start flashing with blue light.
    My actions: I disconnected ethernet - connect again - login to SLATE GUI - it was trying to connect to WIFI (since I am connecting to wan via WIFI)
  2. connection drops in strange manner: i can see my callee live, can hear him - but he was saying that "I am disconnected again" etc etc.
    My actions: just disconnect/reconnect ethernet and call-in to meeting again

I got some logs from period of todays call. I think first disconnection was at 15:37.
Second at 15:48

LOG

Fri Mar 21 15:37:07 2025 daemon.notice netifd: Network device 'wgclient' link is up

Fri Mar 21 15:37:07 2025 daemon.notice netifd: Interface 'wgclient' is now up

Fri Mar 21 15:37:07 2025 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=3 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_467 group_3434 group_6401 group_1455 peer_2002 group_4018 peer_7516 CONFIG_cfg030f15_ports=

Fri Mar 21 15:37:07 2025 user.notice firewall: Reloading firewall due to ifup of wgclient (wgclient)

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8647]: Connected to system UBus

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: started, version 2.85 cache disabled

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: DNS service limited to local subnets

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: 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

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: UBus support enabled: connected to system bus

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq-dhcp[8649]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain test

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain onion

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain localhost

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain local

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain invalid

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain bind

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using only locally-known addresses for domain lan

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using nameserver 1.0.0.1#53

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: using nameserver 1.1.1.1#53

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: read /etc/hosts - 4 addresses

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq[8649]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses

Fri Mar 21 15:37:08 2025 daemon.info dnsmasq-dhcp[8649]: read /etc/ethers - 0 addresses

Fri Mar 21 15:37:17 2025 daemon.info dnsmasq-dhcp[4151]: DHCPREQUEST(br-lan) 192.168.8.245 48:65:ee:1d:4e:29

Fri Mar 21 15:37:17 2025 daemon.info dnsmasq-dhcp[4151]: DHCPACK(br-lan) 192.168.8.245 48:65:ee:1d:4e:29 EPPLWROW041A

Fri Mar 21 15:37:23 2025 daemon.info hostapd: wlan1: STA 1c:53:f9:05:5b:4d IEEE 802.11: authenticated

Fri Mar 21 15:37:23 2025 daemon.notice hostapd: wlan1: STA-OPMODE-N_SS-CHANGED 1c:53:f9:05:5b:4d 2

Fri Mar 21 15:37:23 2025 daemon.info hostapd: wlan1: STA 1c:53:f9:05:5b:4d IEEE 802.11: associated (aid 1)

Fri Mar 21 15:37:23 2025 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 1c:53:f9:05:5b:4d 0 0

Fri Mar 21 15:37:23 2025 daemon.info hostapd: wlan1: STA 1c:53:f9:05:5b:4d RADIUS: starting accounting session 868752A0F29915F0

Fri Mar 21 15:37:23 2025 daemon.info hostapd: wlan1: STA 1c:53:f9:05:5b:4d WPA: pairwise key handshake completed (RSN)

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPDISCOVER(br-lan) 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPOFFER(br-lan) 192.168.8.143 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPDISCOVER(br-lan) 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPOFFER(br-lan) 192.168.8.143 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPDISCOVER(br-lan) 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPOFFER(br-lan) 192.168.8.143 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPREQUEST(br-lan) 192.168.8.143 1c:53:f9:05:5b:4d

Fri Mar 21 15:37:26 2025 daemon.info dnsmasq-dhcp[4151]: DHCPACK(br-lan) 192.168.8.143 1c:53:f9:05:5b:4d Dining-room-TV

Fri Mar 21 15:37:59 2025 daemon.info gl-cloud[5919]: (gl-cloud.lua:297) fetch server from: https://gslb-eu.goodcloud.xyz/getbucket

Fri Mar 21 15:37:59 2025 daemon.info gl-cloud[5919]: (gl-cloud.lua:579) connect mqtt broker: 18.209.114.161 18883

Fri Mar 21 15:38:00 2025 daemon.info gl-cloud[5919]: (gl-cloud.lua:652) conack: 0 connection accepted

Fri Mar 21 15:44:00 2025 daemon.notice netifd: wwan (7401): udhcpc: sending renew to 141.54.65.1

Fri Mar 21 15:44:00 2025 daemon.notice netifd: wwan (7401): udhcpc: lease of 172.23.5.206 obtained, lease time 900

Fri Mar 21 15:48:44 2025 daemon.notice netifd: Network device 'eth2' link is down

Fri Mar 21 15:48:44 2025 kern.info kernel: [ 839.988131] nss-dp 3a001400.dp3 eth2: PHY Link is down

Fri Mar 21 15:48:44 2025 kern.info kernel: [ 839.988445] br-lan: port 2(eth2) entered disabled state

Fri Mar 21 15:48:46 2025 daemon.notice netifd: Network device 'eth2' link is up

Fri Mar 21 15:48:46 2025 kern.info kernel: [ 841.988129] nss-dp 3a001400.dp3 eth2: PHY Link up speed: 1000

Fri Mar 21 15:48:46 2025 kern.info kernel: [ 841.988205] br-lan: port 2(eth2) entered forwarding state

Fri Mar 21 15:48:46 2025 kern.info kernel: [ 841.992900] br-lan: port 2(eth2) entered forwarding state

Fri Mar 21 15:48:48 2025 daemon.info dnsmasq-dhcp[4151]: DHCPREQUEST(br-lan) 192.168.8.245 48:65:ee:1d:4e:29

Fri Mar 21 15:48:48 2025 daemon.info dnsmasq-dhcp[4151]: DHCPACK(br-lan) 192.168.8.245 48:65:ee:1d:4e:29 EPPLWROW041A

Fri Mar 21 15:48:54 2025 kern.info kernel: [ 849.997806] br-lan: port 2(eth2) entered forwarding state

Fri Mar 21 15:49:10 2025 daemon.info dnsmasq-dhcp[4151]: DHCPREQUEST(br-lan) 192.168.8.245 48:65:ee:1d:4e:29

Fri Mar 21 15:49:10 2025 daemon.info dnsmasq-dhcp[4151]: DHCPACK(br-lan) 192.168.8.245 48:65:ee:1d:4e:29 EPPLWROW041A

Fri Mar 21 15:51:30 2025 daemon.notice netifd: wwan (7401): udhcpc: sending renew to 141.54.65.1

2

Hello,

I checked syslog, it seems that only the process of wgclient enabled was at 15:37. The entire log did not see WG vpn drops connection, which means that WG is running without any issue during this period.

At 15:48, the WG vpn was not disconnected, but the eth2 port was disconnected (the corresponding physical port is LAN1), causing this wired client (PC) to disconnect the Internet access, then the connection was restored within a few seconds.

  1. Please change a more reliable network cable.
  2. Please connect to the LAN2 port and observe it.
  3. Please try connecting the router via the wireless WiFi.
4

Thanks for your reply!
Disconnection of eth2 may be part of my manual action "to restore" connection, as described above for my actions to fix disconnection#2 ..Still worth to try your suggestions.
But there was first disconnection (at ~15:37) which has no visibility in logs, correct? (I see logs i pasted actually starting from that time, but previous logs were from 14:30 or smth)

5

Yep, since you attached logs have not occurred the disconnect issue.
You can share the whole logs like begin from 14:30, to the disconnect issue occurs.

6

Captured some new logs for the issue (maybe its another issue though..): looks like WG client restarts for some reason.
Could you help me to understand what happened below?

Wed Apr  9 14:27:47 2025 daemon.info dnsmasq-dhcp[6888]: DHCPREQUEST(br-lan) 192.168.8.245 48:65:ee:1d:4e:29
Wed Apr  9 14:27:47 2025 daemon.info dnsmasq-dhcp[6888]: DHCPACK(br-lan) 192.168.8.245 48:65:ee:1d:4e:29 MACHINE_NAME
Wed Apr  9 14:41:19 2025 daemon.warn dnsmasq[29289]: Maximum number of concurrent DNS queries reached (max: 150)
Wed Apr  9 14:41:32 2025 daemon.info dnsmasq[29289]: exiting on receipt of SIGTERM
Wed Apr  9 14:41:32 2025 daemon.notice netifd: Network device 'wgclient' link is down
Wed Apr  9 14:41:32 2025 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Wed Apr  9 14:41:32 2025 daemon.notice netifd: Interface 'wgclient' is now down
Wed Apr  9 14:41:32 2025 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed Apr  9 14:41:32 2025 user.notice root: disable GRO on wgclient
Wed Apr  9 14:41:41 2025 daemon.info dnsmasq-dhcp[6888]: DHCPREQUEST(br-lan) 192.168.8.245 48:65:ee:1d:4e:29
Wed Apr  9 14:41:41 2025 daemon.info dnsmasq-dhcp[6888]: DHCPACK(br-lan) 192.168.8.245 48:65:ee:1d:4e:29 MACHINE_NAME
7

Hello,

This syslog does not show the reason why wgclient is dropped4. .

  1. Is it possible that the router's Internet fluctuation?
  2. Is it possible that VPN server have problem?
  3. If we want to check the reason, please share the entire syslog file "logread.tar", and check ping www.google.com and ping 8.8.8.8 in the router SSH during the issue occurs.