Thanks for the notice. I have not experienced this on AC88U and AC86U models. Did you do this after a recent firmware upgrade from 384.x to 386.x? The upgrade may require an hour or so to settle down before the GUI works properly. What firmware version and router model are you using?
What is your goal? What are you trying to accomplish? That might help determine the best route you should take.
Actually, I already got what I wanted. The router now has monstrous performance. I just pointed out this X3mrouting anomaly
Sorry, I can't help on the screen issues. The only thing I can thing of is you already had some existing entries that can't convert. If you still want to use the screen, wipe out the current client config first then, enter the configuration.
I tried to do what you wrote but it doesn't work. I am forced to use option 2 or I don't get what I want. I followed the tutorial on this page:
www.snbforums.com
Are you using the modified x3mRouting Advanced OpenVPN Screen as a hack for DNS leak issue with Unbound? My guess is you are using it to create the fwmarks so the script you are using can avail of them. If that is all you need, we can come up with a solution that does not require the modified x3mRouting Open VPN client screen. The purpose of the screen is to route IPSET lists thru VPN or bypass to the WAN interface. I don't see you routing any IPSET lists in the screen picture you posted. I have the x3mRouting screen working on AC88U and AC86U (HND CPU) with 386.x production and beta releases without any of the issues you describe. No one else has reported the issue. So, I am struggling in how to assist. Did you factory reset after moving to 386.x?I tried to do what you wrote but it doesn't work. I am forced to use option 2 or I don't get what I want. I followed the tutorial on this page:
Unbound - Unbound DNS VPN Client w/policy rules
I put everything in functions and made a few little tweaks. I still need to add comments and incorporate a couple of checks to make sure the user has everything configured/installed as expected. User configuration: Unbound - running as system resolver X3mRouting - installed (must have rules to...
I created the 3 files as indicated on the page and in any case followed the whole tutorial. With these 3 files and the x3mRouting option 2 installed everything works. Even if I had to reboot the router, he does execute commands etc. If you need to change the VPN configuration, you must first uninstall option 2, then modify and finally install option 2 again. start to the VPN and then I would have the DNS exposed. If I don't install option 2, on every boot, I have to manually stop the cliet vpn and then restart it. To not use option 2 it would take two commands that once booted, first disable the vpn server and then enable it again
I still think it would help us to know your vision for what you believe success looks like. For example, I'm assuming you want to route DNS through the VPN so that you don't have DNS leaking. Your link to @Swinson 's post makes me think that. I found that when I was trying to accomplish eliminating DNS leaks.
That's right, I'm using x3mRouting to route DNS through the VPN. But that tutorial only works if you install x3mRouting option 2. In any case, I did a matsre reset on the router, removed the usb stick and formatted it. I restarted from zero obviously using GNUton's 386 beta3. I put back AMTM, swap, Entware and then I immediately tried x3mRouting and I confirm that it creates the same anomaly that I indicated. If I install option 2 I can no longer touch the VPN server page or it gives me a configuration error. I will point this anomaly to GNUton.
/jffs/scripts/unbound_via_vc1.sh stop &/jffs/scripts/unbound_via_vc1.sh stop &#!/bin/sh
Check_Tun11_Con() {
ping -c1 -w1 -I tun11 1.1.1.1
}
Delete_Rules() {
iptables-save | grep "unbound_rule" | sed 's/^-A/iptables -t mangle -D/' | while read CMD;do $CMD;done
}
Add_Rules() {
iptables -t mangle -A OUTPUT -d "$wan0_dns0"/32 -p udp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x8000/0x8000
iptables -t mangle -A OUTPUT -d "$wan0_dns1"/32 -p udp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x8000/0x8000
iptables -t mangle -A OUTPUT -d "$wan0_dns0"/32 -p tcp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x8000/0x8000
iptables -t mangle -A OUTPUT -d "$wan0_dns1"/32 -p tcp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x8000/0x8000
Iptables -t mangle -A OUTPUT -p tcp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x1000/0x1000
iptables -t mangle -A OUTPUT -p udp --dport 53 -m comment --comment unbound_rule -j MARK --set-mark 0x1000/0x1000
}
Unbound_vc1() {
Add_Rules
/jffs/addons/unbound/unbound_manager.sh vpn=1 &
logger -st "($(basename "$0"))" $$ Ending Script Execution
}
Unbound_vpnDisable() {
Delete_Rules
/jffs/addons/unbound/unbound_manager.sh vpn=disable &
logger -st "($(basename "$0"))" $$ Ending Script Execution
}
Poll_Tun11() {
Delete_Rules
sleep 5
timer=5
while [ $timer -lt 300 ]; do
Check_Tun11_Con
if [ "$?" -eq 0 ]; then
Unbound_vc1
logger -st "($(basename "$0"))" $$ Ending Script Execution
exit 0
fi
sleep 1
timer++
done
logger -st "($(basename "$0"))" $$ Script Execution Timeout
exit 3
}
if [ -z "$1" ]; then
logger -st "($(basename "$0"))" $$ Script Arg Missing
exit 1
else
logger -st "($(basename "$0"))" $$ Starting Script Execution
wan0_dns0="$( (nvram get wan0_dns) | awk '{print $1}' )"
wan0_dns1="$( (nvram get wan0_dns) | awk '{print $2}' )"
if [ "$wan0_dns1" = "" ]; then
wan0_dns1 = $wan0_dns0
elif [ "$wan0_dns0" = "" ]; then
wan0_dns0 = $wan0_dns1
if [ "$wan0_dns1" = "" ]; then
logger -st "($(basename "$0"))" $$ wan0_dns is NULL
exit 2
fi
else
case "$1" in
start)
Poll_Tun11
exit 0;;
stop)
Unbound_vpnDisable
exit -1;;
*)
logger -st "($(basename "$0"))" $$ Script Arg Invalid
exit 1;;
esac
fi
fiThere were many changes in the OpenVPN GUI and some supporting scripts in the 384.19 and 346.x releases. I monitor changes to those files as Merlin codes. I then update the x3mRouting master repo when Asuswrt-Merlin goes to production release. I suspect there is a difference in one of those support files in the DSL fork that are creating the conditions you are experiencing. When there are changes such as this, I always save off the prior version as a branch. Some people have reasons as to why they can't update to a new version. So saving off some of these older versions allow them to us it. I didn't see the source code files on the GitHub page for the DSL fork so I couldn't do any analysis. If you were still on the 384.19 release, I could have you try the version of x3mRouting that is compatible to see if the problem still exists. The solution @iTyPsIDg posted looks interesting. I will test it out on my end and see if I can add it to x3mRouting as a new feature.
The first two files are different than those in the post you indicated below. I tried the configuration you proposed but it doesn't work, I still have the DNS exposed. I then returned to the configuration that is present in the post you indicated and everything works, I have secure DNS. Obviously I must have x3mRouting option 2 installed or the DNS will be exposed
Thank you for your reply and for your commitment. The router however sunfiona and I am using the configuration with x3mRouting, as I explained earlier. If you can fix the anomaly I mentioned, great. At that point I would change the way to use the VPN tunnel etc.
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!
