skeal
Part of the Furniture
Bottom area of VPN client page.Where do you find this setting?
Ok then its likely not related to your VPN. What settings do you have for DNS?When everything went down, my OpenVPN status still said it was connected.
Bottom area of VPN client page.Where do you find this setting?
Ok then its likely not related to your VPN. What settings do you have for DNS?When everything went down, my OpenVPN status still said it was connected.
Oh, Im not using Policy rules. Its set to All.Bottom area of VPN client page.
On the OpenVPN Client settings, Accept DNS Configuration is set to disabled.Ok then its likely not related to your VPN. What settings do you have for DNS?
Next time it goes down SSH into the router and check stubby:Oh, Im not using Policy rules. Its set to All.
On the OpenVPN Client settings, Accept DNS Configuration is set to disabled.
In the WAN settings, its set to my router (I have Stubby installed).
/opt/etc/init.d/S61stubby check
stubby -C /opt/etc/stubby/stubby.yml -i
/opt/etc/init.d/S61stubby restart
On this command you want to look at the bottom most line of it's output.stubby -C /opt/etc/stubby/stubby.yml -i
IKEv2 issue in RT-AC5300
VPN Server IPSec IKEv2 does not work for my since I upgraded to 384.10. My clients are iOS devices (iPhones and iPads). With prior version 384.9 all work perfectly. My custom scripts are same from here: https://www.snbforums.com/threads/asus-ipsec-vpn-server.44973/#post-473984
Downgrading to 384.9 makes IKEv2 works again.
Stooopid question time: Would I know I was using strongswan if I was? I have no clue what this is, but I know lots of stuff runs on the router that I have no clue what it is.384.10 upgraded to a much newer Strongswan version. You might need to update your configuration to match with the new version.
384.10 upgraded to a much newer Strongswan version. You might need to update your configuration to match with the new version.
Thanks for the reply! The router went into a reboot loop. I was not able to get out of the loop so I had to do a RMA. Hopefully they can fix it. I ended up buying another AC86U."Channel 0" usually indicates that the wifi radio is down/crashed/dead. Try power cycling your router.
The RT-AC86U driver is unchanged in 384.10.
I encountered that two days ago. The second 5 GHz radio of my development RT-AC5300 died![]()
Bottom area of VPN client page.
Ok then its likely not related to your VPN. What settings do you have for DNS?
I am looking to upgrade but want to do a clean install from scratch. All previous upgrades have been dirty.
Will the router loose the DDNS setting when I reset back to factory settings?
This topic has come up a lot this past week. There are two settings that affect how DNS is handled by the OpenVPN Client - Accept DNS Configuration and Redirect Internet Traffic.My primary connection is over VPN and with DNS strict all traffic goes through VPN. If for whatever reason VPN disconnects, Stubby takes over. This is how it works. Just because you have Stubby you dont need to set DNS too disabled.
ThanXYes, but you can setup it again.
ThanX
Hope to have some time alone at home to upgrade. something on my router is choking my internet.
I'll have to install each component and test as I move along.
This topic has come up a lot this past week. There are two settings that affect how DNS is handled by the OpenVPN Client - Accept DNS Configuration and Redirect Internet Traffic.
In the OpenVPN Client, if you set Accept DNS Configuration = Exclusive and use Policy Rules or Policy Rules (Strict), dnsmasq will be bypassed and the OPenVPN Client will "exclusively" use the DNS of the VPN Provider. The Diversion ad blocker written by @thelonelycoder will not work with this configuration as Diversion requires dnsmasq to work. Diversion will work if you set Redirect Internet Traffic to All.
If you want the OpenVPN client to use dnsmasq + Diversion, there are two options available to resolve the DNS and routing issues when using Policy Rules with Asuswrt-Merlin:
The definition of the Accept DNS Configuration field values are as follows:
- Set Accept DNS Configuration to “Strict” and specify the DNS server for the VPN tunnel to use by adding the dhcp-option DNS command in the Custom Configuration section. Without the dhcp-option command, Diversion updates will fail, the Diversion email function will no longer work and the wget command will not able to resolve the domain name.
- My preferred recommendation is to install Stubby DNS over TLS. Stubby will encrypt DNS queries. To enable the OpenVPN Client to use Stubby, set Accept DNS Configuration to “Disabled”.
- Disabled: DNS servers pushed by VPN provided DNS server are ignored.
- Relaxed: DNS servers pushed by VPN provided DNS server are prepended to the current list of DNS servers, of which any can be used.
- Strict: DNS servers pushed by the VPN provided DNS server are prepended to the current list of DNS servers, which are used in order (existing DNS servers are only used if VPN provided ones don’t respond).
- Exclusive: Only the pushed VPN provided DNS servers are used.
Stooopid question time: Would I know I was using strongswan if I was? I have no clue what this is, but I know lots of stuff runs on the router that I have no clue what it is.![]()
Problem is with cyphersuite and OpenSSL version used. When an iOS device connects to VPN using IKEv2, Strongswan crashes and restart after negotiation.

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!