DomainVPNRouting Domain VPN Routing v3.0.4 ***Release***

[Ranger802004]

***v3.0.2 has been released***

Release Notes:
v3.0.2 - 11/05/2024
Enhancements:
- Added functionality to query the AdGuardHome log. This can be enabled or disabled via the QUERYADGUARDHOMELOG configuration option.
- Created option to enable/disable Domain VPN Routing under configuration menu.
- During uninstallation, a prompt has been added to ask to back up the configuration. When reinstalling Domain VPN Routing a backup file will be checked for existence and prompted to restore configuration.
- Removed log message regarding No ASNs being detected if queryasn function is being executed by querypolicy for all policies.
- Enhanced prompts in querypolicy mode.
- Added log message stating length of processing time for querypolicy function.
- Minor optimizations.

Fixes:
- Fixed script locking mechanism when executing querypolicy or queryasn from the UI menu.
- Fixed issue where ASNs were not queried by cron job if no domain policies were created.

 

[Ranger802004]

***v3.0.3 has been released***

Release Notes:
v3.0.3 - 11/08/2024
Fixes:
- Fixed an issue with new installations of Domain VPN Routing.

 

[Ranger802004]

***v3.0.4-beta1 has been released to the beta update channel***

Release Notes:
v3.0.4-beta1 - 11/13/2024
Fixes:
- Fixed an issue that would add erroneous CNAME values into a policy domain list when dig was being used to lookup CNAMES.

 

[privacyguy123]

This new ASN feature seems like it could be super powerful, can you explain how you are using it and how I would get ASN numbers to add?

 

[maghuro]

This new ASN feature seems like it could be super powerful, can you explain how you are using it and how I would get ASN numbers to add?

Let's see.
I want to redirect all traffic of my ISP through WAN. They have around 35 prefixes, and also can change on future.
Instead of adding all of them manually to vpn director, you use the ASN AS15525 and they are automagically added and updated.

Before searching for "ASNs to add", you have to ask yourself what you want to do.

Let's see: "I want all Microsoft traffic to go through vpn because I don't trust them and etc." Then, you search "Microsoft ASN" on Google and then you'll find AS8075

 

[Ranger802004]

***v3.0.4-beta2 has been released to the beta update channel***

Release Notes:
v3.0.4-beta2 - 11/19/2024
Fixes:

• Fixed an issue that would add erroneous CNAME values into a policy domain list when dig was being used to lookup CNAMES.
• Fixed an issue when using the deleteip function to delete an IP address.

 

[Ranger802004]

***v.3.0.4 has been released***

Release Notes:
v3.0.4 - 11/27/2024
Fixes:
- Fixed an issue that would add erroneous CNAME values into a policy domain list when dig was being used to lookup CNAMES.
- Fixed an issue when using the deleteip function to delete an IP address.

 

[cohomology]

Let's see.
I want to redirect all traffic of my ISP through WAN. They have around 35 prefixes, and also can change on future.
Instead of adding all of them manually to vpn director, you use the ASN AS15525 and they are automagically added and updated.

Before searching for "ASNs to add", you have to ask yourself what you want to do.

Let's see: "I want all Microsoft traffic to go through vpn because I don't trust them and etc." Then, you search "Microsoft ASN" on Google and then you'll find AS8075

If I have vpn directors(asus built-in), domain based policies(before asn was introduced), asn polocies etc. etc., which one gets executed when there is a conflict?

 

[Ranger802004]

If I have vpn directors(asus built-in), domain based policies(before asn was introduced), asn polocies etc. etc., which one gets executed when there is a conflict?

They are based on their priority in the ip rules and it is interface based, the marked traffic for interfaces have a higher priority (lower value) than VPN Director rules and in the following order. So there is never a "conflict" just a higher priority will be applied before a lower priority.

WAN Interfaces - 150
OVPNC1 - 1000
OVPNC2 - 2000
OVPNC3 - 3000
OVPNC4 - 4000
OVPNC5 - 5000
WGC1 - 6000
WGC2 - 7000
WGC3 - 8000
WGC4 - 9000
WGC5 - 10000

 

[js28194]

My testing show's that VPN Director rules are 1st, then Domain based policy rules. They do not conflict with each other. They work together sequentially.

 

[cohomology]

They are based on their priority in the ip rules and it is interface based, the marked traffic for interfaces have a higher priority (lower value) than VPN Director rules and in the following order. So there is never a "conflict" just a higher priority will be applied before a lower priority.

WAN Interfaces - 150
OVPNC1 - 1000
OVPNC2 - 2000
OVPNC3 - 3000
OVPNC4 - 4000
OVPNC5 - 5000
WGC1 - 6000
WGC2 - 7000
WGC3 - 8000
WGC4 - 9000
WGC5 - 10000

I see. What matters is not where it is defined but which interface a it references to.

 

[cohomology]

I also want to say ASN is a game changer, based on the short period I used it. Thank you so much!