Subject: Re: wiconfig and rc.d/networkg
To: None <firstname.lastname@example.org>
From: Brook Milligan <email@example.com>
Date: 02/26/2001 08:45:32
Why do you think that wiconfig needs to be run before ifconfig for
wireless network adapters?
ifconfig supports a lot of the wiconfig functionality, including:
- WEP enable & key setting
- power saving
- rate (DS1, DS2, DS11)
- adhoc or basestation mode
- network id
Only because I was reading the "Using IEEE 802.11 WaveLAN under
NetBSD" web page (http://www.netbsd.org/Documentation/network/wavelan.html)
as a guide for what to do. This directly states that wiconfig should
be run after ifconfig lo0. Perhaps this page needs reworking to
indicate that all (most?) of the functionality can be had through
ifconfig and that the configuration should be handled just as for any
Another point: I have my WaveLAN working fine now with the ISA
adapter. The same web page indicates that there have been no reports
about that. One is working fine with an old i486 machine. The only
catch was to set the PCIC_ISA_ALLOC_BASE/SIZE kernel options as
mentioned in the pcmcia(4) man page.
I have another one in an ISA adapter installed in a newer PCI system.
This was a bit trickier to get to work, but now works fine. The only
catch was to get the kernel and BIOS configurations in agreement. The
pcic* kernel device had to be changed to:
pcic1 at isa? port 0x3e2 iomem 0xd0000 iosiz 0x4000
and the BIOS had to be set to reserve 0xd0000 for legacy ISA devices.
As a neophyte with PCMCIA, I didn't understand how the pcic* device
and the BIOS interacted and how the WaveLAN would not be detected
unless the "upstream" pcic* device was configured properly. For
awhile, I thought the WaveLAN was misconfigured and didn't realize I
should be looking at the pcic* configuration instead.
Thanks to the list folks for getting me on the right track.