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:	Mon, 22 Jan 2007 14:30:45 -0500
From:	Michael Wu <flamingice@...rmilk.net>
To:	Jan Evert van Grootheest <j.e.van.grootheest@...way.nl>
Cc:	netdev@...r.kernel.org
Subject: Re: adm8211 (from linville wireless-2.6) in xen guest

On Saturday 20 January 2007 07:19, Jan Evert van Grootheest wrote:
> Hi,
>
> Just writing to thank all of you that made the adm8211 driver in John
> Linvilles wireless-2.6 development tree (not the dscape one, which I
> will try also).
>
CC me then. :) Note that I only maintain the d80211 based adm8211 driver now, 
but that driver doesn't have adhoc support yet.

> One question, though. I'm trying to use it in ad-hoc mode. If there's no
> other station with the same essid, it just keeps mentioning that
> (besides the BCNTC and TSFTF messages)
>
> wlan0: No matching adhoc sta found. Creating IBSS 00:04:e2:3f:2a:70 CHAN=11
>
> And the IBSS changes every time, which is about every 30 seconds. Is it
> really supposed to change the IBSS each time?
Probably not, but I never debugged adhoc mode enough.

> The reason I ask is that my wife has a laptop with an Atheros chip in
> it. If it is configured for ad-hoc it creates the IBSS and sticks with
> it. So I now have two computers that have different behaviour in this
> respect. That in itself is not, I guess, a problem. But it seems to me
> that the random IBSS created by the adm8211 would result in two stations
> not seeing eachother or taking longer than necessary to find eachother?
>
Have you checked? I think the bssid should stop changing once another station 
with the same ssid comes into range.

> And one more question that I don't understand... the wlan0 interface
> does not appear in snmp queries. Any idea about that?
>
Nope.

-Michael Wu

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ