From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: more findings/questions on vlans/bonds
Date: Thu, 16 Apr 2009 17:17:42 +0300 [thread overview]
Message-ID: <49E73E06.5030708@Voltaire.com> (raw)
In-Reply-To: <5325.1239113639@death.nxdomain.ibm.com>
>> I played a bit with bonding vlans (2.6.29 active-backup mode) and it
>> doesn't seem to work - specifically, I noted that bonding doesn't issue
>> fail-over after I changed the current slave link status to down ("ifconfig
>> eth0.4001 down"). I suspect that the carrier based link monitoring scheme
>> is broken wrt to vlan devices
[...]
>> I also played with a post 2.6.29 cut of Linus tree, and I couldn't bond vlans.
Hi Jay,
Did you had the chance to look into the bonding-vlan-devices related issues
I came across when doing these tests?
Or.
next prev parent reply other threads:[~2009-04-16 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 9:14 more findings/questions on vlans/bonds Or Gerlitz
2009-04-07 9:16 ` Or Gerlitz
2009-04-07 14:13 ` Jay Vosburgh
2009-04-16 14:17 ` Or Gerlitz [this message]
2009-04-23 21:04 ` Jay Vosburgh
2009-04-24 15:22 ` Patrick McHardy
2009-04-26 8:21 ` Or Gerlitz
2009-04-26 14:14 ` Or Gerlitz
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=49E73E06.5030708@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.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.