[pve-devel] Network configuration

Martin Waschbüsch service at waschbuesch.it
Tue Jul 28 06:12:09 CEST 2015

> Am 27.07.2015 um 20:27 schrieb Michael Rasmussen <mir at datanom.net>:
> On Mon, 27 Jul 2015 20:08:24 +0200 (CEST)
> Alexandre DERUMIER <aderumier at odiso.com> wrote:
>>>> eval {
>>>> ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
>>>> vlan$port type=internal
>>>> };
>> internal interface can have a random name.
> I know, but to keep it simple and IMHO more intuitive use a descriptive
> name.
>> also, we need to manage update. (ip modification for example).
>> we could do down, up . But it's not optimal.
> How would you do it otherwise? The only way to change IP on an
> interface which is up is to bring it down first, change IP, and then
> bring it up again.

Is it?
I thought you can do

ip addr del dev eth0

to remove one IPv4


ip addr flush dev eth0

to remove all IPs?

This way, at least, the interface is not physically down, as you only modify a single layer 3 protocol's properties.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://pve.proxmox.com/pipermail/pve-devel/attachments/20150728/7645cab2/attachment.sig>

More information about the pve-devel mailing list