netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Leun <lkml20130126@newton.leun.net>
To: Netdev <netdev@vger.kernel.org>
Cc: Rami Rosen <roszenrami@gmail.com>,
	Patrick McHardy <kaber@trash.net>,
	shemminger@linux-foundation.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Missing iproute2 support for 802.1ad
Date: Fri, 21 Jun 2013 21:57:17 +0200	[thread overview]
Message-ID: <20130621215717.528b3cbf@xenia.leun.net> (raw)
In-Reply-To: <20130621173744.1c1ce920@xenia.leun.net>

On Fri, 21 Jun 2013 17:37:44 +0200
Michael Leun <lkml20130126@newton.leun.net> wrote:

> On Fri, 21 Jun 2013 16:52:41 +0300
> Rami Rosen <roszenrami@gmail.com> wrote:
> 
> > This patch by Patrick McHardy, titled:
> > "add 802.1ad support", seems to do the job:
> > http://www.spinics.net/lists/netdev/msg233587.html

> OK, when applying that patch to iproute2 git the if_link.h hunk
> expectedly fails, but the rest applies.

Meanwhile Stephen has grabbed that patch and committed it to iproute2
git - thank you very much.

> But, unfortunately the result is not what I would expect:
[...]
> Both have ether type 0x8100, the first one should have 0x88a8, or did
> I get something wrong?

This either was an problem with veth or with namespace or with both of
them.

With real ethernet I get the same result Patrick has shown in his
802.1aq commit message.

-- 
MfG,

Michael Leun

      reply	other threads:[~2013-06-21 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:17 Missing iproute2 support for 802.1ad Michael Leun
     [not found] ` <CAKoUArm0w70TZvaZSMa1C9vAj+UXsMkza7XTBX0Vq-7B3xrFLA@mail.gmail.com>
2013-06-21 13:52   ` Rami Rosen
2013-06-21 15:37     ` Michael Leun
2013-06-21 19:57       ` Michael Leun [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=20130621215717.528b3cbf@xenia.leun.net \
    --to=lkml20130126@newton.leun.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=roszenrami@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).