ANSWERED AirVPN API - Status Endpoint Discussion

[Esurient 0]

I'm looking at building out a script which automatically runs SpeedTests and checks the IP address in the DroneBL list for abused IPs,

I've first looked at the AirVPN API under the status endpoint as this seems to represent all the servers and whilst this works, I've noticed that some IPs are not the same, e.g. connecting to server 1 will show you that the subnet is x.x.x.211, where as in the status endpoint we can see that this server should only have, x.x.x.215, x.x.x.216 and x.x.x.218

Is the Status endpoint out of date or just does not represent the full network stack?

[Tech Jedi Alex 1515]

Which server is that? It looked a bit like Asterope (UK) as it's the only one with .215 and .216 entry addresses, but its exit is .213. What do you mean by "subnet"? That info is not yielded by the status endpoint.

And, if there is one info the status endpoint does not yield, it's the exit address. It can be queried via DNS, though.

[Esurient 0]

That was just an example,

I did a check now on Germany, Adhil,

Connected I have the IP 37.46.199.70, however reading the status API only 37.46.199.66, 37.46.199.67, 37.46.199.68 and 37.46.199.69 are exposed in the IPv4 entry whilst the client is stating it is using entry 3 (x.68),

If I'm not wrong, if I were to do a DNS query on all DE servers, I get 

dig ANY de.all.vpn.airdns.org @dns1.airvpn.org +short
141.98.102.234
185.189.112.18
83.143.245.50
185.189.112.26
37.46.199.50
185.104.184.42
37.46.199.66
37.46.199.82
141.98.102.178
37.120.217.242
141.98.102.186
141.98.102.242
141.98.102.226
185.189.112.10

On the IPv4 section, which still does not match up the IP address I'm assigned.

Edit: I have geo routing disabled.
 

[Tech Jedi Alex 1515]

You are technically not getting assigned the IP, you're using the address of the server. But anyway, entry and exit IP addresses have been separate since time immemorial, the latter of which is irrelevant for clients wanting to connect, so it's not emitted by the status API.
There are two ways to get that info, though.

• Query servername_exit.airservers.org. This one is used by Eddie for route checks.
• When connected, curl check.airservers.org (with /api for JSON, and prepend ipv4./ipv6. for specific IP version), see Specs, section VPN DNS Server > Special resolution & URLs.

Actually, I was trying to find some documentation on that separation, but neither the FAQ nor the specs mention this. But it's in every server and sale announcement. Little bit of inconsistency there.  So, now you know.

[Esurient 0]

9 minutes ago, Tech Jedi Alex said:

You are technically not getting assigned the IP, you're using the address of the server. But anyway, entry and exit IP addresses have been separate since time immemorial, the latter of which is irrelevant for clients wanting to connect, so it's not emitted by the status API.
There are two ways to get that info, though.

• Query servername_exit.airservers.org. This one is used by Eddie for route checks.
• When connected, curl check.airservers.org (with /api for JSON, and prepend ipv4./ipv6. for specific IP version), see Specs, section VPN DNS Server > Special resolution & URLs.

Actually, I was trying to find some documentation on that separation, but neither the FAQ nor the specs mention this. But it's in every server and sale announcement. Little bit of inconsistency there.  So, now you know.

Oh that's perfect, now I can get rid of the subnet scanning behavior from the app and speed up the db check,

Thanks for the help!

Hope they add this into the FAQ or other relevant page.