[Question] Containers / VMs network questions

[Kimbaras]

Hi,

This is more of a question more than a bug or real issue, sorry if this is not the right place for such things.

My environment is WSL2 on Win11.

I've got some queries about the networking.

I can successfully connect to the PVE dashboard either via localhost:8006 or using the WSL "IP".

When I create either a ct or vm using the DHCP option I correctly get an IP in the internal subnet (which I suspect is set and not random, as when I tried to edit the config it automatically returned to the default values) but I'm unable to access that IP.
Oh and the ct / vm is able to reach outside such as updating or installing new packages.

I'm not really sure if that is an issue with the Win11 host or it's intended and there is something missing from either side.

So, assuming I have a ct up and running with IP 172.30.64.xxx with a webserver installed and listening on port 80.
How can I connect to that webserver from the host (Win11) machine?

Simply pointing the browser to that IP returns a timeout error, but as mentioned, it could also be an issue with the host machine. Unfortunately it's the only Win11 I've got available right now.

Let me know if my situation is clear or you need more details to better understand it!

Thanks!

[kroese]

Very good question! But unfortunately my networking skills are a bit lacking, so I also don't know the answer.

I think the easiest way would be to install something like Tailscale inside the VM (and on the host). Then both machines are in the same Tailscale network, and you can reach the VM very easily by its Tailscale IP address (instead of the 172.30.64.xxx address).

Another way that doesnt require Tailscale would be to shell into the container and add a iptable rule to forward traffic for port X to port 80 on 172.30.64.xxx. Then you can connect to port X on the host to reach port 80 of the VM. Because the container is able to reach that IP, only your host is not. So by redirecting traffic in this way it could be fixed.

But I think the Tailscale way would be a lot easier, because it would not require you to map any specific ports for each VM, and also adds a lot of other handy features (like easy file transfers, hostnames, etc.)

[Kimbaras]

Thanks for the feedback!

Unfortunately at the moment I'm unable to install Tailscale on the host machine.

I will think and make some trials with other ways.

Feel free to close the issue (or keep it open few days until I can provide some additional feedback from my side)

EDIT:

Wait, maybe I misunderstood you comment, with "install Tailscale inside and on the host", what exactly are meaning for the host?
The WSL container or the Win machine?

[kroese]

@Kimbaras The Windows machine. And let's leave this open because maybe other people have better solutions. It is just that I have a lot of experience with Tailscale already, so for me that was the easiest solution.

[d4vid1]

Hi everyone,

I think here is solution, but how to get it to work on proxmox docker?

I use longqt-sea proxmox Container.

Thanks in Advance