Search the Community
Showing results for tags 'feature request'.
Found 5 results
-
Request for the server to forward a /128 to the vpn client so that port forwarding is unneeded for IPv6, though there may be some concerns with it over hosting http content etc...
-
I propose to add an additional option to generate a config file per City (https://airvpn.org/generator/) that will connect to the most optimal server for that city based on server load. This would work similar to how when you connect via Country or Continent. What I mean is when generating config files (https://airvpn.org/generator/) you can only select the specific servers for each city, rather than selecting just the city itself. The problem with connecting via Country or Continent is it will often connect you to a less than optimal server relative to your location. For example, Chicago based connections might be connected to Florida etc. which ultimately leads to connections with bad latency and lower speeds.
-
Hello AirVPN Staff and others. I would very much like to have an API call for creating and removing port forwardings, including requesting a random port. This would allow users to have a different port open for every session started. Setting up a port to be forwarded is already pretty simple, but it does still require having a web browser running and logging in to Air. This may be a small obstacle, but an obstacle nonetheless. I strongly suspect many people will set up a port forwarding only once, and then using the same port for all future sessions, and this has some negative implications for privacy. It is already possible to have this functionality when talking to Air's web server through a browser and clicking buttons manually, so I'm making the assumption it will not be too difficult to do the same through an official HTTP-based API. Does this make sense? I'd love to hear what you think.
-
Hi there, I've been using the AirVPN service now for several weeks and its been great! Due to my ISP (VirginMedia) throttling VPN connections, I've been using the SSL/SSH Tunnels to get through. None the less they still apply a general throttle of 2 MB/s to all encrypted connections. After having done a bit of testing with one of my servers, I realised that the throttling is not done across the whole spectrum of ports, only ports 1 to 1024. For anything higher, in my test case 5432, there was no more throttling being applied. Would it be possible to have the SSH/SSL tunnels connecting over a port greater than 1024, in addition to the current ones (22, 52, 80, and 443)? Thanks!