On 12/17/19 10:35 PM, Chris Hofstaedtler | Deduktiva wrote:
* Frank Thommen <f.thom...@dkfz-heidelberg.de> [191217 22:10]:
I probably don't understand the question correctly: One has the IP traffic
to the server/hypervisor, the other has IP traffic for the attached VMs and
containers. Is there no need for a gateway if the bridge only provisions
VMs and containers with network connectivity? Should I think of the bridge
as a dumb connector on the link level (I should probably and urgently reread
my networking materials :-)
You can think of it as a dumb switch. As a special feature, Linux
allows you to also setup host network connectivity on a bridge - but
it doesn't have to do that.
I would guess that on the bridge you want to use for your VMs, you
don't need an IP adress (and also no gateway then).
Generally speaking, having more than one default gateway per host is
an advanced configuration and you really need to know what you're
doing then. Having multiple interfaces with IP addresses is a common
thing, but you'llneed to understand how your routing setup works.
Thanks, that helps. I think I will additionally remove vmbr0 (using
bond0), as this connection will not be used for any virtual machine or
container, but only to access the hypervisor itself.
frank
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
