go558a83nk

If it was working before but not now

1) check to make sure the server you're trying to connect to is operational

2) perhaps something changed in your local network or your ISP and UDP 53 (the port and protocol you're trying to use according to the log) is now blocked.  Try TCP 443 just to see if that's the problem.

Change the log verbosity to 4 to get more information which could help you determine why it's not working.

Hello,

 

Since I was trying to set it up on a router, I didn't realize I needed to install Eddie to run these prompts. Now that Eddie is installed, I'm assuming my IP is the one under "Stats" that says "IP Entry" and it appears I was right with my guess of the VPN DNS (I found the one I gave you on a random page on airvpn.org)

 

​However, I still don't understand what I'm doing wrong with the command line (as in "Terminal" on my mac).

 

I'm currently connected to Heze and tried "uslookup heze.airservers.org" as well as "us.all.vpn.airdns.org" and "usa.all.vpn.airdns.org"

 

Thoughts?

nslookup heze.airservers.org

and

nslookup us.all.vpn.airdns.org

work for me

It's good to see stuff like this in the forums.  Compared to two years ago I think Air forums have lost a lot of knowledgeable users so this is refreshing.

I don't think I'll have an opportunity to use this as I use pfense but I hope somebody finds it useful.

Online Sessions: 14770 - BW: 41983 Mbit/s

Since the DNS problem a few days ago sessions and bandwidth has been down in my perception.

I wish Air kept a graph for the whole network like they do for each server.