From: Felix Fietkau <nbd@openwrt.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Johannes Berg <johannes@sipsolutions.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"
Date: Wed, 01 May 2013 23:06:16 +0200 [thread overview]
Message-ID: <518183C8.8050606@openwrt.org> (raw)
In-Reply-To: <CAOaVG179Rx_JfV99mbjWhwQTALb5gh+2_WVFWDSbngA0qkzoGw@mail.gmail.com>
On 2013-05-01 10:21 PM, Stephen Hemminger wrote:
> What about using AF_PACKET bound to underlying wireless device and the
> packet type. You can even use BPF to filter.
As far as I know, AF_PACKET only works when not binding it to the packet
type (otherwise it get stolen by the rx handler).
Not binding it to the packet type and using BPF to filter is expensive
on small embedded devices with small caches. Still, this requires
userspace changes, so we need a different solution.
> Another alternative would be to have bridge accept control frames on
> dormant device but not send.
Sounds good, will you send a patch for that?
- Felix
next prev parent reply other threads:[~2013-05-01 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:02 Regression in 3.9 caused by "bridge: respect RFC2863 operational state" Felix Fietkau
2013-05-01 19:49 ` Krishna Chaitanya
[not found] ` <CAOaVG179Rx_JfV99mbjWhwQTALb5gh+2_WVFWDSbngA0qkzoGw@mail.gmail.com>
2013-05-01 21:06 ` Felix Fietkau [this message]
2013-05-01 22:49 ` Stephen Hemminger
2013-05-02 0:53 ` Felix Fietkau
[not found] <CAFuUQkhHsRZMnNYBbVZU0=BcAKMEktzYgPv6oc=CMFd7MFDi6g@mail.gmail.com>
2015-12-04 2:31 ` YanBo
2016-01-19 15:45 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-01-19 21:10 ` YanBo
2016-01-19 21:48 ` Stephen Hemminger
2016-01-19 21:55 ` Felix Fietkau
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=518183C8.8050606@openwrt.org \
--to=nbd@openwrt.org \
--cc=chaitanya.mgit@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=stephen@networkplumber.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).