Date: Wed, 20 Sep 2000 16:06:35 -0700 From: Denver Maddux <denver@nitrous.net> To: Bob Ney <bney@quiknet.com> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Problems getting WaveLAN device (wi0) working Message-ID: <20000920160635.E10774@nitrous.net> In-Reply-To: <3.0.6.32.20000920133438.0110c740@pop.quiknet.com> References: <4.3.1.1.20000920122431.00c45b90@localhost> <4.3.1.1.20000920122431.00c45b90@localhost> <20000920131158.D61974@gblx.net> <3.0.6.32.20000920133438.0110c740@pop.quiknet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The drivers recently installed on a Windows laptop in my household (not mine... never...) default to BSS mode, not Ad-Hoc. I plugged my AP in and didn't do anything to it's config and was forced to use BSS mode on my FreeBSD laptops also. I honestly don't know the advantage of either, and I almost don't care... I just care that it works. :) -Denver Bob Ney wrote: > These settings will remove the card from Ad-Hoc mode however, The problems > being experienced are consistant with those I have seen. My BSD machines > talk to each other ok in mode 3, but will not talk to a windows laptop also > running in mode 3. (Ad-Hoc),nor will they talk to the access point. The > Windows machine is running newer drivers and I am wondering if there have > been some protocol changes to the ad-hoc function in the windows and access > point software. Everything works fine in mode 1, but that requires the > access point as the communications hub. > > At 01:11 PM 9/20/00 -0700, you wrote: > >For mine I have to add the following options to get it to work with the > >AP in default settings: > > > >/usr/sbin/wicontrol -i wi0 -n "" > >/usr/sbin/wicontrol -i wi0 -s atom > >/usr/sbin/wicontrol -i wi0 -p 1 > > > >-s is not really required, atom is my stationID for my laptop so change > >that to whatever you like. > > > >I have also seen those messages but it doesn't seem to stop it from > >working ... providing the above settings are configured. > > > >-Steve > > > >* Ross Finlayson <finlayson@live.com> [000920 12:41]: > >> Has anyone else encountered this problem (with a WaveLAN/Orinico card in a > >> ISA->PCMCIA adaptor): > >> > >> On boot, the "pcic" and "pccard" devices come up fine, and "pccardd" is > >> started. The WaveLAN card is detected, and the "wi0" interface is > >> configured (using my "pccard_ifconfig" setting). "netstat -r" shows > >> correct routing table entries. I'm keeping the interface in "ad hoc" mode > >> (port type 3: the default). > >> > >> In other words, everything looks fine, EXCEPT that I'm not seeing any > >> traffic on the interface (e.g., when my other machine - a Windoze laptop > >> with a WaveLAN card also in "ad hoc" mode - tries to do DHCP). > >> > >> One hint is that when I run > >> wicontrol -i wi0 > >> (to see the interface's settings), I get > >> wicontrol: SIOCGWAVELAN: Invalid argument' > >> So, it appears that something hasn't been configured properly. Any ideas? > >> > >> Ross. > >> > >> ps. I had previously gotten a WaveLAN card to work with FreeBSD, but only > >> using a WaveLAN<->Ethernet adaptor box, which - to FreeBSD - looks just > >> like a regular (non-wi) Ethernet interface. This is my first time trying > >> to get "wi" to work. > >> > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-mobile" in the body of the message > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-mobile" in the body of the message > > > Bob Ney > Quiknet Inc. > Director Operations > (916) 782-9700 > bney@quiknet.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000920160635.E10774>