go558a83nk

For over a month Draco has been down with line problems. Staff, do you have an estimate as to when it'll be up again?

Same here, using Firefox. And, when I do visit ipleak.net firefox seems to "crash" and it won't resolve any more domains but otherwise works. But, nslookup via command line still works. So, I know it's just firefox. Other DNS leak test sites still work.

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.

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.

Please be more specific. Are you using the router as the OpenVPN client? If so, what speed to that same server do you get if you use the AirVPN software (Eddie) on a PC? If not using the router as OpenVPN client then it's practically irrelevant and the problem lies elsewhere. If you get higher speeds with Eddie on a PC than with the router as OpenVPN client, then you know the problem is the relatively slow CPU on the router.

no that that's a router, was this company a kickstarter or something like that at one point or another? yes, if I recall correctly.

Is your server running and listening on the port that you're assigned?

I don't think there's a guide and I wouldn't expect one...you're already beyond 99% of users.

First I've heard of this. I'm curious too.

no, it means that right now AirVPN only supports IPv4 connections (except on 2 test servers) and that ipv6 is disabled when connecting. if you enable ipv6 in the latest Eddie beta and connect to the test servers which support ipv6, then you'll have both while connected to VPN.

So, you insist that somehow AirVPN can fix the internet? I guess they should take that as a compliment.

nothing, just switch servers like you did. if it is a route problem between you and the server how do you think you can fix it anyway? just be glad you have options.

This is working as intended far as I understand.

no, there's not a problem. If you have no ISP IPv6 address and/or you're not connecting to AirVPN servers with IPv6 enabled then you'll see what you see.

Nothing to be worried about? It literally kills my connection until I manually disconnect and reconnect. For about the last hour I've been trying to download some torrents and it almost instantly kills my connection, so far I've got about 20MB out of the 5GB+ I'm trying to download. I've tried limiting the speed in my torrent client but at this point it seems that I can't download torrents with out it killing my connection. If I can't figure this out there's no point in even having a VPN. sounds like you have a device or software that's interfering.

Well, assuming you connect to a server that's not overloaded, it's not an AirVPN problem. It's just a matter of fact with VPN and that you're using a connection that's likely relegated to low priority by your ISP and transit/peer providers. Sure, some ports and protocols may not be as affected by traffic shaping as others. Your best bet is to test to different locations (not different servers in the same location) and find one that works best for you. It will work best because the path between you and that server is most conducive to good speed, not because those servers are inherently better.

That's only very few errors. Nothing to be worried about.

The hope is that tls-crypt UDP sessions can defeat firewalls yet give better performance than the TCP tunnel required with SSL. But, I haven't seen anybody post about their experience in China with tls-crypt yet.

I've never done that but sounds like it'll work.

It will resolve to whatever server in Canada is least busy at the time. So, it does change.

10.4.0.1 is only accessible through the VPN tunnel. It's best to just pick a server and use its IP address.

Have you tried TCP 443?