Slate 7 Pro connection issues with Wireguard Server

Router
1

Just got a Slate 7 Pro (love it)…. but it is having problems connecting to my Synology Wireguard server. I also have a GL-MT3000 connected to the same Synology Wireguard server with no issues. The Slate 7 wireguard client config is similar to the GM-MT3000 client config other than the few obvious. I am getting “Error: argument "mptcp_wgclient1" is wrong: table id value is invalid”

I tried adding to the route table but still no luck. Also, if you add to the route table, a reboot will remove the change.

vi /etc/iproute2/rt_tables
Added the following line:
100 mptcp_wgclient1

Thu Jul 16 16:21:01 2026 daemon.info dnsmasq[4428]: read /tmp/hosts/dhcp.wgclient1 - 3 addresses
Thu Jul 16 16:21:02 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Thu Jul 16 16:21:02 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Thu Jul 16 16:21:05 2026 daemon.info dnsmasq[4428]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Thu Jul 16 16:21:05 2026 daemon.info dnsmasq[4428]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Thu Jul 16 16:21:05 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Thu Jul 16 16:21:05 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Thu Jul 16 16:21:05 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Thu Jul 16 16:31:54 2026 daemon.notice netifd: Network device 'wgclient1' link is down
Thu Jul 16 16:31:54 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Thu Jul 16 16:31:55 2026 daemon.info dnsmasq[15658]: read /tmp/hosts/dhcp.wgclient1 - 3 addresses
Thu Jul 16 16:31:55 2026 daemon.info dnsmasq[15661]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Thu Jul 16 16:31:55 2026 daemon.info dnsmasq[15661]: read /tmp/hosts/dhcp.wgclient1 - 3 addresses
Thu Jul 16 16:31:55 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Thu Jul 16 16:31:55 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Thu Jul 16 16:31:57 2026 daemon.info dnsmasq[15661]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Thu Jul 16 16:31:57 2026 daemon.info dnsmasq[15661]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Thu Jul 16 16:31:57 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Thu Jul 16 16:31:57 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Thu Jul 16 16:31:57 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)

4

Hi,

The message “Error: argument "mptcp_wgclient1" is wrong: table id value is invalid” is related to an AWG-side service check and should not affect the normal use of WireGuard. There is no need to manually add the 100 mptcp_wgclient1 rule. If you have already added it, we recommend removing it.

Could you please check whether the Slate 7 Pro and MT3000 are using the same WireGuard configuration file at the same time? If so, please use a separate WireGuard configuration for each device to avoid potential connection conflicts.

5

As you see the separate Slate 7 Pro & MT3000 clients sessions. The MT3000 is working and transferring data. Slate 7 Pro is not.

Synology Wireguard Clients
Synology Wireguard Clients1163×352 19.8 KB

6

Hi,

Thank you for the update. We can see that the MT3000 and Slate 7 Pro are using separate WireGuard client sessions.
The Slate 7 Pro connection is established but has very limited traffic.
Could you please provide the following information from the Slate 7 Pro via SSH and send the results to us via private message.

wg show
ip rule show
ip route show table all

We will check the WireGuard status and routing information to further identify where the traffic issue occurs.
Thank you for your cooperation.