Port forwarding on AirVPN with Virtual Machine

[Mercury 0]

Hi,

 

so I've recently set-up a virtual machine to run uTorrent on (my way of restricting VPN use to uTorrent since I'm too stupid to do it another way).

Forwarding ports through the virtual machine is not that hard actually. I've done it with my regular uTorrent port and it works (without the VPN on).

 

However, when I forward the port I use for uTorrent in the virtual machine with the AirVPN Client Area - it doesn't work.

I forward a port and then I check whether or not it's open with CanYouSeeMe.org (as I usually do) and it shows me that it's not open while I'm

connected to the VPN and it shows me that it's open while I'm not (because I forwarded that port in my router).

 

Any idea why this is happening? My VM uses NAT to create a network connection. Maybe that has something to do with it?

Oh and I'm using the OpenVPN GUI not the AirVPN Client.

 

Would appreciate some help!

 

Greetz,

- Mercury

[Staff 10015]

Hello!

 

Since your VM is attached via NAT to your host you need to forward that very same port from your host to your VM. Virtualization software like VirtualBox nowadays handle very well port forwarding to VMs attached via NAT.

 

Kind regards

[Mercury 0]

Hello!

 

Since your VM is attached via NAT to your host you need to forward that very same port from your host to your VM. Virtualization software like VirtualBox nowadays handle very well port forwarding to VMs attached via NAT.

 

Kind regards

 

I did that. Sorry that I didn't make myself clear enough.

 

So if I use the CanYouSeeMe.org site without the VPN up (on my VM) the port is open (because I forwarded it in my router-interface and forwarded it again through the VM settings).

And as soon as I connect to the VPN (on my VM) the port is closed (even though I have forwarded it in the AirVPN webinterface). That is what I'm struggling with.

 

Thanks for helping!

 

Greetz,

- Mercury

[Staff 10015]

Hello!

 

Is the service running and listening to the correct port when you perform the test? Also make sure that some firewall does not block packets to and from the service: in some cases a firewall might block them when the system is inside the VPN. Check the firewall both on the host and the VM.

 

When testing is over, you should not forward that very same port on the router to prevent potential correlation attacks.

 

Kind regards

[Mercury 0]

Hello!

 

Is the service running and listening to the correct port when you perform the test? Also make sure that some firewall does not block packets to and from the service: in some cases a firewall might block them when the system is inside the VPN. Check the firewall both on the host and the VM.

 

When testing is over, you should not forward that very same port on the router to prevent potential correlation attacks.

 

Kind regards

 

Hi, so I'm not forwarding any ports anymore, I just use UPnP in uTorrent and it works. No idea but apparently UPnP does enough to make it work.

Thanks though, if issues ever arise I'll seek help again!

 

Greetz,

- Mercury