Automatize the insertion or deletion of IP #s

[aldebaran 0]

Hello,

 

I have set my air vpn set so that it does not show any ip leaks and for this use the IP #s 10.4.0.1 and 10.5.0.1. Without these it does not hide the leak nor does it work the other way around. It causes DNS accessibility issues when I leave the IP 's inside and connect over my ISP. 

 

However, in addition to the camouflaged or latent connection, I also need to have a normal connection over my ISP as well since I have a web presence with a few websites and a server etc. So it is a bit of a chore to every time add or remove these IP #s according to the connection I want to use.

 

Is there a work around the ritual?

 

Regards,

 

aldebaran

[Staff 10334]

Hello,

 

you might write a script to modify your routing table after the push from our server, so that traffic to some destination IP addresses will not be tunneled. However feel free to elaborate if we have misunderstood your needs.

 

See here (for Windows, but the same applies to any OS with the due syntax modifications):

https://airvpn.org/topic/3721-netflix/?do=findComment&comment=3724

 

Kind regards

[NaDre 161]

Hello,

 

I have set my air vpn set so that it does not show any ip leaks and for this use the IP #s 10.4.0.1 and 10.5.0.1. Without these it does not hide the leak nor does it work the other way around. It causes DNS accessibility issues when I leave the IP 's inside and connect over my ISP. 

 

However, in addition to the camouflaged or latent connection, I also need to have a normal connection over my ISP as well since I have a web presence with a few websites and a server etc. So it is a bit of a chore to every time add or remove these IP #s according to the connection I want to use.

 

Is there a work around the ritual?

 

Regards,

 

aldebaran

 

You may be interested in this approach:

 

https://airvpn.org/topic/9289-dns-leaks-and-how-to-fix-them/?do=findComment&comment=9978

 

I use my native interface most of the time. And so using AirVPN's DNS servers is impractical. So I use the approach outlined in the above post to avoid DNS leaks. The one concern is whether AirVPN's "double hop" geo-location stuff is compatible with my approach.