[pve-devel] pve-common : linux bridge and ovs new modelimplementation v2

[Alexandre DERUMIER]

>>Is possible add this feature to firewall as default (if firewall is 
>>enabled)? ... The PVE cluster comunication only is allowed for his PVE 
>>Nodes? 
>>
>>I think that with this feature the multicast protocol not will generate 
>>excessive and unnecessary traffic in the LAN 

Hi, you should use igmp snooping on your physical switches for this.

It's not possible with a firewall to say only send multicast traffic to a specific host.
(or it's not multicast anymore ;)


----- Mail original ----- 

De: "Cesar Peschiera" <brain at click.com.py> 
À: pve-devel at pve.proxmox.com 
Envoyé: Jeudi 1 Mai 2014 17:46:05 
Objet: Re: [pve-devel] pve-common : linux bridge and ovs new modelimplementation v2 

Is possible add this feature to firewall as default (if firewall is 
enabled)? ... The PVE cluster comunication only is allowed for his PVE 
Nodes? 

I think that with this feature the multicast protocol not will generate 
excessive and unnecessary traffic in the LAN 

----- Original Message ----- 
From: "Alexandre Derumier" <aderumier at odiso.com> 
To: <pve-devel at pve.proxmox.com> 
Sent: Tuesday, April 29, 2014 10:49 AM 
Subject: [pve-devel] pve-common : linux bridge and ovs new 
modelimplementation v2 


> changelog: 
> 
> - handle new firewall tap option 
> - improve tap_unplug 
> - improve bridges cleanup 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel