Feature request: API for port forwarding

[mage1982 15]

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.

[OpenSourcerer 1435]

I must say: This is a very interesting feature request.

It would make port forwarding on the fly possible, thus making VoIP work with AirVPN. Well, except SIP, but I'm sure there is a way, too. Of course I'm aware of the fact that VoIP software need to be rewritten a bit to make them forward ports before establishing a connection.. a script might be sufficient, too. Things to think about after the feature is implemented, if at all.

 

Awaiting more thoughts on this.

[Staff 9972]

Hello!

 

It's a good idea, it will be implemented. We can't say exactly when, it will require some work.

 

Kind regards

[OpenSourcerer 1435]

Hello!

 

It's a good idea, it will be implemented. We can't say exactly when, it will require some work.

 

Kind regards

 

Nice! I will do some research on how a port-forward-on-the-fly feature can be realised with a Fritz!Box. And then the Fritz!Box guide will finally be rewritten and tested with my new router.

[Stalinium 44]

Bump, I too would like to see an API for port-forwarding management. In my case all I want to do: only do port-forwarding when my primary client is to be connected and remove PF on disconnect/shutdown so it is not unnecessarily kept track of.
Any further software configuration due to changing port numbers is of course my own headache (firewall rules probably or further software APIs).

Not the usual UPnP/NAT-PMP. Although maybe you'll eventually need it (to solve the port exhaustion problem). The problem with those: users have too little control over them in programs.

For the sake of completeness, other threads when this was asked:
2016: https://airvpn.org/forums/topic/18317-forward-ports-api-support/?tab=comments#comment-43652
2017: https://airvpn.org/forums/topic/21706-api-for-port-forwarding/?tab=comments#comment-57135
2021: https://airvpn.org/forums/topic/49390-connectivity-check-on-httpsairvpnorgports-removed/?do=findComment&comment=166562