Beta Asuswrt-Merlin 386.3 beta is now available

[octopus]

Since 192.168.12.0/24 appears twice in your rules, there is a conflict. DNS exclusion only considers the Local IP. Not sure what the expected behavior is in this scenario.

Yes that's what I think it also started after this modification. I just want to see if it can be fixed or if it is an expected function.

https://github.com/RMerl/asuswrt-merlin.ng/commit/00e83f928e501f4e4d0fcf434aafb53057605a4b

 

[mvadu]

with DNS set to "Exclusive" does the router still resolve the local peers? With the older firmware clients using the tunnel with DNS set to "Exclusive" would not resolve the local peers even though they are using router as DNS server. Is it something that can be done (i.e. to allow for local peers to be resolved, but use the VPN provider DNS for everything else) in strict mode?

 

[Laxarus]

For VPN director, is it possible to use domain names instead of remote IP addresses for selective routing?

 

[RMerlin]

For VPN director, is it possible to use domain names instead of remote IP addresses for selective routing?

No.

 

[Laxarus]

No.

I hope you can consider adding that. It would be a most welcome addition since manually finding out ips 1-by-1 and adding them are not very practical.

 

[nzwayne]

@nzwayne, there is no Beta 3.

yeah...Beta 2. Thks.

 

[dave14305]

Yes that's what I think it also started after this modification. I just want to see if it can be fixed or if it is an expected function.

https://github.com/RMerl/asuswrt-merlin.ng/commit/00e83f928e501f4e4d0fcf434aafb53057605a4b

Perhaps a WAN rule should be ignored for DNS if it also has a Remote IP defined?

 

[RMerlin]

I hope you can consider adding that. It would be a most welcome addition since manually finding out ips 1-by-1 and adding them are not very practical.

Not possible. A routing table works with IP addresses, not text.

 

[RMerlin]

Perhaps a WAN rule should be ignored for DNS if it also has a Remote IP defined?

It used to be back in the vpnrouting.sh days. I don't remember if that was re-implemented with VPN Director, I would have to check.

 

[jerry6]

386.3 beta working well on my 5300
Thanks

 

[octopus]

.

It used to be back in the vpnrouting.sh days. I don't remember if that was re-implemented with VPN Director, I would have to check.

I saw you have fixed this issue. Thanks

Is it supposed to apply all WAN-rule to all vpn-clients chain when you not specific "Remote IP"?

 

[RMerlin]

Is it supposed to apply all WAN-rule to all vpn-clients chain when you not specific "Remote IP"?

WAN rules will always have priority over any other rules.

 

[iTyPsIDg]

I dirty flashed from 386.2_4 to 386.3 Beta 1 on Friday. I noticed that my Guest Network VPNs worked fine, but my main network wouldn't go through the VPN at all. I also noticed that I still have the old dropdown without VPN Director listed:

Spoiler: no VPN director option

If I select Policy Rules (strict) I can't change the option back to anything else.

Today, I reflashed with Beta 2, then I did a full reset and reconfigured everything manually. I still don't see VPN director in the dropdown and my traffic still doesn't go through the VPN.

My Unbound configuration does go through the VPN, so according to DNS Leak Test, my DNS IP is correct but my LAN doesn't go through the VPN at all.

 

[octopus]

I dirty flashed from 386.2_4 to 386.3 Beta 1 on Friday. I noticed that my Guest Network VPNs worked fine, but my main network wouldn't go through the VPN at all. I also noticed that I still have the old dropdown without VPN Director listed:

Spoiler: no VPN director option

View attachment 35000

If I select Policy Rules (strict) I can't change the option back to anything else.

Today, I reflashed with Beta 2, then I did a full reset and reconfigured everything manually. I still don't see VPN director in the dropdown and my traffic still doesn't go through the VPN.

My Unbound configuration does go through the VPN, so according to DNS Leak Test, my DNS IP is correct but my LAN doesn't go through the VPN at all.

If you missed that part in changelog , here it is

Spoiler: Changelog

Asuswrt-Merlin 386/NG Changelog
===============================

386.3 (xx-xxx-xxxx)
- NOTE: First time you boot into this version, you need to
either shift-reload the main index page, or clear
your browser cache.

 

[iTyPsIDg]

If you missed that part in changelog , here it is

Spoiler: Changelog

Asuswrt-Merlin 386/NG Changelog
===============================

386.3 (xx-xxx-xxxx)
- NOTE: First time you boot into this version, you need to
either shift-reload the main index page, or clear
your browser cache.

I cleared the browser cache and tried shift-reload, but it still doesn't mention VPN Director in that dropdown.

 

[dave14305]

I cleared the browser cache and tried shift-reload, but it still doesn't mention VPN Director in that dropdown.

Show us exactly what version number the router shows you.

 

[iTyPsIDg]

Show us exactly what version number the router shows you.

 

[dave14305]

View attachment 35003

Is x3mrouting overwriting the default VPN Client page?
Test with:

umount /www/Advanced_OpenVPNClient_Content.asp

Refresh GUI page. Be happy. Put x3mrouting page back:

mount -o bind /jffs/addons/x3mRouting/Advanced_OpenVPNClient_Content.asp /www/Advanced_OpenVPNClient_Content.asp

 

[iTyPsIDg]

Is x3mrouting overwriting the default firmware page?

I'm not sure I fully understand. Do you mean this page?

Spoiler: Firmware page

 

[dave14305]

I'm not sure I fully understand. Do you mean this page?

Spoiler: Firmware page

View attachment 35005

I edited my post above just now.