summaryrefslogtreecommitdiffstats
path: root/usr.sbin/wicontrol
Commit message (Collapse)AuthorAgeFilesLines
...
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Actually implement -a as documented since import (set access point density).brooks2001-06-262-9/+8
| | | | | | | Remove documentation for short-lived usage as "print keys in ASCII." PR: bin/21803 MFC after: 1 week
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for usr.sbin/ to 8.ru2001-03-201-3/+0
|
* mdoc(7) police: Change -filled displays (which just happenru2001-02-071-6/+2
| | | | | | to be the same as -ragged in the current implementation) to -ragged. With mdocNG, -filled displays produce the correct output, formatted and justified to both margins.
* Move MD <machine/if_wavelan_ieee.h> to MI <dev/wi/if_wavelan_ieee.h>peter2001-01-091-1/+1
|
* If the first argument doesn't start with '-' assume that it is animp2000-12-311-2/+7
| | | | | | | | | | interface. This augments the default to an appropriate interface code. # These programs should be merged into ifconfig, ala NetBSD, but that's # a fight for another day. Idea from: OpenBSD
* mdoc(7) police: removed history info from the .Os FreeBSD call.ru2000-12-141-1/+1
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-20/+20
|
* When an interface isn't specified use wi0 as the default.joe2000-10-281-3/+12
| | | | | | | This gets around a segmentation fault that occurs when the interface isn't specified first before any of the options. Inspired by PR: bin/22241
* When an interface isn't specified use wi0 as the default.joe2000-10-281-1/+2
| | | | | | | This gets around a segmentation fault that occurs when the interface isn't specified first before any of the options. Inspired by PR: bin/22241
* Fix PR #21245: handle wep keys correctly and pretty print hex keyswpaul2000-09-212-36/+42
| | | | | as appropriate. Nick: this sort of does what your changes did, except the hex/text printing is done automatically using isprint().
* Forgot semicolon after rcsidnsayer2000-09-171-1/+1
| | | | Submitted by: gshapiro
* 1. In key printing routine, the loop variable was j, but inside thensayer2000-09-162-19/+38
| | | | | | | | loop was referencing i. 2. Print keys in hex rather than ascii by default. 3. Add a -a flag to reverse #2 on demand.
* Update the description of available channel for Japan.sanpei2000-07-261-14/+15
| | | | | | | | | The regulations has been changed to adopt 802.11b since Oct. 99. For 11Mbps NICs sold in Japan, all DS channels (1..14) are available. Thank you, itojun. Obtained from: NetBSD:basesrc/usr.sbin/wiconfig/wiconfig.8 Rev.1.5 ->1.6
* Bring the ancontrol buffer oflows fixes here too.roberto2000-06-181-2/+2
| | | | Submitted by: Aaron Campbell <aaron@openbsd.org>
* Remove more single-space hard sentence breaks.sheldonh2000-03-021-7/+14
|
* Remove single-space hard sentence breaks. These degrade the qualitysheldonh2000-03-011-36/+72
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
* Add support for WEP (encryption) for silver and gold WaveLAN/IEEE turbo cards.wpaul2000-02-022-8/+227
| | | | | | | | | | | | Also update wicontrol to enable/disable encryption, set WEP keys and set the TX key index. Silver cards only have 40-bit keys. This is something of a quick hack, but it works well enough for me to commit this from the LinuxWorld exhibit floor. The WEP support only shows up if you have a card that supports it. Would have been approved by: jkh, if he hadn't wandered off somewhere Approved in his place by: msmith, who's standing right here
* Update the WaveLAN/IEEE driver:wpaul1999-11-253-2/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Convert to new bus attachment scheme. Thanks to Blaz Zupan for doing the initial work here. One thing I changed was to have the attach and detach routines work like the PCI drivers, which means that in theory you should be able to load and unload the driver like the PCI NIC drivers, however the pccard support for this hasn't settled down yet so it doesn't quite work. Once the pccard work is done, I'll have to revisit this. - Add device wi0 to PCCARD. If we're lucky, people should be able to install via their WaveLAN cards now. - Add support for signal strength caching. The wicontrol utility has also been updated to allow zeroing and displaying the signal strength cache. - Add a /sys/modules/wi directory and fix a Makefile to builf if_wi.ko. Currently this module is only built for the i386 platform, though once the pccard stuff is done it should be able to work on the alpha too. (Theoretically you should be able to plug one of the WaveLAN/IEEE ISA cards into an alpha with an ISA slot, but we'll see how that turns out. - Update LINT to use only device wi0. There is no true ISA version of the WaveLAN/IEEE so we'll never use an ISA attachment. - Update files.i386 so that if_wi is dependent on card.
* $Id$ -> $FreeBSD$peter1999-08-283-4/+4
|
* Various man page cleanup:mpp1999-08-151-2/+2
| | | | | | | | | | - Sort xrefs. - FreeBSD.ORG -> FreeBSD.org - Be consistent with section names as outlined in mdoc(7). - Other misc mdoc cleanup. PR: doc/13144 Submitted by: Alexey M. Zelkin <phantom@cris.net>
* Fix a number of typos.mpp1999-07-301-6/+6
|
* Fix typo: sofware -> software.sheldonh1999-07-281-2/+2
| | | | | PR: 12837 Submitted by: Norihiro Kumagai <kuma@jp.freebsd.org>
* - Fix up some comments in if_wi.c (no code changes)wpaul1999-05-222-9/+27
| | | | | | | - Mention that the 6Mbps turbo adapters are supported in HARDWARE.TXT and RELNOTES.TXT and the wi.4 man page - Mention turbo adapters in the wicontrol.8 man page and provide a complete table of available transmit speed settings
* Fix usage in wicontrol.c to agree with man page.wpaul1999-05-142-14/+39
| | | | | Update documentation for -f frequency selection option to include complete list of channel numbers and frequencies.
* Fix a couple of small buglets.wpaul1999-05-071-2/+2
|
* Add support to wicontrol(8) and wi(4) for enabling and configuringwpaul1999-05-072-3/+37
| | | | | | | power management. This will only work on newer firmware revisions; older firmware will silently ignore the attempts to turn power management on. Patches supplied by: Brad Karp <karp@eecs.harvard.edu>
* Modify wicontrol(8) and wi(4) to allow setting the frequency of thewpaul1999-05-062-11/+19
| | | | | | | WaveLAN's radio modem. The default is whatever the NIC uses since NICs sold in different countries may default to different frequencies. (The Lose95/LoseNT software doesn't let you select the channel so it's probably not really meant to be changed.)
* Fix some byte ordering problems; I was storing string lengths wrong,wpaul1999-05-061-4/+4
| | | | | | | which was causing wicontrol to crash when reading string parameters from the WaveLAN. Patches submitted by: Brad Karp <karp@eecs.harvard.edu>
* Add device driver support for the Lucent WaveLAN/IEEE 802.11 PCMCIAwpaul1999-05-053-0/+695
adapter (and some workalikes). Also add man pages and a wicontrol utility to manipulate some of the card parameters. This driver was written using information gleaned from the Lucent HCF Light library, though it does not use any of the HCF Light code itself, mainly because it's contaminated by the GPL (but also because it's pretty gross). The HCF Light lacks certain featurs from the full (but proprietary) HCF library, including 802.11 frame encapsulation support, however it has just enough register information about the Hermes chip to allow someone with enough spare time and energy to implement a proper driver. (I would have prefered getting my hands on the Hermes manual, but that's proprietary too. For those who are wondering, the Linux driver uses the proprietary HCF library, but it's provided in object code form only.) Note that I do not have access to a WavePOINT access point, so I have only been able to test ad-hoc mode. The wicontrol utility can turn on BSS mode, but I don't know for certain that the NIC will associate with an access point correctly. Testers are encouraged to send their results to me so that I can find out if I screwed up or not.
OpenPOWER on IntegriCloud