Re: Call for review... PR 25577
On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote: Well I can't see that since it's not an array and the values come from iterating through Cisco's API and a direct query for the transmit key. Look at ancontrol for the ugly secret details! I'm pretty sure I've also managed to get it to reports things that just plain aren't true like Bruce did. I've bitched to my Cisco rep again to try and get better doc, but so far I haven't had much luck. I just made a specific request for more data on setting and getting WEP keys. In my patches, I just copied the stuff from ancontrol since that's all we've got. The linux code is even more non-sensical then ancontrol in that it reports five keys. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: Call for review... PR 25577
Brooks Davis writes: | On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote: | Well I can't see that since it's not an array and the values come | from iterating through Cisco's API and a direct query for the | transmit key. Look at ancontrol for the ugly secret details! | | I'm pretty sure I've also managed to get it to reports things that just | plain aren't true like Bruce did. I've bitched to my Cisco rep again | to try and get better doc, but so far I haven't had much luck. I just | made a specific request for more data on setting and getting WEP keys. | In my patches, I just copied the stuff from ancontrol since that's all | we've got. The linux code is even more non-sensical then ancontrol in | that it reports five keys. FYI we've found a bug in ancontrol and the scheme for reporting keys if keys are not filled in order. It would be nice to get the source for the Linux configuration utilties that they distribute with the driver on the Cisco web site. I've tried to run it under Linux and I get "no radio found" although I can ping over the Aironet card! Linux and no source makes it hard to figure out what is happening. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
If memory serves me right, Doug Ambrisko wrote: Brooks Davis writes: | On Mon, Apr 02, 2001 at 12:28:38PM -0700, Doug Ambrisko wrote: | Well I can't see that since it's not an array and the values come | from iterating through Cisco's API and a direct query for the | transmit key. Look at ancontrol for the ugly secret details! | | I'm pretty sure I've also managed to get it to reports things that just | plain aren't true like Bruce did. I've bitched to my Cisco rep again | to try and get better doc, but so far I haven't had much luck. I just | made a specific request for more data on setting and getting WEP keys. I'd like to complain to my Cisco rep too, oh wait, I *am* my Cisco rep. Nevermind. I'll try asking around on one of the internal mailing lists to see what I can dig up. But my plate is pretty full if I'm actually going to need to hack code on this. | In my patches, I just copied the stuff from ancontrol since that's all | we've got. The linux code is even more non-sensical then ancontrol in | that it reports five keys. Five keys...could be the new home networking stuff? FYI we've found a bug in ancontrol and the scheme for reporting keys if keys are not filled in order. It would be nice to get the source for the Linux configuration utilties that they distribute with the driver on the Cisco web site. I've tried to run it under Linux and I get "no radio found" although I can ping over the Aironet card! Linux and no source makes it hard to figure out what is happening. Can't use Linux configuration utils...I wonder if there's a minimum firmware rev on the card that you need? Bruce. PGP signature
Re: Call for review... PR 25577
Bruce A. Mah writes: | 1. Seems like I needed to ifconfig the interface up before my other | commands would take effect. I don't recall needing to do any such | thing with the old driver before I could do ancontrol. Is this a | change in behavior or did I miss something? I fixed this and Archie put it in -current and after 4.3 goes out he should MFC it. In the interim try the patch at: http://www.ambrisko.com/doug/an.patch it has some new features such as enabling promiscuous mode from Allan Saddi! | WEP Key status: | Key 0 is set 40 bits | Key 1 is set 128 bits | Key 2 is set 40 bits | Key 3 is unset | The active transmit key is 2 | | If I had to guess, I'd say that if there is an array of WEP keys, the | programs are starting to read one key too late into the array when they | display them. There also seems to be a little disagreement as to | whether keys are numbered starting from 0 or 1. Well I can't see that since it's not an array and the values come from iterating through Cisco's API and a direct query for the transmit key. Look at ancontrol for the ugly secret details! FYI from my laptop: WEP Key status: Key 0 is set 128 bits Key 1 is set 40 bits Key 2 is unset Key 3 is unset The active transmit key is 0 This corresponds to my Win 98 setting even when I twiddled things around and add things to verify it. It was a 1:1 mapping between the configuration utility and ancontrol. I'm also looking at running the Cisco for Linux configuration utilities under FreeBSD's Linux emulation. However, I can't get them to work under Linux (well I'm Linux challenged ... where's "make world"). I've heard they have lots of features but won't release the source for these utilities :-( Atleast the driver source is available so we should be able to emulate the Linux ioctls that they use :-) Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
If memory serves me right, Doug Ambrisko wrote: Bruce A. Mah writes: | 1. Seems like I needed to ifconfig the interface up before my other | commands would take effect. I don't recall needing to do any such | thing with the old driver before I could do ancontrol. Is this a | change in behavior or did I miss something? I fixed this and Archie put it in -current and after 4.3 goes out he should MFC it. In the interim try the patch at: http://www.ambrisko.com/doug/an.patch it has some new features such as enabling promiscuous mode from Allan Saddi! Yeah, David Wolfskill pointed this out too. Wonder why I didn't see it before...maybe something was doing an "ifconfig up" and I just didn't realize it (pccard_ether maybe?). Pass me the pointy hat. | WEP Key status: | Key 0 is set 40 bits | Key 1 is set 128 bits | Key 2 is set 40 bits | Key 3 is unset | The active transmit key is 2 | | If I had to guess, I'd say that if there is an array of WEP keys, the | programs are starting to read one key too late into the array when they | display them. There also seems to be a little disagreement as to | whether keys are numbered starting from 0 or 1. Well I can't see that since it's not an array and the values come from iterating through Cisco's API and a direct query for the transmit key. Look at ancontrol for the ugly secret details! OK. I have a question...an_readkeyinfo() seems to use the loop counter i directly in determining what key number to print out. However, the an_ltv_wepkey structure has an an_key_index member; I'm wondering if that's somehow significant, should be used, or whatever. I was thinking of having an_readkeyinfo() print this out just for kicks. No guarantees, but I'll put it on my TODO list. Note that an important difference between your laptop configuration and mine is that you are using a contiguous range of WEP keys (0 and 1) whereas I am not (0 and 2). FYI: Here's the info from Cisco's key manglement program under Win2K, the same interface as above: Current Adapter is 340 Series PCMCIA Adapter's Firmware Does Support WEP (Version V3.98) Adapter is Associated WEP is Enabled WEP Key 1 is Set (40 Bits) WEP Key 2 is Not Set WEP Key 3 is Set (128 Bits) WEP Key 4 is Not Set WEP Tx Key is Key 3 Doesn't bear much resemblance to what I showed before (the transmit key was right, but little else). Thanks, Bruce. PGP signature
Re: Call for review... PR 25577
Hi Brooks, Can I suggest you add a DS22 for DS 22Mb/s which is going through final approvals at the IEEE. I'll wait for these patches to settle down and merge the functionality into the raylink driver. Are you planning on making a unified interface for things like the signal strenght cache? Duncan -- Duncan Barclay | God smiles upon the little children, [EMAIL PROTECTED] | the alcoholics, and the permanently stoned. [EMAIL PROTECTED]| Steven King To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
On Sat, Mar 31, 2001 at 10:16:44AM +0100, Duncan Barclay wrote: Can I suggest you add a DS22 for DS 22Mb/s which is going through final approvals at the IEEE. I've added it and updated the diff for -current. I'll mess with the -stable diff Thursday when I get back from my short vacation. I'll wait for these patches to settle down and merge the functionality into the raylink driver. Sounds good. We'll need to figure out how to specify hopsets. You can either overload channel or add a new hopset option. Are you planning on making a unified interface for things like the signal strenght cache? I'm not sure at this point. It's probalby a good idea, though it may be to expensive to populate on interfaces. For instance, the an driver only sets one of the three possible values. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: Call for review... PR 25577
I stupidly wrote: it is not immediately obvious to me how to set ad-hoc mode using ifconfig(8)). Please disregard...I see it now. Must be my allergy meds, yeah, that's it... :-) Bruce. PGP signature
Re: Call for review... PR 25577
Cool. Does this mean that any of the foocontrol programs can go away? I've long wished that we could have some of the wireless control stuff go directly into ifconfig rather than having to run an external program before bringing up the interface. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
In message [EMAIL PROTECTED] Jordan Hubbard writes: : Cool. Does this mean that any of the foocontrol programs can go away? : I've long wished that we could have some of the wireless control stuff : go directly into ifconfig rather than having to run an external : program before bringing up the interface. Mostly. There are still some minor issues, but the vast majority of the functionality they provide can go poof. My comment to the patch would be lose the ifdef. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
In message [EMAIL PROTECTED], Jordan Hubbard writes: Cool. Does this mean that any of the foocontrol programs can go away? As far as I can see, anything short of firmware updates can be done by ifconfig and therefore, presumably, foocontrol can die for 802.11-valued foo. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
On Fri, Mar 30, 2001 at 01:14:13PM -0800, Jordan Hubbard wrote: Cool. Does this mean that any of the foocontrol programs can go away? I've long wished that we could have some of the wireless control stuff go directly into ifconfig rather than having to run an external program before bringing up the interface. They won't go away, but 99.99% of people won't have to touch them. There are a number of vendor specific settings that I didn't attempt to build generic ioctl interfaces for, but you really don't need them most of the time. I'm planning to add some more features to the ioctl interface over time including the stuff necessicary to build generic version of the pretty GUI apps you get in Windows. As an extra bonus, this stuff should let you install with a floppy and a wireless nic. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: Call for review... PR 25577
From: Poul-Henning Kamp [EMAIL PROTECTED] Date: Fri, 30 Mar 2001 23:07:08 +0200 Any comments/reviews before we commit the patch to PR25577 ? OK; I've built today's -CURRENT (this time, after applying Brooks' patchset; I had built -CURRENT earlier today). Here's a (slightly sanitized) ifconfig output: m758712358[1] ifconfig gif0: flags=8010POINTOPOINT,MULTICAST mtu 1280 gif1: flags=8010POINTOPOINT,MULTICAST mtu 1280 gif2: flags=8010POINTOPOINT,MULTICAST mtu 1280 gif3: flags=8010POINTOPOINT,MULTICAST mtu 1280 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 faith0: flags=8000MULTICAST mtu 1500 an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::240:96ff:fe34:4ee9%an0 prefixlen 64 scopeid 0x8 inet 207.76.207.214 netmask 0xff00 broadcast 207.76.207.255 ether 00:40:96:34:4e:e9 media: autoselect (DS/11Mbps) status: associated supported media: autoselect autoselect adhoc DS/11Mbps DS/11Mbps adhoc DS/5.5Mbps DS/5.5Mbps adhoc DS/2Mbps DS/2Mbps adhoc DS/1Mbps DS/1Mbps adhoc ssid SSID goes here stationname "" channel 6 authmode OPEN powersavemode OFF powersavesleep 200 wepmode OFF weptxkey 2 wepkey 1:64-bit m758712358[2] So I haven't got so far as to actually *use* the ifconfig capabilities to get the card configured -- I had already worked up a script to do that with ancontrol, and I wanted to get this out sooner than it would take me to re-work that. First, this looks very promising; I like the direction and the bulk of the implementation (from what I've seen so far). One concern, and this may well affect other NIC flavors, is the list of media types is a little annoying to parse. Hmmm... speaking Perl, I suppose it could be characterized as /^\s+supported media:(\s[\S+(\sadhoc)?)+$/ Nevertheless, I believe it would be a little easier to parse (both for people simple scripts) if the separator before "adhoc" were different from the one between adjacent supported media. Or am I just being rather denser than usual? Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for review... PR 25577
On Fri, Mar 30, 2001 at 03:51:27PM -0800, David Wolfskill wrote:
One concern, and this may well affect other NIC flavors, is the list of
media types is a little annoying to parse. Hmmm... speaking Perl, I
suppose it could be characterized as
/^\s+supported media:(\s[\S+(\sadhoc)?)+$/
Nevertheless, I believe it would be a little easier to parse (both for
people simple scripts) if the separator before "adhoc" were
different from the one between adjacent supported media.
Or am I just being rather denser than usual?
No, you're entirely correct. However, this isn't my fault. ;-) The
problem here is that our ifconfig's if_media support is really crappy.
My proposed solution is to take the -m option from {Net,Open}BSD.
Without the -m flag they don't display the supported media list. With
it, they display it in a much cleaner manner with one possability per
line. It's on my todo list though anyone else could deal with it as
well. I figured this patch was big enough without adding a bunch of
cleanups to it. As it stands, there is a cleanup of a bug that ment you
could never see some mediaopt's in the supported list. Instead you'd
see the same media type twice with not differences. Apparently no one
actually uses mediaopts other then full-duplex. ;-)
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
PGP signature
