Staff

I believe I have an answer for my own question.  According to this video:http://www.youtube.com/watch?v=-7EzElm5v2Q
FiOS does traffic shape using DPI (Deep Packet Inspection).  We have to hide OpenVPN connection to not be throttled using an SSL tunnel over port 443.  Luckily, AirVPN provides that option.
 
Using a tunnel now gets me to 55/35.  Much better than the 10 I was getting.
 
Just letting other FiOS/AirVPN customers know that this is the way to do get better performance.  Thanks to those who helped above.

Hi, 
this is a an important question.
 
We have recorded a dramatic increase of clients requiring connections to NL servers in the past weeks and months. With the increase of single connected clients (consider that since April a user can connect simultaneously three clients and also consider that Air user base has grown up considerably during this year), we must take into account different variables to a server load in addition to available bandwidth.
 
CPUs of our servers not only must handle TLS auth and OpenVPN AES-256 encryption/decryption, but also SSH and OpenSSL additional tunnels. There is, so far, no scientific study which determines how the CPU load increases (under the same provided bandwidth) with the increase of connected clients in an OpenVPN server, but empirically it might be not linear (example: 50 clients requiring 1 Mbit/s each stress CPU more than one client requiring 50 Mbit/s does). So, we could have a server that has a line and a port of 1 Gbit/s, but whose CPU gets at capacity before that limit (for example already at 650 Mbit/s). Therefore, in order to respect our commitment to always provide at least 4 Mbit/s per client in at least one server in the world, we add servers before this limit is reached. In the particular case of the Netherlands, we have decided to go beyond our warrant, because customers clearly appear to be very interested in this country.
 
With the current configuration and considering the average numbers of clients connected to Netherlands servers with an excess prudential margin of 20%, we are now able to provide more than 4 Mbit/s per client in the Netherlands alone, even keeping into account potential aforementioned overhead. In the "Top 10 Users Speed", right now, we can see that the topmost 4 clients are all in the Netherlands, ranging from 65 Mbit/s to 40 Mbit/s each.
 
Kind regards

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hi, 
this is a an important question.
 
We have recorded a dramatic increase of clients requiring connections to NL servers in the past weeks and months. With the increase of single connected clients (consider that since April a user can connect simultaneously three clients and also consider that Air user base has grown up considerably during this year), we must take into account different variables to a server load in addition to available bandwidth.
 
CPUs of our servers not only must handle TLS auth and OpenVPN AES-256 encryption/decryption, but also SSH and OpenSSL additional tunnels. There is, so far, no scientific study which determines how the CPU load increases (under the same provided bandwidth) with the increase of connected clients in an OpenVPN server, but empirically it might be not linear (example: 50 clients requiring 1 Mbit/s each stress CPU more than one client requiring 50 Mbit/s does). So, we could have a server that has a line and a port of 1 Gbit/s, but whose CPU gets at capacity before that limit (for example already at 650 Mbit/s). Therefore, in order to respect our commitment to always provide at least 4 Mbit/s per client in at least one server in the world, we add servers before this limit is reached. In the particular case of the Netherlands, we have decided to go beyond our warrant, because customers clearly appear to be very interested in this country.
 
With the current configuration and considering the average numbers of clients connected to Netherlands servers with an excess prudential margin of 20%, we are now able to provide more than 4 Mbit/s per client in the Netherlands alone, even keeping into account potential aforementioned overhead. In the "Top 10 Users Speed", right now, we can see that the topmost 4 clients are all in the Netherlands, ranging from 65 Mbit/s to 40 Mbit/s each.
 
Kind regards

Hi, 
this is a an important question.
 
We have recorded a dramatic increase of clients requiring connections to NL servers in the past weeks and months. With the increase of single connected clients (consider that since April a user can connect simultaneously three clients and also consider that Air user base has grown up considerably during this year), we must take into account different variables to a server load in addition to available bandwidth.
 
CPUs of our servers not only must handle TLS auth and OpenVPN AES-256 encryption/decryption, but also SSH and OpenSSL additional tunnels. There is, so far, no scientific study which determines how the CPU load increases (under the same provided bandwidth) with the increase of connected clients in an OpenVPN server, but empirically it might be not linear (example: 50 clients requiring 1 Mbit/s each stress CPU more than one client requiring 50 Mbit/s does). So, we could have a server that has a line and a port of 1 Gbit/s, but whose CPU gets at capacity before that limit (for example already at 650 Mbit/s). Therefore, in order to respect our commitment to always provide at least 4 Mbit/s per client in at least one server in the world, we add servers before this limit is reached. In the particular case of the Netherlands, we have decided to go beyond our warrant, because customers clearly appear to be very interested in this country.
 
With the current configuration and considering the average numbers of clients connected to Netherlands servers with an excess prudential margin of 20%, we are now able to provide more than 4 Mbit/s per client in the Netherlands alone, even keeping into account potential aforementioned overhead. In the "Top 10 Users Speed", right now, we can see that the topmost 4 clients are all in the Netherlands, ranging from 65 Mbit/s to 40 Mbit/s each.
 
Kind regards

Hello!
 
Very interesting. It comes out that "the personal iOS hotspot feature, as for the USB/bluetooth tethering and MyWi, binds the traffic on a the 3G interface. OpenVPN changes the routing and uses the PPP interface, so the packets coming from the shared clients are bound to the 3G but the system route is going to the PPP interface, so it doesn't work." (by the author of GuizmoVPN app: http://www.guizmovpn.com/index.php?option=com_agora&task=topic&id=119&p=1&Itemid=15#p438 ).
 
Kind regards

Ok guys here's the crazy explanation for this entire issue.
 
I had an issue where high cpu usage caused the vpn to seem to die, but it was more like just connections get dropped.
 
It was caused by lag ?
The apinger or gateway monitor was unable to reach the monitor ip of the wan upstream (it could reach the airvpn gw interface tho)
Ok here's the entire cause and effect
 
Lag causes apinger to raise a delay alarm which triggers a filter reload and if the gateway monitor ip can't be reached it will therefore also trigger a firewall state drop.
 
Lol and that's how you get a weird issue my friends.

Hi, 
this is a an important question.
 
We have recorded a dramatic increase of clients requiring connections to NL servers in the past weeks and months. With the increase of single connected clients (consider that since April a user can connect simultaneously three clients and also consider that Air user base has grown up considerably during this year), we must take into account different variables to a server load in addition to available bandwidth.
 
CPUs of our servers not only must handle TLS auth and OpenVPN AES-256 encryption/decryption, but also SSH and OpenSSL additional tunnels. There is, so far, no scientific study which determines how the CPU load increases (under the same provided bandwidth) with the increase of connected clients in an OpenVPN server, but empirically it might be not linear (example: 50 clients requiring 1 Mbit/s each stress CPU more than one client requiring 50 Mbit/s does). So, we could have a server that has a line and a port of 1 Gbit/s, but whose CPU gets at capacity before that limit (for example already at 650 Mbit/s). Therefore, in order to respect our commitment to always provide at least 4 Mbit/s per client in at least one server in the world, we add servers before this limit is reached. In the particular case of the Netherlands, we have decided to go beyond our warrant, because customers clearly appear to be very interested in this country.
 
With the current configuration and considering the average numbers of clients connected to Netherlands servers with an excess prudential margin of 20%, we are now able to provide more than 4 Mbit/s per client in the Netherlands alone, even keeping into account potential aforementioned overhead. In the "Top 10 Users Speed", right now, we can see that the topmost 4 clients are all in the Netherlands, ranging from 65 Mbit/s to 40 Mbit/s each.
 
Kind regards

Website: http://www.deezer.com/
Deezer is a web-based music streaming service. It allows users to listen to music on various devices online or offline.
 
Status: OK
Native: All server except US and NL
Routing: US and NL, to FR route.

Website: http://www.bbc.co.uk/
Breaking news, sport, TV, radio and a whole lot more. The BBC informs, educates and entertains - wherever you are, whatever your age.

Status: Not accessible
Native: none
Routing: all servers

http://www.cielotv.it/
 
Website: http://www.cielotv.it/
Cielo (Sky in English) is an Italian television channel broadcast by 21st Century Fox aimed to a young audiences,[1] and available on digital terrestrial and satellite television through Sky Italia.
 
Status: OK
Routing: All server to IT route.

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hi, 
this is a an important question.
 
We have recorded a dramatic increase of clients requiring connections to NL servers in the past weeks and months. With the increase of single connected clients (consider that since April a user can connect simultaneously three clients and also consider that Air user base has grown up considerably during this year), we must take into account different variables to a server load in addition to available bandwidth.
 
CPUs of our servers not only must handle TLS auth and OpenVPN AES-256 encryption/decryption, but also SSH and OpenSSL additional tunnels. There is, so far, no scientific study which determines how the CPU load increases (under the same provided bandwidth) with the increase of connected clients in an OpenVPN server, but empirically it might be not linear (example: 50 clients requiring 1 Mbit/s each stress CPU more than one client requiring 50 Mbit/s does). So, we could have a server that has a line and a port of 1 Gbit/s, but whose CPU gets at capacity before that limit (for example already at 650 Mbit/s). Therefore, in order to respect our commitment to always provide at least 4 Mbit/s per client in at least one server in the world, we add servers before this limit is reached. In the particular case of the Netherlands, we have decided to go beyond our warrant, because customers clearly appear to be very interested in this country.
 
With the current configuration and considering the average numbers of clients connected to Netherlands servers with an excess prudential margin of 20%, we are now able to provide more than 4 Mbit/s per client in the Netherlands alone, even keeping into account potential aforementioned overhead. In the "Top 10 Users Speed", right now, we can see that the topmost 4 clients are all in the Netherlands, ranging from 65 Mbit/s to 40 Mbit/s each.
 
Kind regards

Hello!
 
First of all, let's clarify the units for every reader.
 
MB: Megabyte
Mbit: Megabit
s: second
1 Byte = 8 bit
1 MB/s = 8 Mbit/s
 
Assuming a good quality line and low latency from your node to the VPN server (if you have high latency, for example with a satellite connection, then you will be unable in any case to get stellar performance with OpenVPN), a couple of possible reasons for poor performance are:
 
1) Traffic shaping. In the past years many ISPs (the majority in the world) have performed wild overselling, promising peak bandwidth performance that they could deliver constantly only if a tiny fraction (1% of even less) of their customers were connected simultaneously. They now prefer to shape traffic on almost everything instead of investing in infrastructure expansion. Comcast performs traffic shaping. In the European Union, an ISP is obliged by law to tell you if it performs traffic shaping or applies any other technique limiting your usage of any service or protocol, but not in the USA. https://airvpn.org/topic/10967-slow-airvpn-speeds-050mbs-down-or-less/?do=findComment&comment=15358
 
2) Wrong MTU size, so that you get packet fragmentation that hits performance.
 
Possible solutions to problem 1 are changing connection ports (try in particular port 53 UDP) and switching to a protocol which might be less capped than another, for example by trying OpenVPN over SSL if you see that your "https traffic" is not as slow as pure OpenVPN traffic. A more effective solution might be changing ISP with one that can deliver what it advertises.
 
Solution to problem 2 is changing the packet size with mssfix. Do not change TUN MTU size with directives "tun-mtu" and/or "fragment"! Without a corresponding change on the server side, doing that would have unpredictable effects and might also prevent a connection. Change it by using "mssfix" only. Start with "mssfix 1350" and test, then increase or decrease the size with little steps, re-testing each time. Please note (important) that mssfix directive makes sense only in UDP mode. On the www you can find also good methods which help you determine the correct value in order to speed up the trial-and-error process. See for example here for some more information and details http://www.dslreports.com/faq/695 Once again: do not touch the MTU of your physical or virtual network cards (unless you exactly know what you're doing), just operate through the OpenVPN directive mssfix.
 
Kind regards

Hello!

First of all, with our client please try a connection on port 80 TCP or port 53 TCP, just in case your ISP caps bandwidth on some or all UDP ports. Just select the "Modes" tab and pick the appropriate port, then click "Enter".

Then, please make sure that your client listening port matches the port you have remotely forwarded on our system.

In order to forward a port on our system, log in our website and select menu "Member Area"->"Forwarded ports". Let the system pick a random port for you (TCP & UDP) and write down that port. Finally, configure your torrent client to listen to the very same port.

You don't need and you must not forward the same port on your router (security issues).

On the FAQ, you will find more detailed instructions:
https://airvpn.org/faq

Kind regards

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hello!

We're very glad to inform you that five new 1 Gbit/s servers located in the Netherlands are available: Ceres, Julliet, Pallas, Riguel and Sedna.

The AirVPN client will show automatically the new servers, while if you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 2018 UDP and TCP.

Just like every other Air server, Ceres, Julliet, Pallas, Riguel and Sedna support OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.
 
Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

Hello!
 
The TLS Cipher is wrong. Try with "None". If it fails, try with "TLS-DHE-RSA-WITH-AES-128-CBC-SHA". Both are very wrong but for some DD-WRT glitch, on newer builds either the first or the second work, while all the other ones (wrong as well) fail.
 
Kind regards

@dd79 thank you very much!

Hello!
We're glad to inform you that the critical, remotely exploitable "shellshock" bug http://seclists.org/oss-sec/2014/q3/650 does not affect our systems, which (if they used bash) have been all patched with appropriate updates.
 
Kind regards
AirVPN Staff
 

Hello!
We're glad to inform you that the critical, remotely exploitable "shellshock" bug http://seclists.org/oss-sec/2014/q3/650 does not affect our systems, which (if they used bash) have been all patched with appropriate updates.
 
Kind regards
AirVPN Staff
 

Hello!
 
We're very glad to inform you that our XMPP (Jabber) server is now available for free to all members of AirVPN web site. The server has an A-A security rating.
 
We have opened a dedicated forum: https://airvpn.org/forum/37-xmpp
 
Enjoy XMPP!
 
Kind regards & datalove
AirVPN Staff

Overview

We host a XMPP (Jabber) server, with A-A security rating. We recommend to use only OTR compatible client.

It's available for free to every member of this website.

This forum is open to already available or new guides, tutorials or discussions (even about XEP).


Recommended client

OS X: Adium
Windows, Linux: Pidgin
Android: Xabber