any part of 10.0.0.0/24 or fd00::/8 AirVPN will not use?

[NaDre 159]

EDIT: The title should of course have been "any part of 10.0.0.0/8 or fd00::/8 AirVPN will not use?"

 

Since Gen 2 is still a work in progress, I thought it would be better to ask this question now rather than later.

 

Some of us may want to have private IPv4 or IPv6 addresses on our LAN that will not conflict with AirVPN. I guess we can assume that AirVPN will leave 192.168.0.0/16 and 172.16.0.0/12 alone?

 

But does AirVPN reserve the right to use any part of 10.0.0.0/8? Or is there part of 10.0.0.0/8 that AirVPN promises not to use?

 

Same question for IPv6 private addresses. Is there any part of fd00::/8 that AirVPN promises not to use?

 

===

 

For readers who do not understand what this is about see this:

 

https://en.wikipedia.org/wiki/Private_network#Private_IPv6_addresses

 

Other VPN providers will probably use private addresses in 10.0.0.0/8 and fd00::/8 too.

 

AirVPN has just changed its strategy for assigning private IPv4 subnets with Gen2. See this:

 

https://airvpn.org/topic/28391-proper-resolvconf-nameserver/?p=74937

 

AirVPN only used a few IPv4 subnets (e.g. 10.4.0.0/16 or 10.5.0.0/16) before Gen2.

[Staff 10116]

Hello!
 
In Generation 2 subnets are smaller and unique to each server OpenVPN daemon. In this way multi-homing becomes much easier and any (unlikely) overlapping with your local subnet somewhere in 10.0.0.0/8 can immediately be resolved by changing server.
 
In IPv6, our assigned ULAs are in fde6:7a:7d20::/48 - even here collisions with your local addresses are very unlikely.

 

Kind regards