From: Johannes Berg <johannes@sipsolutions.net>
To: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: rt28xx AP-mode problem with commit 3edaf3e61fda3aa9ff8d38445bf92f2bec23bf63 "mac80211: manage AP netdev carrier state"
Date: Fri, 18 May 2012 19:16:27 +0200 [thread overview]
Message-ID: <1337361387.4802.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120518011829.GD22418@yumi.tdiedrich.de>
[dropping openwrt list, it keeps bothering me that I should subscribe]
On Fri, 2012-05-18 at 03:18 +0200, Tobias Diedrich wrote:
> One more clue:
> I think this has to do with the order in which the OpenWRT wifi
> script does things:
>
> hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf
> hostapd_ctrl=/var/run/hostapd-phy0/wlan0
> ifconfig wlan0
> ifconfig wlan0 down
> ifconfig wlan0 hw ether 1c:af:f7:49:50:56 up
> ifconfig wlan0 0.0.0.0
> ifconfig wlan0
> ifconfig br-lan
> ifconfig wlan0 0.0.0.0
> ifconfig wlan0 hw ether 1c:af:f7:49:50:56 up
> iw dev wlan0 set txpower fixed 2000
Wow, ok, setting the interface down while the AP is up really isn't a
valid use of it. I'm actually amazed that it ever works at all when you
do this. Either this should be done the other way around, or hostapd
needs to get some smarts about it. For example, with the start-AP
function transition, I'm not sure even *beacon* after you do this...
johannes
next prev parent reply other threads:[~2012-05-18 17:16 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
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 [this message]
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=1337361387.4802.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).