linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
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 11:12:26 +0200	[thread overview]
Message-ID: <20110114091226.GA32344@jm.kir.nu> (raw)
In-Reply-To: <4D2FF7A4.3070106@candelatech.com>

On Thu, Jan 13, 2011 at 11:13:40PM -0800, Ben Greear wrote:
> 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.

Yes. So what?

> 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'?

I would say it is up to whoever decided to set the interface down to
restart hostapd.. There is a proposed patch for hostapd to do this
automatically, but I'm yet to fully understand why one would set the
interface down in the first place.

-- 
Jouni Malinen                                            PGP id EFC895FA

  parent reply	other threads:[~2011-01-14  9:12 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
2011-01-14  9:12 ` Jouni Malinen [this message]
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=20110114091226.GA32344@jm.kir.nu \
    --to=j@w1.fi \
    --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).