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

[Ranger802004]

***v3.0.1-beta2 has been released***

Release Notes:
v3.0.1-beta2 - 10/22/2024
Enhancements
- Added functionality to add ASNs to be routed over an interface.
- Added ADDCNAMES to Show Policy menu when viewing a policy.
- Optimized functionality to generate interface list when creating or editing a policy or ASN.
- Optimized functionality for boot delay timer and setting process priority.
- System Information under Configuration menu now shows status of dig and jq being installed.
- Domain VPN Routing will now check for WAN being connected and will error out when executing querypolicy, queryasn, or update if WAN is not connected.
- Minor optimizations

Fixes:
- Fixed an issue where IP FWMark rules were erroneously being deleted when editing or deleting a policy.
- Fixed an issue with executing the kill function to kill Domain VPN Routing processes, this was also happeneing in update mode.
- Fixed grammatical error on Main Menu for queryasn.
- Fixed error when editing a policy and getting an error for no NEWASININTERFACE variable.
- Fixed an erroroneous file being created under /jffs/configs/domain_vpn_routing/policy_all_domainlist ***It is safe to delete this file***
- Various minor fixes

 

[Ranger802004]

***v3.0.1 has been released***

Release Notes:
v3.0.1 - 10/26/2024
Enhancements
- Added functionality to add ASNs to be routed over an interface.
- Added ADDCNAMES to Show Policy menu when viewing a policy.
- Optimized functionality to generate interface list when creating or editing a policy or ASN.
- Optimized functionality for boot delay timer and setting process priority.
- System Information under Configuration menu now shows status of dig and jq being installed.
- Domain VPN Routing will now check for WAN being connected and will error out when executing querypolicy, queryasn, or update if WAN is not connected.
- Minor optimizations

Fixes:
- Fixed an issue where IP FWMark rules were erroneously being deleted when editing or deleting a policy.
- Fixed an issue with executing the kill function to kill Domain VPN Routing processes, this was also happeneing in update mode.
- Fixed grammatical error on Main Menu for queryasn.
- Fixed error when editing a policy and getting an error for no NEWASININTERFACE variable.
- Fixed an erroroneous file being created under /jffs/configs/domain_vpn_routing/policy_all_domainlist ***It is safe to delete this file***
- Various minor fixes

 

[Ranger802004]

***v3.0.2-beta1 has been released to the Beta Channel***

Release Notes:
v3.0.2-beta1 - 10/26/2024
Enhancements
- Added functionality to query the AdGuardHome log.
- 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.

 

[maghuro]

***v3.0.1 has been released***

Release Notes:
v3.0.1 - 10/26/2024
Enhancements
- Added functionality to add ASNs to be routed over an interface.
- Added ADDCNAMES to Show Policy menu when viewing a policy.
- Optimized functionality to generate interface list when creating or editing a policy or ASN.
- Optimized functionality for boot delay timer and setting process priority.
- System Information under Configuration menu now shows status of dig and jq being installed.
- Domain VPN Routing will now check for WAN being connected and will error out when executing querypolicy, queryasn, or update if WAN is not connected.
- Minor optimizations

Fixes:
- Fixed an issue where IP FWMark rules were erroneously being deleted when editing or deleting a policy.
- Fixed an issue with executing the kill function to kill Domain VPN Routing processes, this was also happeneing in update mode.
- Fixed grammatical error on Main Menu for queryasn.
- Fixed error when editing a policy and getting an error for no NEWASININTERFACE variable.
- Fixed an erroroneous file being created under /jffs/configs/domain_vpn_routing/policy_all_domainlist ***It is safe to delete this file***
- Various minor fixes

The ASN function is simply amazing!!!
It completely solved the problem I was trying to figure out, trying to redirect all traffic from my IPTV provider through wan.

Thank you so much

 

[ComputerSteve]

***v3.0.2-beta1 has been released to the Beta Channel***

Release Notes:
v3.0.2-beta1 - 10/26/2024
Enhancements
- Added functionality to query the AdGuardHome log.
- 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.

So with this new beta I can no longer query any policies.. They get stuck and just remain on the first domain indefinitely.

 

[js28194]

@Ranger802004 Thank you again for this script. A question on ASN. I see that adding an ASN ask's which interface, and shows the VPN client ovpnc1 is connected. What happens if you disconnect from vpn1 and connect to vpn2 via VPN Director? I know from a previous version, some kind soul provided the code to automate domain name routing when you switched vpn clients. Is there a way to automate this also or is it manual for now adding ASN to all 5 ovpncXX connections?

Thanks again.

 

[Tarek Yag]

Is it obligatory now to use the ASN function?

I hate getting an error message in my logs every time DomainVPNRouting runs, just because I don't use the new ASN feature!

domain_vpn_routing: Query ASN - ***No ASNs Detected***

I believe this message shouldn't be more than a notice!

 

[maghuro]

Is it obligatory now to use the ASN function?

I hate getting an error message in my logs every time DomainVPNRouting runs, just because I don't use the new ASN feature!


I believe this message shouldn't be more than a notice!

It's a notice.

Also, dev - my logs are full of debug messages. I can confirm I'm not in a beta.

Is it supposed?

 

[Tarek Yag]

It's a notice.

I'm running version 3.0.1 final, and I can confirm again it's an error here!
[UPDATE] I did a reboot and the message is still showing at error level in my syslog-ng setup.

 

[Ranger802004]

Is it obligatory now to use the ASN function?

I hate getting an error message in my logs every time DomainVPNRouting runs, just because I don't use the new ASN feature!


I believe this message shouldn't be more than a notice!

Open a GitHub issue and I can make an enhancement around it, thanks.

 

[Ranger802004]

@Ranger802004 Thank you again for this script. A question on ASN. I see that adding an ASN ask's which interface, and shows the VPN client ovpnc1 is connected. What happens if you disconnect from vpn1 and connect to vpn2 via VPN Director? I know from a previous version, some kind soul provided the code to automate domain name routing when you switched vpn clients. Is there a way to automate this also or is it manual for now adding ASN to all 5 ovpncXX connections?

Thanks again.

Yes this it the correct way to do it.

 

[Tarek Yag]

Open a GitHub issue and I can make an enhancement around it, thanks.

Done. Thanks a lot!

 

[Ranger802004]

***v3.0.2-beta2 released to the beta channel***

Release Notes:
v3.0.2-beta2 - 10/29/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.

 

[maghuro]

@Ranger802004
Regarding ASN...

Do they change? I'm asking because I don't know.

Isn't it better to check their IPs, I dunno, once a day? Once a week?

Right now the app is only checking the policies, not ASNs

Also - my logs are full of debug messages. I can confirm I'm not in a beta.

 

[Ranger802004]

@Ranger802004
Regarding ASN...

Do they change? I'm asking because I don't know.

Isn't it better to check their IPs, I dunno, once a day? Once a week?

Right now the app is only checking the policies, not ASNs

Also - my logs are full of debug messages. I can confirm I'm not in a beta.

Open a GitHub issue and the ASNs query for the IP subnets applicable to them that you have added to your ASN query list.

 

[maghuro]

Open a GitHub issue and the ASNs query for the IP subnets applicable to them that you have added to your ASN query list.

I didn't understand the ASN thing.

I added two ASN. They queried their IPs. And on the cronjob, they are never queried again...

 

[Ranger802004]

I didn't understand the ASN thing.

I added two ASN. They queried their IPs. And on the cronjob, they are never queried again...

They should start querying immediately after the policies and if they are small they will check all of the subnets for being in the proper ipset fairly quickly.

 

[maghuro]

They should start querying immediately after the policies and if they are small they will check all of the subnets for being in the proper ipset fairly quickly.

Oh I see.
The problem is that I haven't configured any policies.
So, when the cronjob runs, it doesn't detect any policy and then it doesn't query the ASN...

 

[Ranger802004]

Oh I see.
The problem is that I haven't configured any policies.
So, when the cronjob runs, it doesn't detect any policy and then it doesn't query the ASN...

Open a GitHub issue please.

 

[Ranger802004]

***v3.0.2-beta3 has been released to the Beta update channel***

Release Notes:
v3.0.2-beta3 - 11/02/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.