From: Mark Smith <lk-netdev@lk-netdev•nosense.org>
To: Rick Jones <rick.jones2@hp•com>
Cc: Stephen Hemminger <shemminger@vyatta•com>,
Jay Vosburgh <fubar@us•ibm.com>,
Ben Greear <greearb@candelatech•com>,
bonding-devel@lists•sf.net, netdev@vger•kernel.org
Subject: Re: Bonding ALB sends bogus packets
Date: Fri, 31 Jul 2009 11:00:58 +0930 [thread overview]
Message-ID: <20090731110058.0e4216ee.lk-netdev@lk-netdev.nosense.org> (raw)
In-Reply-To: <4A72314C.9080007@hp.com>
Hi Rick,
On Thu, 30 Jul 2009 16:48:28 -0700
Rick Jones <rick.jones2@hp•com> wrote:
> Mark Smith wrote:
> >
> > ETH_P_LOOP should probably have been avoided, as "LOOP" or "loopback"
> > is commonly used to refer to the Ethernet Configuration Testing
> > Protocol (google search for "Ethernet Loop protocol").
>
> I wonder how that relates to linkloop:
>
> http://sourceforge.net/projects/linkloop/
>
> http://fr2.rpmfind.net/linux/RPM/opensuse/factory/x86_64/usr_share_doc_packages_linkloop_Tree.html
>
> >
> > I'd suggest not using any form of ARP for this purpose. It'd place an
> > IPv4 requirement on the bonded interface, and various "empty" ARP
> > frames have meaning e.g. duplicate address detection. 802.2 test frames
> > or the original Ethernet V2.0 Configuration Testing Protocol have been
> > used for this bridge table address refresh purpose in the past.
>
> I can never remember if linkloop uses XID or Test frames :(
>
>From memory when I looked into it a year or so ago, linkloop
used 802.2 test frames.
When I decided to have a go at implementing ECTP for the Linux kernel
a couple of years ago, one thing I didn't want to was to duplicate
already existing layer 2 testing functionality in the kernel, which
meant comparing 802.2 test frames capability verses ECTP. 802.2 test
frames only do single hop unicast request/reply testing, obviously
requiring you to already know the test unicast address. ECTP, in
addition, provides broadcast and optionally multicast ECTP capable node
discovery, and the ability test a path of nodes, by providing a list of
unicast addresses to visit i.e. a strict source route. As I've found
IPv4 'broadcast pings' occasionally useful, I thought a layer 2
equivalent, not requiring IPv4 to be functioning, would also be quite
useful.
ECTP could also probably be used over any 802.2 capable network, by
using the SNAP encoding with an OUI of 0x000000 and then a protocol ID
of 0x9000.
(When you start looking into it, it's interesting how many layer 2
keepalive/testing protocols have been developed over the years,
including most recently the Ethernet OAM protocols. What is also
suprising is that the original Ethernet V2.0 Configuration Testing
Protocol tends to be more capable than any of them - they're usually
just single-hop request/reply testing)
Regards,
Mark.
prev parent reply other threads:[~2009-07-31 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 20:06 Bonding ALB sends bogus packets Stephen Hemminger
2009-07-30 20:28 ` Jay Vosburgh
2009-07-30 20:35 ` Stephen Hemminger
2009-07-30 23:36 ` Mark Smith
2009-07-30 23:48 ` Rick Jones
2009-07-31 1:30 ` Mark Smith [this message]
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=20090731110058.0e4216ee.lk-netdev@lk-netdev.nosense.org \
--to=lk-netdev@lk-netdev$(echo .)nosense.org \
--cc=bonding-devel@lists$(echo .)sf.net \
--cc=fubar@us$(echo .)ibm.com \
--cc=greearb@candelatech$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rick.jones2@hp$(echo .)com \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox