Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:52607 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757077Ab2EJI1g (ORCPT ); Thu, 10 May 2012 04:27:36 -0400 Message-ID: <1336638453.4334.15.camel@jlt3.sipsolutions.net> (sfid-20120510_102742_254576_EC118C30) Subject: Re: rt28xx AP-mode problem with commit 3edaf3e61fda3aa9ff8d38445bf92f2bec23bf63 "mac80211: manage AP netdev carrier state" From: Johannes Berg To: Tobias Diedrich Cc: "John W. Linville" , OpenWrt Development List , linux-wireless@vger.kernel.org Date: Thu, 10 May 2012 10:27:33 +0200 In-Reply-To: <1336637726.4334.13.camel@jlt3.sipsolutions.net> (sfid-20120510_101538_229332_FE8BA9F3) References: <20120509105719.GA24457@yumi.tdiedrich.de> <1336564773.4323.19.camel@jlt3.sipsolutions.net> <20120509121827.GD5472@yumi.tdiedrich.de> <20120509210448.GE5472@yumi.tdiedrich.de> <1336637726.4334.13.camel@jlt3.sipsolutions.net> (sfid-20120510_101538_229332_FE8BA9F3) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 2012-05-10 at 10:15 +0200, Johannes Berg wrote: > 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. I don't see anything like that happening upon netif_carrier_on(), the only thing that really seems to happen is attaching and starting qdiscs, which shouldn't make a difference across drivers... Is this using compat-wireless? But then, so do I right now, against 3.1 base kernel. johannes