[PVE-User] VLAN and 4.2 upgrade

Laurent CARON lcaron at unix-scripts.info
Mon May 9 09:13:02 CEST 2016


My bad.

I forgot to:

dpkg --purge vzctl

After running it, it works wonderfully.

/etc/network/if-up.d/vzifup-post was the culpirt.

Sorry for the noise.

On 06/05/2016 17:05, Dietmar Maurer wrote:
> The corresponding if-up/if-down scripts are here:
>
> /etc/network/if-post-down.d/vlan
> /etc/network/if-pre-up.d/vlan
>
>
>> On May 6, 2016 at 1:35 PM Laurent CARON <lcaron at unix-scripts.info> wrote:
>>
>>
>> On 06/05/2016 12:50, Dietmar Maurer wrote:
>>>> Is there really no way we can re-introduce the native debian VLAN config ?
>>>
>>> AFAIK VLAN still works as before (we just not use the deprecated vconfig
>>> package).
>>>
>>
>> Unfortunately not
>>
>> The following stanzas in :/etc/network/interfaces:
>>
>> auto vlan136
>> iface vlan136 inet manual
>>          vlan-raw-device eth1
>>
>>
>> auto vmbr136
>> iface vmbr136 inet manual
>>          bridge_ports vlan136
>>          bridge_stp off
>>          bridge_fd 0
>>
>> # ifup vlan136 results in:
>> Failed to bring up vlan136
>>
>> Is there a way you could not have a conflict between pve-manager and vlan ?
>>
>> Thanks
>>
>
>
> !DSPAM:572cb2e334831305710144!
>




More information about the pve-user mailing list