[pve-devel] pve-firewall: container problem

[Dietmar Maurer]

I finally created an ifupdown helper script, so we can do the following now:

auto vmbr0
iface vmbr0 inet manual
	bridge_ports bond0
	bridge_stp off
	bridge_fd 0

# this create the veth device and plug it into vmbr0
auto pm0
iface pm0 inet static
	address  192.168.10.10
	netmask  255.255.255.0
	gateway  192.168.10.1
	VETH_BRIDGETO vmbr0

see https://git.proxmox.com/?p=pve-firewall.git;a=commitdiff;h=c27d58f3b2c4b38fdf2ba1bf93ac6d43b20bd920

> >>Yes, it is somehow similar to an OVS IntPort?
> 
> yes, exactly !
> 
> 
> ----- Mail original -----
> 
> De: "Dietmar Maurer" <dietmar at proxmox.com>
> À: "Alexandre DERUMIER" <aderumier at odiso.com>
> Cc: pve-devel at pve.proxmox.com
> Envoyé: Mercredi 5 Mars 2014 06:12:07
> Objet: RE: pve-firewall: container problem
> 
> > Good Idea, but I think that it should be tested (mainly with
> > multicast, igmp quierier, ...)
> >
> > mainly also test that we could provide dhcp from this ip on veth (if
> > we implement a dhcp later this year)
> 
> sure, tesing is always a good idea ;-)
> 
> > It could be great too, if on day we use new vlan bridge filtering
> > feature, so it could be possible to assign 1vlan by veth-bridgeport
> 
> Yes, it is somehow similar to an OVS IntPort?