Search the Community
Showing results for tags 'feature request'.
Found 3 results
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!
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.
Hello AirVPN, Just a quick usability suggestion. It would be great to be able to add a short description or label to each forwarded port. It's hard to keep track of which port is used for what or why you even have it open in the first place. Thank you for taking this into consideration