On Mon, Apr 17, 2006 at 09:27:09PM +0200, Johannes Berg wrote:
> On Mon, 2006-04-17 at 12:06 -0700, Jean Tourrilhes wrote:
>
> > Definitely. I was just pointing out that scanning behaviour is
> > not dictated by current setting of the drivers (except when the
> > hardware does it, cf. Ornoco).
>
> Yeah, I was just repeating it for Ulrich :)
>
> > For freq, it's simpler. In managed mode, it's never 'fixed',
> > because the card/driver choose the frequency. In master mode, it's
> > almost always 'fixed', because the user has to set the frequency. In
> > ad-hoc mode, it depend in the node creates or not the IBSS.
>
> But isn't that a detail the user shouldn't have to know? See, if a node
> with a higher TSF joins the IBSS, then it gets to send out the beacons
> for it, IIRC.
Who sent the beacon is different from who created the IBSS. If
you don't like this proposal, here is another one : if in ad-hoc mode
the actual IBSS freq is the same as what the user set, then set the
'fixed' flag, otherwise report the actual freq without the 'fixed'
flag.
Or if you have another meaningful use of the flag in ad-hoc
mode, just shout.
> johannes
Jean
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
