DomainVPNRouting Domain VPN Routing v3.0.0-beta2 ***Release***

[Ranger802004]

Domain VPN Routing is a tool used to route specific website domains to specific VPN tunnels or override all traffic being routed to a VPN tunnel to directly route through a WAN interface.

***v3.0.0-beta2 Release****
This is the release information regarding v3.0.0-beta2, please read the notes carefully prior to installing.

Readme - https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/readme.txt

Script - https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/domain_vpn_routing.sh

Install Command:

/usr/sbin/curl -s "https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/domain_vpn_routing-beta.sh" -o "/jffs/scripts/domain_vpn_routing.sh" && chmod 755 /jffs/scripts/domain_vpn_routing.sh && sh /jffs/scripts/domain_vpn_routing.sh install

Updating:
If v2.x.x is currently installed, enable Dev Mode in the configuration menu and perform an update to receive this beta release.

Support:
- Submit a ticket via GitHub here.

Release Notes:
v3.0.0-beta2 - 10/04/2024
Enhancements:
- Added functionality to support wildcards for subdomains. Example: *.example.com ***Requires DNS Logging to be enabled***
- Added DNS Overrides for VPN Client interfaces, when a policy is configured with a specific interface it will use the system default DNS Server unless a DNS override is configured for that specific interface in the configuration menu.
- Domain queries will now utilize dig if it is installed and will bypass use of nslookup.
- If dig is installed, a policy can be configured to allow CNAMES of domains to be added to the policy domain list automatically during query execution. This is disabled by default for existing policies and can be enabled using the editpolicy function.

Fixes:
- Reduced names of IPSets to allow policy names to have a max length of 24 characters.
- Fixed issue that caused RT-AC68U and DSL-AC68U to lock up on execution due to limitation of 2 OpenVPN Client slots.
- Domain VPN Routing will now check the IP version and test it for compability.
- Fixed an issue with beta update channel.

 

[Ranger802004]

Minor fixes were applied to v3.0.0-beta1, check for updates and verify your checksum matches the repo version and if not perform an update to get the revision.

 

[ComputerSteve]

Domain VPN Routing is a tool used to route specific website domains to specific VPN tunnels or override all traffic being routed to a VPN tunnel to directly route through a WAN interface.

***v3.0.0-beta1 Release****
This is the release information regarding v3.0.0-beta1, please read the notes carefully prior to installing.

Readme - https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/readme.txt

Script - https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/domain_vpn_routing.sh

Install Command:

/usr/sbin/curl -s "https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/domain_vpn_routing/domain_vpn_routing-beta.sh" -o "/jffs/scripts/domain_vpn_routing.sh" && chmod 755 /jffs/scripts/domain_vpn_routing.sh && sh /jffs/scripts/domain_vpn_routing.sh install

Updating:
If v2.x.x is currently installed, enable Dev Mode in the configuration menu and perform an update to receive this beta release.

Release Notes:
v3.0.0-beta1 - 09/29/2024
Enhancements:
- Added functionality to support wildcards for subdomains. Example: *.example.com ***Requires DNS Logging to be enabled***
- Added DNS Overrides for VPN Client interfaces, when a policy is configured with a specific interface it will use the system default DNS Server unless a DNS override is configured for that specific interface in the configuration menu.
- Domain queries will now utilize dig if it is installed and will bypass use of nslookup.
- If dig is installed, a policy can be configured to allow CNAMES of domains to be added to the policy domain list automatically during query execution. This is disabled by default for existing policies and can be enabled using the editpolicy function.

Fixes:
- Reduced names of IPSets to allow policy names to have a max length of 24 characters.
- Fixed issue that caused RT-AC68U and DSL-AC68U to lock up on execution due to limitation of 2 OpenVPN Client slots.
- Domain VPN Routing will now check the IP version and test it for compability.

Can I use this with AdGuard home ?? If so.. how do I enable logging for DNSMasq ? Or do I not need DNSMasq since I’m using AdGuard home ? Or do I run both ? Can you run both ?

 

[Ranger802004]

Can I use this with AdGuard home ?? If so.. how do I enable logging for DNSMasq ? Or do I not need DNSMasq since I’m using AdGuard home ? Or do I run both ? Can you run both ?

I responded to you in GitHub.

 

[Ranger802004]

v3.0.0-beta2 has been released to address an update issue with the beta channel.

 

[maghuro]

@Ranger802004 how to enable dns logging?

Google didn't help me...

 

[ComputerSteve]

@Ranger802004 how to enable dns logging?

Google didn't help me...

Ranger has explained this to me !
To enable DNS logging you would create the file /jffs/configs/dnsmasq.conf.add (If it does not exist already) and then add the following lines to the file.

log-queries
log-facility=/var/log/dnsmasq.log

Restart DNSMasq

service restart_dnsmasq

 

[maghuro]

Ranger has explained this to me !
To enable DNS logging you would create the file /jffs/configs/dnsmasq.conf.add (If it does not exist already) and then add the following lines to the file.

log-queries
log-facility=/var/log/dnsmasq.log

Restart DNSMasq

service restart_dnsmasq

Unfortunatelly, for some reason, some error occurs. When I enter app settings, it shows the following:

System Information:
DNS Logging Status Status: Disabled
DNS Log Path Log Path: /var/log/dnsmasq.logno-resolv
WAN FWMark WAN FWMark: 0x8000
WAN Mask WAN Mask: 0xf000
WAN Reverse Path Filter WAN RP Filter: Loose Filtering

 

[maghuro]

Unfortunatelly, for some reason, some error occurs. When I enter app settings, it shows the following:

System Information:
DNS Logging Status Status: Disabled
DNS Log Path Log Path: /var/log/dnsmasq.logno-resolv
WAN FWMark WAN FWMark: 0x8000
WAN Mask WAN Mask: 0xf000
WAN Reverse Path Filter WAN RP Filter: Loose Filtering

I managed to fix it.

Now, when I query a policy, this happens (when I have wildcards domains, for example *.meo.pt)


Select the Policy You Want to Query: 2
Query Policy: MeoTV
: No such file or directory
: No such file or directory
: No such file or directory

 

[Ranger802004]

Unfortunatelly, for some reason, some error occurs. When I enter app settings, it shows the following:

System Information:
DNS Logging Status Status: Disabled
DNS Log Path Log Path: /var/log/dnsmasq.logno-resolv
WAN FWMark WAN FWMark: 0x8000
WAN Mask WAN Mask: 0xf000
WAN Reverse Path Filter WAN RP Filter: Loose Filtering

Because you have /var/log/dnsmasq.log and no-resolv on the same line in your add on dnsmasq file in /jffs/configs/dnsmasq.conf.add.