All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Ben Greear <greearb@candelatech.com>, NetDev <netdev@vger.kernel.org>
Subject: Re: Routing tables associated with VLANs dissappear when parent ethX down/up
Date: Wed, 21 Nov 2007 21:25:34 +0100	[thread overview]
Message-ID: <4744943E.2010000@trash.net> (raw)
In-Reply-To: <20071121120027.54c277ea@freepuppy.rosehill>

Stephen Hemminger wrote:
> On Wed, 21 Nov 2007 11:51:43 -0800
> Ben Greear <greearb@candelatech.com> wrote:
>
>   
>> For consideration, this patch seems to work for me.  I'm not sure
>> why we ever listed to these events.  I've only tested on a NIC that
>> doesn't support hw-accel at the moment..will test with e1000 later.
>>
>> Thanks,
>> Ben
>>
>>     
>
> But then if you are doing bonding or bridging of vlan's 
> and you bring down the root network device, the upper layer is not
> notified (for failover).
>   

operstate should be enough for this I guess. Ben, what does iproute show
for the vlan device when the lower device is down?


  reply	other threads:[~2007-11-21 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  1:20 Routing tables associated with VLANs dissappear when parent ethX down/up Ben Greear
2007-11-21 19:51 ` Ben Greear
2007-11-21 20:00   ` Stephen Hemminger
2007-11-21 20:25     ` Patrick McHardy [this message]
2007-11-21 20:54       ` Ben Greear
2007-11-21 21:12         ` Patrick McHardy
2007-11-21 21:52           ` Ben Greear
2007-11-21 22:24             ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4744943E.2010000@trash.net \
    --to=kaber@trash.net \
    --cc=greearb@candelatech.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.