Thanks,
I'll try to improve it next week to support network ranges and add support for
lxc + gui
- Mail original -
De: "dietmar"
À: "aderumier" , "pve-devel"
Envoyé: Vendredi 15 Janvier 2016 17:28:39
Objet: Re: [pve-devel] [PATCH] add
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
ang Bumiller"
À: "aderumier"
Cc: "pve-devel"
Envoyé: Vendredi 15 Janvier 2016 12:09:27
Objet: Re: [pve-devel] [PATCH] add support for network trunks
> On January 15, 2016 at 12:02 PM Alexandre DERUMIER
> wrote:
>
>
> >>Given the bridge comman
> On January 15, 2016 at 12:02 PM Alexandre DERUMIER
> wrote:
>
>
> >>Given the bridge command syntax we used here:
> >>system("/sbin/bridge vlan add dev $iface vid 2-4094") == 0 ||
> >>
> >>And the new command you introduced here:
> >>+ system("/sbin/bridge vlan add dev $iface vid $trunk")
> + &$safe_num_ne($oldnet->{trunks}, $newnet->{trunks}) ||
>>Should this be $safe_string_ne()? (Since it's a ';' separated list and
>>possibly contains 'x-y' ranges.
I'll look at it, maybe I can improve this.
- Mail original
On Fri, Jan 15, 2016 at 03:15:35AM +0100, Alexandre Derumier wrote:
> @@ -454,7 +454,7 @@ my $nic_model_list_txt = join(' ', sort @$nic_model_list);
> my $netdesc = {
> optional => 1,
> type => 'string', format => 'pve-qm-net',
> -typetext => "MODEL=XX:XX:XX:XX:XX:XX
> [,bridge=][,q
This add support for net trunks vlan filtering
for ovs and linux vlan-aware bridge
Can be mixed with current "tag" option
examples:
--
allow only 802.1Q packets with vlanid 2,3,4 :
netx: .,trunks=2,3,4
allow only 802.1Q packets with vlanid 2,3,4 and tag non-802.1Q packets to
vlani
