All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	linux-wireless@vger.kernel.org
Subject: Re: rt28xx AP-mode problem with commit 3edaf3e61fda3aa9ff8d38445bf92f2bec23bf63 "mac80211: manage AP netdev carrier state"
Date: Thu, 10 May 2012 10:15:26 +0200	[thread overview]
Message-ID: <1336637726.4334.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120509210448.GE5472@yumi.tdiedrich.de>

On Wed, 2012-05-09 at 23:04 +0200, Tobias Diedrich wrote:

> > PKG_REV:=1f0cc27eb98f7d1af9c64d0752238184cbdb9a24

Ok.

> When associating to the AP works (3edaf3e61fda3aa9ff8d38445bf92f2bec23bf63 reverted):
> root@OpenWrt:/# ip monitor
> dev eth0.1 lladdr 00:50:5b:04:05:7e REACHABLE
> dev wlan0 lladdr a0:0b:ba:c6:9f:88 REACHABLE

Ah, well, I wanted "ip monitor" (and maybe restrict to "ip monitor
link") while you start/stop hostapd. Sorry for not being clear on that.
Also could be useful to look at it with the tcpdump thing, which is very
very strange.

I wonder if things like broadcast addresses are only added upon
netif_carrier_on() and that would reprogram filters and cause issues for
rt2x00... For that we'd need to do some more debugging inside mac80211
though.

johannes


  parent reply	other threads:[~2012-05-10  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 10:57 rt28xx AP-mode problem with commit 3edaf3e61fda3aa9ff8d38445bf92f2bec23bf63 "mac80211: manage AP netdev carrier state" Tobias Diedrich
2012-05-09 11:59 ` Johannes Berg
2012-05-09 12:18   ` Tobias Diedrich
2012-05-09 21:04     ` Tobias Diedrich
2012-05-09 21:28       ` Tobias Diedrich
2012-05-10  8:13         ` Johannes Berg
2012-05-10  8:15       ` Johannes Berg [this message]
2012-05-10  8:27         ` Johannes Berg
2012-05-18  0:57           ` Tobias Diedrich
2012-05-18  1:18           ` Tobias Diedrich
2012-05-18 17:16             ` Johannes Berg
2012-05-19  7:54               ` Tobias Diedrich
2012-05-11 23:39         ` Tobias Diedrich

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=1336637726.4334.13.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=ranma+openwrt@tdiedrich.de \
    /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.