Wireguard VPN: daemon.notice netifd: wgclient (8509): RTNETLINK answers: Permission denied

Routers
1

I am using a MT1300 Beryl router with the firmware version 4.3.7.

Suddenly I started to receive the following error seen from the VPN dashboard logs when trying to connect to a major VPN provider:

daemon.notice netifd: Interface 'wgclient' is setting up now
daemon.notice netifd: wgclient (5911): RTNETLINK answers: Permission denied
2023 daemon.notice netifd: Interface 'wgclient' is now down
2023 user.notice mwan3[6723]: Execute ifdown event on interface wgclient (unknown)
user.notice firewall: Reloading firewall due to ifdown of wgclient ()
daemon.notice netifd: Interface 'wgclient' is setting up now
daemon.notice netifd: wgclient (8509): RTNETLINK answers: Permission denied

Previously the VPN was working. I noticed this problem after toggling one or two settings on the router: (1) DNS settings which I then reverted to the original “Mode: Automatic” and (2) setting a timezone on the router.

I am writing to see if anyone else has encountered this problem. I will update this thread if I find additional helpful information.

1 Like
2

And to clarify, I have tried clicking the button “Update servers” in the VPN tab for Wireguard Client to update the servers from my provider.

3

I think I can answer my own question: the account for the VPN provider has expired.

4

I am having the same issue:

Thu Sep  5 23:24:25 2024 daemon.notice netifd: Interface 'wgclient' is now down
Thu Sep  5 23:24:25 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Thu Sep  5 23:24:35 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Thu Sep  5 23:24:35 2024 daemon.notice netifd: wgclient (24796): RTNETLINK answers: Permission denied

but my account is still active (I can connect just fine from my computer or my phone).

Some discussions (here and there) seem to suggest that deactivating ipv6 is the option.

As far as I can tell, IPV6 is not enabled in my Admin Panel. What could be the solution?

5

Which VPN provider do you use?

Is your key for WireGuard still active there?

6

Which VPN provider do you use?

Azire.

Is your key for WireGuard still active there?

I've used the router's configuration, it created a token on their end, and it should be working as far as I know. I looked around but don't know how to check if my key is still active -- I can connect just fine with other devices on the same account, using the same process.

7

I figured what the issue could be which i am also facing.

Currently I use a custom dns with a vpn, the problem is I cannot use my custom dns with my vpn

WGCLIENT interface is missing and says Unsupported protocol type.

8

Sorry for the noob question. What is a custom DNS here?

Fo example, I use Adguard and let it resolve the DNS. Would that be a problem?

I am using an GL-MT3000 and today I test it for the first time inside a network that I do not control and I can not connect home with my wireguard VPN as I could on the network I do control.

9

I had the same issue and nothing worked until I changed my password.

10

imo, it has nothing to do with the luci message of the protocol being unsupported, it is just gl software uses their own wg software which isn't the same as luci-proto-wireguard.

the error is something I have seen a extremely long time, but wireguard remains working, it also is a notice not a error.

I guess the wireguard interface lacks the netifd stuff so whenever a ifup or ifdown event occurs it shows this message as a warning.

It is harmless :smiley: