Don't flush other IPs when setting up vboxnet interfaces

[poige]

Currently I'm using vboxnet-interfaces configured with other tools, for e. g., it could be Quagga that supports adding configured IPs postponed till interface's creation.
Those IPs are in fact statically assigned and they belong to different IP-networks.

But then during Virtualbox configuration of vboxnet interfaces it completely flushes all IPs but the one it uses itself.

There's no clear workaround for that, hence I'm suggesting to change this behaviour.

[socratis]

I'm using vboxnet-interfaces

What do you mean by that, can you explain it? Not a term I'm familiar with.

it could be Quagga that supports adding configured IPs postponed till interface's creation.

Again, what is "Quagga"? And why would VirtualBox know what a Quagga is?

it completely flushes all IPs but the one it uses itself.

What's the "completely flushes" part?

I believe that you need to explain your problem in VirtualBox-speak, to make it more understandable...

[Martin]

It looks like the OP want's to use the host OS possibilities to assign more than one IP address to a network interface on a vbox created (vboxnet) network interface.
Vbox seems to completely reinitialize its virtual interfaces which removes changes / additions done outside of Vbox.

[socratis]

If we're talking about this Quagga (https://www.quagga.net/) I can't understand how there's interference, I guess I'm old school and I need to see a step-by-step guide on how to re-create the scenario, and most importantly where does VirtualBox come into play.

Vbox seems to completely reinitialize its virtual interfaces which removes changes / additions done outside of Vbox.

What does that mean? You want to change a NIC's properties (which ones?) from within the guest and then VirtualBox breaks those changes? (how?)

Again, an example would go a long way...