Subject: bin/25833: What happens with wiconfig?? is 1.6version better than -current ?
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <pancake@phreaker.net>
List: netbsd-bugs
Date: 06/05/2004 23:54:25
>Number:         25833
>Category:       bin
>Synopsis:       wiconfig tool in -current is out of date.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 05 23:25:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 2.0F
>Organization:
	
>Environment:
	
	
System: NetBSD pl2 2.0F NetBSD 2.0F (pancake-laptop) #22: Fri May 28 17:34:49 CEST 2004 root@panser:/usr/src/sys/arch/i386/compile/PANCAKE_LAPTOP i386
Architecture: i386
Machine: i386
>Description:
	I was looking at netbsd documentation and I was glad when I see that
	my wiconfig tool doesn't have any flag that doc. talks about.

	I just download the 1.6 branch src to ensure that in 1.6 info is
	correct.

	[0:/tmp/netbsd/P]# ./a.out 
	usage: a.out interface [-oD] [-t tx rate] [-n network name] [-s station name]
       [-e 0|1] [-k key [-v 1|2|3|4]] [-T 1|2|3|4]
       [-c 0|1] [-q SSID] [-p port type] [-a access point density]
       [-m MAC address] [-d max data length] [-r RTS threshold]
       [-f frequency] [-M 0|1] [-P 0|1] [-S max sleep duration]
       [-A 0|1 ] [-R 1|3]

       wiconfig tool in -current doens't have any flag to put wi in hostap mode
       for example...why 1.6 branch have more things than 2.0 ?

       take a look on the new wiconfig:
       [0:~]# wiconfig 
       usage: wiconfig interface [-oD] [-s station name]
      [-a access point density]
      [-m MAC address] [-d max data length] [-r RTS threshold]
      [-M 0|1] [-R 1|3] [-g fragmentation threshold]


	
>How-To-Repeat:
	wiconfig wi0 -c 1 (for example)
	
>Fix:
	take 1.6 branch code and import to the -current branch?
	
>Release-Note:
>Audit-Trail:
>Unformatted: