Port forwarding

[VVispy]

Is there currently no way to port forward so that I can open my server up to the public?
#309

[VVispy]

I have many ports port forwarded on my router pointed to my multipass vm with bridged networking. Host is on windows 11. I can access my server on my home internet but if I use a VPN or another wifi it wont resolve to my ip, wont load.
all ports say closed on https://portchecker.co/
@ricab

[Sploder12]

Ah, I meant using the private IP when trying to connect externally. Correct, when port forwarding you specify the private IP (192.168.x.x) to the router so that when data is sent to the public IP it can be routed correctly to that device. But the devices trying to connect from a different network would want to use the public IP.

It would be best to keep all discussion on GitHub so others can benefit from it. Although, this is getting a bit out of scope of what Multipass does.

You could also try doing something like what is discussed in #309 where you forward traffic from the host to the guest.

[VVispy]

@Sploder12

It would be best to keep all discussion on GitHub so others can benefit from it

I would post the solution here once its found.

#309 shouldn't be needed as its bridged. I can do it on VMware

I am using my public ip to connect from other networks...

[VVispy]

@Sploder12
Me and my friend tested on Macos and Windows. Macos qemu driver works to forward the port to the public bridged ip, port checker confirms this. Windows doing the same thing does not work on both the hyperv and virtualbox drivers. Have not tested on linux.
Vmware forwarding works on the same windows device so its an issue with the driver/multipass.

[VVispy]

It would be a lot easier to talk on a chatting platform such as discord, matrix or simplex

[Sploder12]

Hi @VVispy,
One thing to double check on Hyper-V is that the external virtual switch is using the right interface on the host. For example, a laptop will need to use the Wi-Fi interface instead of the Ethernet interface typically.
Another thing to try is setting a static IP on the bridged interface in the instance by modifying the netplan config.

We are actively working on a refined Hyper-V driver implementation so hopefully any rough edges will be resolved with that.