AX-1800 wireguard vpn server DNS

when I connect to vpn using wireguard client, I am able to connect however I am not able to browse internet
I am using AX-1800

  • Version4.5.0
  • Firmware Typerelease8

Please try opening the cascading option

I tried cascading option, but no luck

make sure you have client profiles created verify what is the dns configured on each client files. check if you have adguard enabled try disabling once.

Please follow the General Troubleshooting part of this thread to provide further information:

"Client profiles are generated by the router portal. I’m unsure why I have DNS 64.6.64.6; to me, it should be 10.10.0.1. What are your thoughts on this?

[Interface]
Address = 10.10.0.2/24
PrivateKey = A***********************************************************
DNS = 64.6.64.6
MTU = 1420

[Peer]
AllowedIPs = 0.0.0.0/0,::/0
Endpoint = z******.glddns.com:83
PersistentKeepalive = 25
PublicKey = B*********************************************************
PresharedKey = D****************************************************"

also my adguard is down, following is screenshot of my phone running client with above config

You can alter the client profile for desire dns before using the profile. Lets say if you wish to have google dns go with 8.8.8.8 or 8.8.4.4

But if you are running any vpn client thn i prefer to use vpn dns.

Thank you for your guidance, @admon I have conducted general troubleshooting steps outlined in the provided link/guide. However, I am reluctant to reset the firmware as it would result in the loss of DHCP Address Reservation settings for numerous devices. Is there a method available to backup and restore this information?

yes, I tired with 1.1.1.1 and 8.8.8.8 and 8.8.4.4 with no luck, I do wish to use routers vpn dns so that i can access my local internet regardless of my location

I also notice lots of errors in my systemlog, not sure if they are related with wireguard
Sat Feb 10 10:12:43 2024 kern.warn kernel: [25941.100236] net_ratelimit: 10 callbacks suppressed
Sat Feb 10 10:12:43 2024 kern.crit kernel: [25941.100263] protocol 0800 is buggy, dev eth0

I end up restting the firmware, I suppose the issue occoured after firmware upgrade. the issue is fixed, however I still see errors in the log, is there a way to fix it?

Tue Feb 13 16:26:31 2024 daemon.notice wpa_supplicant[2933]: wlan-sta0: Unknown event 62
Tue Feb 13 16:26:31 2024 daemon.info lua: (…pkg-arm_cortex-a7/gl-sdk4-repeater/usr/sbin/repeater:567) <3>Unknown event 62
Tue Feb 13 16:26:32 2024 kern.crit kernel: [48369.720043] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:32 2024 kern.crit kernel: [48369.720092] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:34 2024 daemon.notice wpa_supplicant[2933]: wlan-sta0: Unknown event 62
Tue Feb 13 16:26:34 2024 daemon.info lua: (…pkg-arm_cortex-a7/gl-sdk4-repeater/usr/sbin/repeater:567) <3>Unknown event 62
Tue Feb 13 16:26:35 2024 kern.warn kernel: [48372.719972] net_ratelimit: 10 callbacks suppressed
Tue Feb 13 16:26:35 2024 kern.crit kernel: [48372.720005] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:35 2024 kern.crit kernel: [48372.723747] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:35 2024 kern.crit kernel: [48372.728146] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:35 2024 kern.crit kernel: [48372.732432] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:36 2024 kern.crit kernel: [48373.730036] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:36 2024 kern.crit kernel: [48373.730083] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:36 2024 kern.crit kernel: [48373.733461] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:36 2024 kern.crit kernel: [48373.737633] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:37 2024 kern.crit kernel: [48374.740018] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:37 2024 kern.crit kernel: [48374.740065] protocol 0800 is buggy, dev eth0
Tue Feb 13 16:26:40 2024 kern.warn kernel: [48377.739939] net_ratelimit: 10 callbacks suppressed