netdev - Re: [RFC PATCH] bcm43xx: set channel when the interface is brought up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Jan 2007 13:57:40 +0100
From:	"Ivo Van Doorn" <ivdoorn@...il.com>
To:	"Jiri Benc" <jbenc@...e.cz>
Cc:	"Pavel Roskin" <proski@....org>, bcm43xx-dev@...ts.berlios.de,
	netdev@...r.kernel.org
Subject: Re: [RFC PATCH] bcm43xx: set channel when the interface is brought up

Hi,

> > Correct, similar problems have been detected in rt2x00. The temporary
> > solution in there is to demand a scanning operation after the interface
> > has been brought up.
>
> Scanning? No no no, please! That would be a clear bug and misbehaviour.

Hmm, I think I forgot to add one little thing in my comment.
The scanning operation is demanded in the rt2x00 README, so the driver
doesn't start the scanning automatically and just awaits the user commands.
The user is also free to change the channel to make the configuration active.
But a scanning command will also display if it has at least found some AP,
so without scanning results attempting to scan will very likely fail. ;)

Ivo
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html