From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: No beacons generated when you bring ath9k AP interface down and up.
Date: Fri, 14 Jan 2011 09:26:31 +0100 [thread overview]
Message-ID: <1294993591.3853.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D2FF7A4.3070106@candelatech.com>
On Thu, 2011-01-13 at 23:13 -0800, Ben Greear wrote:
> Been a long day, but I think I finally see the problem.
>
> If you have an ath9k AP interface running with hostapd, and you
> run: ip link set vap0 down; ip link set vap0 up;
> then it will disable beaconing.
>
> One reason is that the ieee80211_do_open calls the
> ieee80211_bss_info_change_notify before it sets the RUNNING
> flag, so it would disable beaconing. A second is that
> it doesn't set the BEACON_CHANGED flag anyway, so even if you
> hack things to set RUNNING first, it still doesn't work right.
>
> I'm not sure where the problem actually lies: Should ath9k
> start beaconing automatically on VAP interface add? Is
> it up to hostapd to detect the ifdown/ifup and re-set everything
> up properly? Or maybe it's just a very bad idea to bounce
> a VAP interface with 'ip link set'?
Why would that be a good idea? I mean ... why would you want to do
that?!
johannes
next prev parent reply other threads:[~2011-01-14 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 7:13 No beacons generated when you bring ath9k AP interface down and up Ben Greear
2011-01-14 8:26 ` Johannes Berg [this message]
2011-01-14 9:12 ` Jouni Malinen
2011-01-14 13:22 ` Ben Greear
2011-01-14 14:17 ` Brian Prodoehl
2011-01-14 13:49 ` Jorge Boncompte [DTI2]
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=1294993591.3853.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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 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).