Allowing one domain/one address to bypass AirVPN

[rununtilyoufly 0]

I need to allow one address to bypass the VPN.
I prefer a locked down - VPN at the router solution - but I don't believe there's any flexibility in my Asus GT-AX11000 that would do such a thing.

To run Channels DVR on the same computer that I want to keep locked down behind VPN full time, I need to be able to allow access to one address for the checking, as per a bunch of research and digging this up on their forum. (see attached image)

Open to advice on different solutions, thank you all so much.

EDIT: The computer that I use is an Apple Silicon Mac, running the latest MacOS 14 Sonoma.

Edited ... by rununtilyoufly
added computer detail

[OpenSourcerer 1435]

5 hours ago, rununtilyoufly said:

but I don't believe there's any flexibility in my Asus GT-AX11000 that would do such a thing

Not terribly familiar with the setup on this router, but in the ovpn file you can add routes using --route, like so:

route 192.168.0.0 255.255.0.0 net_gateway

This would create a route to 192.168.0.0/16 via the gateway of the interface the connection is established over, i.e., outside the VPN. Maybe you can set routes somewhere in the GUI, or reimport such a prepared config?

[rununtilyoufly 0]

Sadly, inputting it with the IP addresses of what I need to route outside of the VPN, it's just throwing an "error - check configuration" regardless of uploading it that way or adding it in the area to add information. Hopefully someone comes along that's faced this head on with these devices/firmware and has an answer, but truly, thank you!

[OpenSourcerer 1435]

23 hours ago, rununtilyoufly said:

Sadly, inputting it with the IP addresses of what I need to route outside of the VPN, it's just throwing an "error - check configuration" regardless of uploading it that way or adding it in the area to add information

In case you misformatted it – can you post one such a line you wrote?

[rununtilyoufly 0]

On 11/7/2023 at 1:29 PM, OpenSourcerer said:

In case you misformatted it – can you post one such a line you wrote?

 

route 104.21.71.35 255.255.0.0 net_gateway
route 172.67.142.202 255.255.0.0 net_gateway

which should be the ip addresses that community.getchannels.com needs to bypass the VPN with.

Thank you!

[OpenSourcerer 1435]

Hm, it's correctly done, then.
 

On 11/6/2023 at 9:15 PM, rununtilyoufly said:

Hopefully someone comes along that's faced this head on with these devices/firmware and has an answer, but truly, thank you!

Guess we need to resort to that. Sorry!

[rununtilyoufly 0]

1 hour ago, OpenSourcerer said:

Hm, it's correctly done, then.
 

Guess we need to resort to that. Sorry!

Nothing to be sorry for, I appreciate you trying to help.
I really feel as if that must be right. 

Is there a way in a Wireguard config file to do similar, or would it cancel out as well?
I'm just trying to figure out the best plan of action here, even if that means *not* doing it at the router level yet still making sure nothing but what I approve passes by the VPN on the Mac mini (M2, Apple Silicon)

[OpenSourcerer 1435]

1 hour ago, rununtilyoufly said:

Is there a way in a Wireguard config file to do similar, or would it cancel out as well?

Wireguard only knows the AllowedIPs directive which indicates which IP ranges are to be routed via VPN. An exclusion must be done with so-called DisallowedIPs calculators which calculate a longer list of allowed IP ranges, excluding those you don't want to be routed. We had this just recently in another thread:.