Archived from groups: alt.internet.wireless (
More info?)
On Wed, 08 Sep 2004 22:50:08 +0200, hans <jkkrutgers@wanadoo.nl>
wrote:
>Jeff Liebermann wrote:
>> There's another exception. If you're using the Ad-Hoc mode, all the
>> radios are client radios. It would be a bad idea to have them scan
>> all channels looking for each other. So, in Ad-Hoc, the channel
>> number of the client radio is fixed and does not scan. Running a
>> "site survey" on an ad-hoc system only lists radios that are on its
>> channel.
>Not my experience.
I beg to differ.
>I have a pc with wireless and a laptop with wireless
>and changed channels several times to avoid same channel usage.
You can change channels in ad-hoc mode all you want. However, ad-hoc
mode does NOT scan for empty channels or compatible SSID's. You set
it for a specific channel and leave it there.
Note that the channel is specified in the ad-hoc setup in the
following instructions:
http://www.zyxel.com/support/supportnote/ZyAIR_G2000/app/Adhoc.htm
http://www.hardavenue.com/reviews/adhocguide.shtml
>I was often in ad hoc mode and it keeps scanning
>(in netstumbler anyway)
Netstumbler is doing the scanning. It scans all the channels looking
for access points. In ad-hoc mode, there are no access points.
Netstumbler is very good about not trampling infrastructure or ad-hoc
connections and can be run simultaneously with either an ad-hoc or
infrastructure clients.
>But could there be another reason?
>May be the AP is not on all the time?
>If the other signal is not an AP but a pc-peer then the
>signal is only on when they have switched on the computer.
I'm sorry. I don't understand any of the above. Repeating again:
1. An access point is set to a specific channel.
2. Client radios scan all channels looking for access points.
3. All ad-hoc radios are client radios and are set to a fixed
channel. They do NOT scan channels but do scan for an IBSS network to
join.
4. Netstumbler is a client application and does not know anything
about ad-hoc or infrastructure modes. It scans channels looking for
infrastructure access points.
5. Netstumbler will detect ad-hoc clients, but seems to belch
multiple BSSID's with some (not all) ad-hoc clients.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice
http://www.LearnByDestroying.com
# jeffl@comix.santa-cruz.ca.us
# 831.421.6491 digital_pager jeffl@cruzio.com AE6KS