On Thu, Feb 17, 2011 at 12:45:35PM +0100, Camiel Dobbelaar wrote:
> On 16-2-2011 14:27, Reyk Floeter wrote:
> > My previous change to vlan(4) allows to change the vlandev and vlan id
> > on-the-fly without re-creating the vlan interface.
>
> I hesitated to ask this simple question, because I might
On 2011 Feb 17 (Thu) at 12:45:35 +0100 (+0100), Camiel Dobbelaar wrote:
:On 16-2-2011 14:27, Reyk Floeter wrote:
:> My previous change to vlan(4) allows to change the vlandev and vlan id
:> on-the-fly without re-creating the vlan interface.
:
:I hesitated to ask this simple question, because I migh
On 16-2-2011 14:27, Reyk Floeter wrote:
> My previous change to vlan(4) allows to change the vlandev and vlan id
> on-the-fly without re-creating the vlan interface.
I hesitated to ask this simple question, because I might be overlooking
something, but what exactly is the advantage over just using
This fixes the breakage I saw with a carp child. This also works with a
bridge child. The routing socket sees the interface status changes, so
things that care get notified.
OK.
On 2011 Feb 16 (Wed) at 14:27:18 +0100 (+0100), Reyk Floeter wrote:
:Hi!
:
:My previous change to vlan(4) allows to
Hi!
My previous change to vlan(4) allows to change the vlandev and vlan id
on-the-fly without re-creating the vlan interface.
Unfortunately, I figured out that carp(4) on vlan stops working if you
change the vlandev (vlan parent). The problem is that the vlan
interface forgets about its multicas
