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

[iTyPsIDg]

There is currently no method of bulk deletion short of deleting the entire policy and creating a new one.

Thank you. That is not a problem. Might I suggest a note in the README to avoid doing what I did and what @js28194 suggested? It seems natural that people will attempt to bulk delete in this manner which will cause problems.

 

[js28194]

I haven't tested this yet, but after bulk delete in the file, I'm not sure what happens if completely delete the corresponding policy_yourpocliyname_domaintoip file. I think the script recreates it basically "cleaning up" the ip addresses albiet in a round about way.

 

[ComputerSteve]

So question @Ranger802004 I'm noticing that my GT-AX11000 Pro running your latest beta script and running 3006 codebase firmware is displaying when I run the terminal command liststats -> vpnc_ipset6 ... I don't know what that is ? If I go to my GT-AX11000 running merlin 3004 codebase and your latest beta of the script I don't see vpnc_ipset6 listed when I run liststats in terminal... Is this normal ? Do I need this ?

 

[Ranger802004]

So question @Ranger802004 I'm noticing that my GT-AX11000 Pro running your latest beta script and running 3006 codebase firmware is displaying when I run the terminal command liststats -> vpnc_ipset6 ... I don't know what that is ? If I go to my GT-AX11000 running merlin 3004 codebase and your latest beta of the script I don't see vpnc_ipset6 listed when I run liststats in terminal... Is this normal ? Do I need this ?

I’m not sure what is creating this, please open a GitHub issue so we can investigate.

 

[Ranger802004]

***v3.1.1-beta4 has been released to the beta channel***
Review your policies to make sure your DNS servers have not been erroneously added to the policies Domain to IP lists. If they are added use the deleteip function to remove.

Release Notes:
v3.1.1-beta4 - 04/23/2025
Enhancements:
- If DNS-over-TLS is enabled and servers are configured on the system DNS-over-TLS DNS server list, dig will configure use for DNS-over-TLS by randomly selecting a DNS-over-TLS DNS server.
- Python3 and dig are required to be installed for this functionality.
- An existing DNS configuration for the interface in Domain VPN Routing will override this functionality.
- Added debug logging for DNS-over-TLS configuration during querypolicy function execution.

Fixes:
- Fixed an issue with IPv4 unreachable rules being created for VPN interfaces due to a missing default route for the VPN routing table.
- Fixed an issue where restoreasncache was executing when restoring an individual policy, this will still execute when restoring all policies.
- Fixed issues with erroneous data being ingested by dig.
- Fixed an issue with dig applying DNS Server configuration incorrectly and causing unreturned data from queries.
- Minor fixes and optimizations

 

[Ranger802004]

***v3.1.1 has been released to production channel***

Release Notes:
Enhancements:
- If DNS-over-TLS is enabled and servers are configured on the system DNS-over-TLS DNS server list, dig will configure use for DNS-over-TLS by randomly selecting a DNS-over-TLS DNS server.
- Python3 and dig are required to be installed for this functionality.
- An existing DNS configuration for the interface in Domain VPN Routing will override this functionality.
- Added debug logging for DNS-over-TLS configuration during querypolicy function execution.

Fixes:
- Fixed an issue with IPv4 unreachable rules being created for VPN interfaces due to a missing default route for the VPN routing table.
- Fixed an issue where restoreasncache was executing when restoring an individual policy, this will still execute when restoring all policies.
- Fixed issues with erroneous data being ingested by dig.
- Fixed an issue with dig applying DNS Server configuration incorrectly and causing unreturned data from queries.
- Minor fixes and optimizations