netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Evert van Grootheest <j.e.van.grootheest@caiway.nl>
To: Michael Wu <flamingice@sourmilk.net>
Cc: netdev@vger.kernel.org
Subject: Re: adm8211 (from linville wireless-2.6) in xen guest
Date: Mon, 22 Jan 2007 22:56:11 +0100	[thread overview]
Message-ID: <45B532FB.6080200@caiway.nl> (raw)
In-Reply-To: <200701221430.50547.flamingice@sourmilk.net>

Michael,

Michael Wu wrote:
> On Saturday 20 January 2007 07:19, Jan Evert van Grootheest wrote:
>   
>> 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.
>   
If there're some tests I can help with, just ask.
I've decided yesterday that I really should get myself a WRT54G or 
somesuch. So there's not much pressure for this adm8211 anymore.
>> 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.
>   
Well, it took more than 1 minute and I left for coffee. When I returned 
they had found eachother.

Do you perhaps know whether there's a sourcetree somewhere of the dscape 
code that can be compiled as external modules for 2.6.18?
At least I can help test the dscape code, which I understand is the 
current future of wireless in linux.

Thanks,
Jan Evert


  reply	other threads:[~2007-01-22 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 12:19 adm8211 (from linville wireless-2.6) in xen guest Jan Evert van Grootheest
2007-01-22 19:30 ` Michael Wu
2007-01-22 21:56   ` Jan Evert van Grootheest [this message]
2007-01-23 15:20   ` Dan Williams

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=45B532FB.6080200@caiway.nl \
    --to=j.e.van.grootheest@caiway.nl \
    --cc=flamingice@sourmilk.net \
    --cc=netdev@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).