All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Don't enable PROMISC when adding AP to a bridge?
Date: Mon, 13 Jul 2015 16:06:20 -0700	[thread overview]
Message-ID: <55A4446C.4090803@candelatech.com> (raw)

I notice some of my WLE900VX cards will lock up and not receive any packets
after a few seconds of being in PROMISC mode.  This happens on my own
CT firmware as well as stock firmware-2.bin.  This breaks monitor mode, of
course, but it also breaks bridged AP mode.

So, I found this patch from way back when:
http://lists.celinuxforum.org/pipermail/bridge/2008-June/005906.html

I hacked a similar thing into my 4.0.4 kernel, and now bridged mode
AP seems much more stable (and the radio does not go into PROMISC mode,
so it should be more efficient in a busy RF environment).

Maybe this feature could be revisited?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Don't enable PROMISC when adding AP to a bridge?
Date: Mon, 13 Jul 2015 16:06:20 -0700	[thread overview]
Message-ID: <55A4446C.4090803@candelatech.com> (raw)

I notice some of my WLE900VX cards will lock up and not receive any packets
after a few seconds of being in PROMISC mode.  This happens on my own
CT firmware as well as stock firmware-2.bin.  This breaks monitor mode, of
course, but it also breaks bridged AP mode.

So, I found this patch from way back when:
http://lists.celinuxforum.org/pipermail/bridge/2008-June/005906.html

I hacked a similar thing into my 4.0.4 kernel, and now bridged mode
AP seems much more stable (and the radio does not go into PROMISC mode,
so it should be more efficient in a busy RF environment).

Maybe this feature could be revisited?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2015-07-13 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 23:06 Ben Greear [this message]
2015-07-13 23:06 ` Don't enable PROMISC when adding AP to a bridge? Ben Greear
2015-07-14  5:13 ` Michal Kazior
2015-07-14  5:13   ` Michal Kazior

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=55A4446C.4090803@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@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.