From: Nick Carter <ncarter100@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org, benjamin.poirier@gmail.com,
davem@davemloft.net, shemminger@linux-foundation.org
Subject: Re: [PATCH] bridge: Forward EAPOL when STP off
Date: Thu, 23 Jun 2011 22:30:03 +0100 [thread overview]
Message-ID: <BANLkTi=kUSr9yeOkyjn5oYcn6gtiFTKf_w@mail.gmail.com> (raw)
In-Reply-To: <20110604224209.5c784729@s6510.ftrdhcpuser.net>
Stephen,
It doesn't look like ebtables can do this
http://www.spinics.net/lists/netfilter/msg51200.html
I've written some new diffs that I will send out to netdev.
Thanks,
Nick
On 4 June 2011 14:42, Stephen Hemminger <shemminger@vyatta.com> wrote:
> On Thu, 2 Jun 2011 16:59:13 +0100
> Nick Carter <ncarter100@gmail.com> wrote:
>
>> Signed-off-by: Nick Carter <ncarter100@gmail.com>
>>
>> If STP is disabled then forward frames destined to the 802.1X PAE group
>> address (01-80-C2-00-00-03)
>>
>> This change is required to support virtual machines running an 802.1X
>> supplicant and bridged to an ethernet interface.
>>
>> This change has been tested and works fine with a range of supplicants.
>
> No. This is getting messy and starts down the path of the recent
> 802.3ad change which just got reverted. A better solution is needed
> than individual hacky standards breaking. If you really need to do
> this, use the "duct tape" of networking ebtables.
>
> See also:
> https://lists.linux-foundation.org/pipermail/bridge/2007-November/005638.html
>
prev parent reply other threads:[~2011-06-23 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 15:59 [PATCH] bridge: Forward EAPOL when STP off Nick Carter
2011-06-04 13:42 ` Stephen Hemminger
2011-06-23 21:30 ` Nick Carter [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='BANLkTi=kUSr9yeOkyjn5oYcn6gtiFTKf_w@mail.gmail.com' \
--to=ncarter100@gmail.com \
--cc=benjamin.poirier@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=shemminger@vyatta.com \
/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).