ANSWERED Port Forwarding question - public vs local port

[k0n0r 0]

Hi Guys,

my program requires port 9999 to be open.

I have set the port in the client area as a local port of 9999, and it gave me port 30250 at the top in big bold writing.

When i check if port 9999 is open on a 3rd party website it says the port is closed. If i check port 30250, it says it is open.

I'm a little confused, does this mean i should change the port in the application im using from 9999 to 30250? 

Why did i have to tell AirVPN in the client area that i needed 9999 forwarded if its still closed, and it gave me port 30250? 

 

Edited ... by k0n0r

[OpenSourcerer 1363]

The remote port is the port opened on all AirVPN servers. People from the outside must use this port to connect.
The local port is the port on which your listening application awaits connections.

While you can forward port A to B, it might be easier to forward the same port A to A, in this case, 30250 to 30250. 30250 to 9999 works just as well, of course, but you need to remember the fact that your app must run on 9999 and others need to use 30250 to connect.
 

1 hour ago, k0n0r said:

Why did i have to tell AirVPN in the client area that i needed 9999 forwarded if its still closed, and it gave me port 30250? 

You left the remote port empty and entered the local port explicitly, so the system forwarded a random port to your explicitly written local port. If you left local port empty, too, the system would've assigned you a random port, to the same random local port.

I hope all this clears up the confusion a little.

[k0n0r 0]

1 hour ago, OpenSourcerer said:

The remote port is the port opened on all AirVPN servers. People from the outside must use this port to connect.
The local port is the port on which your listening application awaits connections.

While you can forward port A to B, it might be easier to forward the same port A to A, in this case, 30250 to 30250. 30250 to 9999 works just as well, of course, but you need to remember the fact that your app must run on 9999 and others need to use 30250 to connect.
 

You left the remote port empty and entered the local port explicitly, so the system forwarded a random port to your explicitly written local port. If you left local port empty, too, the system would've assigned you a random port, to the same random local port.

I hope all this clears up the confusion a little.

thank you! so if im understanding you right, i am OK that my port is set to 9999 on my PC application, that when traffic for port 9999 comes through airVPN it will put it through 30250. 

So everything is working as it should?
 

[OpenSourcerer 1363]

9 hours ago, k0n0r said:

that when traffic for port 9999 comes through airVPN it will put it through 30250. 

Traffic on remote port 30250 is forwarded to your local port 9999, otherwise correct.