Proxmox

spayk · 03-17-2019, 03:17 PM

Hello all!
I have installed a debian Jessie on my physicall laptop (A) and also installed proxmox (newest) here. I have made few virtual machines.
I would like to connect them to the network.
Those machines have "output" in the world, but the problem is that my other pysicall laptop (b) is not able to find them locally. Here is my screenshot from the proxmox - network configuration of physciall machine (A). Where should I look to make them visible via LAN? IPtables?

/dev/random · 03-29-2019, 04:06 PM

Quote:

Originally Posted by spayk

Hello all!
I have installed a debian Jessie on my physicall laptop (A) and also installed proxmox (newest) here. I have made few virtual machines.
I would like to connect them to the network.
Those machines have "output" in the world, but the problem is that my other pysicall laptop (b) is not able to find them locally. Here is my screenshot from the proxmox - network configuration of physciall machine (A). Where should I look to make them visible via LAN? IPtables?

What is the output of this:

Code:

iptables -L

vincix · 03-29-2019, 05:20 PM

What is the network configuration of the virtual machines? Give one example to understand how they're connected with each other.
In the meantime, you could also show us the output of brctl show (or ip link show) and the contents of /etc/network/interfaces. There's too litte information you've provided.

berndbausch · 03-30-2019, 04:32 AM

Quote:

Originally Posted by spayk

my other pysicall laptop (b) is not able to find them locally

Do you mean ping etc doesn't reach the VMs? They might indeed be blocked by rules in iptables, but you also need to ensure ip_forward is set. Which it should be after installing Proxmox and libvirt (which comes as part of Proxmox, I would guess), but it's always good to check:

Code:

sysctl net.ipv4.ip_forward

vincix · 03-30-2019, 09:13 AM

If you haven't changed anything, I don't see how iptables might be the problem, to be honest. It should accept everything by default. The first place I'd look for are network bridges - information you can gather from the aforementioned commands. If they're correctly connected, then I'd also have a peek at iptables, why not?

/dev/random · 03-30-2019, 01:09 PM

Quote:

Originally Posted by vincix

If you haven't changed anything, I don't see how iptables might be the problem, to be honest. It should accept everything by default. The first place I'd look for are network bridges - information you can gather from the aforementioned commands. If they're correctly connected, then I'd also have a peek at iptables, why not?

Its not the virtual machines, its the host I am worried about... in the past ubuntu (firewalld) came with rules that were not exactly friendly to some applications.

vincix · 03-30-2019, 06:48 PM

As far as I know Centos/Red Hat did that and it blocked basically everything except for the services you'd install with your system - usually openssh. Firewalld was developed by Redhat, not Canonical, although of course you could run it on any distro. Ubuntu comes with ufw and the default behaviour, as far I as know, is to leave everything open. It is disabled by default.