Menu
▾
▴
wirelessdriver-devel — Discussion of development related issues
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(16) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
(6) |
May
(5) |
Jun
(3) |
Jul
(4) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2003 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
|
May
(3) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(9) |
Dec
(4) |
| 2004 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(3) |
Jul
(1) |
Aug
(5) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
|
From: yjin8 <yj...@21...> - 2001-12-20 02:35:10
|
DQpUaGUgZXJyb3IgbWVzc2FnZSBpcyAidGhlIGFwcGxpY2F0aW9uIHN5c3RlbSBwcmVmZXJlbmNl cyBoYXMgdW5leHBlY2VkbHkgcXVpdCINCiAgICAgICAgICAgICAgICAgICAgICJ0aGUgc3lzdGVt IGFuZCBvdGhlciBhcHBsaWNhdGlvbnMgaGF2ZSBub3QgYmVlbiBhZmZlY3RlZC4iDQogICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAiT0si DQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiB5amluOCANClRvOiB3aXJl bGVzc2RyaXZlci1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQgDQpTZW50OiBUaHVyc2RheSwg RGVjZW1iZXIgMjAsIDIwMDEgMTA6MjQgQU0NClN1YmplY3Q6IGhlbHA6IG15IHdpcmVsZXNzIGNh cmQgY2FuJ3QgYmUgZm91bmQgaW4gdGhlIHN5c3RlbSBwcmVmZXJlbmNlcw0KDQoNCkRlYXIgU2ly LA0KICAgIEkndmUgdXNlZCB3aXJlbGVzcyBjYXJkIGluIFBvd2VyUEMgRzMgbm90ZWJvb2sgd2l0 aCBNQUMgT1MgMTAuMSwgYW5kICBpbnN0YWxsZWQgdGhlIGRyaXZlciBmcm9tIHRoZSBzb3VyY2Vm b3JnZS4gSSBmb3VuZCB0aGF0IHRoZSB3aXJlbGVzcyBjYXJkIHdhcyB3b3JraW5nIG9uLCBhbmQg SSBjb3VsZCBjb25maWd1cmF0ZSB0aGUgSVAgYWRkcmVzcyBhbmQgRE5TIGluIHRoZSB0ZXJtaW5h bCwgYnV0IGluIHRoZSBzeXN0ZW0gcHJlZmVyZW5jZXMgSSBjYW4ndCBvcGVuIHRoZSBuZXR3b3Jr IGl0ZW0sIGlmIGkgcHVsbCB0aGUgd2lyZWxlc3MgY2FyZCBvdXQsIGFuZCBvcGVuIHRoZSBuZXR3 b3JrIGl0ZW0sIHRoZW4gaW5zZXJ0IHRoZSB3aXJlbGVzcyBjYXJkLCB0aGUgY2FyZCB3b3JrIG9u LCBhbmQgaW4gdGhlIG5ldHdvcmsgcHJlZmVyZW5jZSBJIGNhbid0IGZpbmQgdGhlIGFpcnBvcnQg aXRlbSB0byBiZSBzZWxlY3RlZC4gDQogICAgSWYgeW91IGNvdWxkIHRlbGwgbWUgdGhhdCdzIHdo eSwgYW5kIGhvdyB0byB3cml0ZSBteSBjYXJkIGluZm9ybWF0aW9uIHRvIHRoZSBzeXN0ZW0gcHJl ZmVyZW5jZXMuDQogICAgVGhhbmtzIHZlcnkgbXVjaC4NCg0KDQoNCiANCg== |
|
From: yjin8 <yj...@21...> - 2001-12-20 02:26:32
|
RGVhciBTaXIsDQogICAgSSd2ZSB1c2VkIHdpcmVsZXNzIGNhcmQgaW4gUG93ZXJQQyBHMyBub3Rl Ym9vayB3aXRoIE1BQyBPUyAxMC4xLCBhbmQgIGluc3RhbGxlZCB0aGUgZHJpdmVyIGZyb20gdGhl IHNvdXJjZWZvcmdlLiBJIGZvdW5kIHRoYXQgdGhlIHdpcmVsZXNzIGNhcmQgd2FzIHdvcmsgb24s IGFuZCBJIGNvdWxkIGNvbmZpZ3VyYXRlIHRoZSBJUCBhZGRyZXNzIGFuZCBETlMsIGJ1dCBpbiB0 aGUgc3lzdGVtIHByZWZlcmVuY2VzIEkgY2FuJ3Qgb3BlbiB0aGUgbmV0d29yayBpdGVtLCBpZiBp IHB1bGwgdGhlIHdpcmVsZXNzIGNhcmQgb3V0LCBhbmQgb3BlbiB0aGUgbmV0d29yayBpdGVtLCB0 aGVuIGluc2VydCB0aGUgd2lyZWxlc3MgY2FyZCwgdGhlIGNhcmQgd29yayBvbiwgYW5kIGluIHRo ZSBuZXR3b3JrIHByZWZlcmVuY2UgSSBjYW4ndCBmaW5kIHRoZSBhaXJwb3J0IGl0ZW0gdG8gYmUg c2VsZWN0ZWQuIA0KICAgIElmIHlvdSBjb3VsZCB0ZWxsIG1lIHRoYXQncyB3aHksIGFuZCBob3cg dG8gd3JpdGUgbXkgY2FyZCBpbmZvcm1hdGlvbiB0byB0aGUgc3lzdGVtIHByZWZlcmVuY2VzLg0K ICAgIFRoYW5rcyB2ZXJ5IG11Y2guDQoNCg0KDQogDQo= |
|
From: Curtis L. <cur...@hp...> - 2001-12-18 16:31:54
|
That is great, I am excited to get that drop. You mentioned that use of the keychain could make the command line tool incompatible with Darwin. If you have read the docs you probably realize that while the keychain stores passwords it does not remove the need to have a UI to enter passwords - because that is how passwords are entering into the keychain. Consequently a way of getting the password from the user must always exist in case the keychain is either unavailable or does not have the needed password. It just requires more work on your part. This is nothing new, a UI easier for the user is usually more work for the guy writing the code. Thanks again to all for providing this driver! Curtis On 12/18/01 4:21 AM, "David Ross" <n1...@ma...> wrote: > I've taken a look at the API for the key chain and I estimate that I'll > have support done by the New Year. > > There is a lot of documentation to read to make sure that I implement it > correctly, but it looks doable. > > -- Dave > > On Friday, December 14, 2001, at 08:07 PM, David Ross wrote: > >> I'm thinking that if the api is understandable enough that I'll move >> all password storage into the keychain. >> Though this has one downside - if I make a command line tool to allow >> manipulation of the driver or just to init it, there would be no way to >> access the keychain before you logged in (as far as I know) and it >> would make the commandline tool darwin incompatible. >> >> I'll take a look into this, this weekend and get back to you on Sunday >> on how long it will take me to get this done. >> >> -- Dave >> >> >> On Friday, December 14, 2001, at 07:55 PM, Curtis Laser wrote: >> >>> The 128 bit network is driven by HP branded Lucent Access Points that >>> are >>> stuffed with Orinoco Gold cards. >>> >>> As I remember the keychain API you pass in something like an account >>> or URL >>> and you get the password for it back. The network could obviously be >>> the >>> "account". The only limitation would be one password per network but >>> that >>> doesn't seem all that restrictive. A big benefit of using the API is >>> that >>> the passwords are stored in an encrypted file. >>> >>> Curtis >>> >>> >>> on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: >>> >>>> Curtis, >>>> >>>> Interesting that the Orinoco Gold cards appear to be different >>>> from the WaveLAN gold cards. What type of access point is driving your >>>> 128 bit network? >>>> >>>> As far as keychain support for the prefpane is concerned, that >>>> is an interesting idea. I know that Dave was planning to implement a >>>> mechanism for saving passwords to a pref file (or pw file) but I don't >>>> know if he has considered keychain support. Do you think it would work >>>> well with saving multiple networks and passwords? If so, perhaps you >>>> and >>>> dave should discuss it. Please post any future development discussion >>>> to >>>> the devel list. >>>> >>>> Thanks for your feedback & interest in helping, >>>> >>>> Y >>>> >>>> On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: >>>> >>>> >>>>> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of >>>>> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. >>>>> >>>>> I connect to both a 128 bit and 40 bit encrypted networks. I have >>>>> tried a number of cards with this version of the software. >>>>> >>>>> Using an Orinoco Gold card I can connect to the 128 bit encrypted >>>>> network, but not to the 40 bit encrypted network. The WEP key for the >>>>> 128 bit network is a simple hex representation of the ASCII >>>>> characters >>>>> in the key. I tried both this approach and getting the key from >>>>> Airport Config's utility with the 40 bit network and neither worked. >>>>> >>>>> I thought I might be doing something wrong, so I tried a Silver card >>>>> (HP branded but essentially a silver Orinoco card) and this was able >>>>> to connect to the 40 bit network (using the key from Airport Config) >>>>> without problems. I suspect that there is a problem for Orinoco Gold >>>>> cards accessing a 40 bit encrypted network. >>>>> >>>>> I can also confirm that I could connect to neither network using a >>>>> WaveLAN gold card. >>>>> >>>>> I have considered adding Keychain support to the Wireless Config >>>>> panel, but before I start mucking with the code I wanted to know how >>>>> much turmoil that part of the code is currently experiencing, I >>>>> wouldn't want to step on your toes. >>>>> >>>>> Thanks for all your hard work! >>>>> Curtis Laser >>>>> >>>> >>> >> >> >> _______________________________________________ >> Wirelessdriver-devel mailing list >> Wir...@li... >> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > |
|
From: David R. <n1...@ma...> - 2001-12-18 11:21:21
|
I've taken a look at the API for the key chain and I estimate that I'll have support done by the New Year. There is a lot of documentation to read to make sure that I implement it correctly, but it looks doable. -- Dave On Friday, December 14, 2001, at 08:07 PM, David Ross wrote: > I'm thinking that if the api is understandable enough that I'll move > all password storage into the keychain. > Though this has one downside - if I make a command line tool to allow > manipulation of the driver or just to init it, there would be no way to > access the keychain before you logged in (as far as I know) and it > would make the commandline tool darwin incompatible. > > I'll take a look into this, this weekend and get back to you on Sunday > on how long it will take me to get this done. > > -- Dave > > > On Friday, December 14, 2001, at 07:55 PM, Curtis Laser wrote: > >> The 128 bit network is driven by HP branded Lucent Access Points that >> are >> stuffed with Orinoco Gold cards. >> >> As I remember the keychain API you pass in something like an account >> or URL >> and you get the password for it back. The network could obviously be >> the >> "account". The only limitation would be one password per network but >> that >> doesn't seem all that restrictive. A big benefit of using the API is >> that >> the passwords are stored in an encrypted file. >> >> Curtis >> >> >> on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: >> >>> Curtis, >>> >>> Interesting that the Orinoco Gold cards appear to be different >>> from the WaveLAN gold cards. What type of access point is driving your >>> 128 bit network? >>> >>> As far as keychain support for the prefpane is concerned, that >>> is an interesting idea. I know that Dave was planning to implement a >>> mechanism for saving passwords to a pref file (or pw file) but I don't >>> know if he has considered keychain support. Do you think it would work >>> well with saving multiple networks and passwords? If so, perhaps you >>> and >>> dave should discuss it. Please post any future development discussion >>> to >>> the devel list. >>> >>> Thanks for your feedback & interest in helping, >>> >>> Y >>> >>> On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: >>> >>> >>>> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of >>>> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. >>>> >>>> I connect to both a 128 bit and 40 bit encrypted networks. I have >>>> tried a number of cards with this version of the software. >>>> >>>> Using an Orinoco Gold card I can connect to the 128 bit encrypted >>>> network, but not to the 40 bit encrypted network. The WEP key for the >>>> 128 bit network is a simple hex representation of the ASCII >>>> characters >>>> in the key. I tried both this approach and getting the key from >>>> Airport Config's utility with the 40 bit network and neither worked. >>>> >>>> I thought I might be doing something wrong, so I tried a Silver card >>>> (HP branded but essentially a silver Orinoco card) and this was able >>>> to connect to the 40 bit network (using the key from Airport Config) >>>> without problems. I suspect that there is a problem for Orinoco Gold >>>> cards accessing a 40 bit encrypted network. >>>> >>>> I can also confirm that I could connect to neither network using a >>>> WaveLAN gold card. >>>> >>>> I have considered adding Keychain support to the Wireless Config >>>> panel, but before I start mucking with the code I wanted to know how >>>> much turmoil that part of the code is currently experiencing, I >>>> wouldn't want to step on your toes. >>>> >>>> Thanks for all your hard work! >>>> Curtis Laser >>>> >>> >> > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |
|
From: Michael E. <mre...@ho...> - 2001-12-15 10:45:38
|
If you pass the keychain a url type thing, then just stuff the keys in like: http://NetworkName/Key1 http://NetworkName/Key2 http://NetworkName/Key3 http://NetworkName/Key4 Then if you detect a network name, you can query your keychain for that url on all four keys to see if anything hits. Or if you use a static network name, well - you get the picture. This is just an oursiders guess, BTW. I havn't even looked at coding for Carbon/Coca. Mike >From: Curtis Laser <cur...@hp...> >To: yuriwho <yu...@ma...> >CC: <wir...@li...>, David Ross ><n1...@ma...>, <Wir...@li...> >Subject: [Wirelessdriver-devel] Re: [Wirelessdriver-support] WEP >Functionality >Date: Fri, 14 Dec 2001 17:55:13 -0700 > >The 128 bit network is driven by HP branded Lucent Access Points that are >stuffed with Orinoco Gold cards. > >As I remember the keychain API you pass in something like an account or URL >and you get the password for it back. The network could obviously be the >"account". The only limitation would be one password per network but that >doesn't seem all that restrictive. A big benefit of using the API is that >the passwords are stored in an encrypted file. > >Curtis > > >on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: > > > Curtis, > > > > Interesting that the Orinoco Gold cards appear to be different > > from the WaveLAN gold cards. What type of access point is driving your > > 128 bit network? > > > > As far as keychain support for the prefpane is concerned, that > > is an interesting idea. I know that Dave was planning to implement a > > mechanism for saving passwords to a pref file (or pw file) but I don't > > know if he has considered keychain support. Do you think it would work > > well with saving multiple networks and passwords? If so, perhaps you and > > dave should discuss it. Please post any future development discussion to > > the devel list. > > > > Thanks for your feedback & interest in helping, > > > > Y > > > > On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: > > > > > >> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of > >> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. > >> > >> I connect to both a 128 bit and 40 bit encrypted networks. I have > >> tried a number of cards with this version of the software. > >> > >> Using an Orinoco Gold card I can connect to the 128 bit encrypted > >> network, but not to the 40 bit encrypted network. The WEP key for the > >> 128 bit network is a simple hex representation of the ASCII characters > >> in the key. I tried both this approach and getting the key from > >> Airport Config's utility with the 40 bit network and neither worked. > >> > >> I thought I might be doing something wrong, so I tried a Silver card > >> (HP branded but essentially a silver Orinoco card) and this was able > >> to connect to the 40 bit network (using the key from Airport Config) > >> without problems. I suspect that there is a problem for Orinoco Gold > >> cards accessing a 40 bit encrypted network. > >> > >> I can also confirm that I could connect to neither network using a > >> WaveLAN gold card. > >> > >> I have considered adding Keychain support to the Wireless Config > >> panel, but before I start mucking with the code I wanted to know how > >> much turmoil that part of the code is currently experiencing, I > >> wouldn't want to step on your toes. > >> > >> Thanks for all your hard work! > >> Curtis Laser > >> > > > > >_______________________________________________ >Wirelessdriver-devel mailing list >Wir...@li... >https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx |
|
From: David R. <n1...@ma...> - 2001-12-15 01:07:28
|
I'm thinking that if the api is understandable enough that I'll move all password storage into the keychain. Though this has one downside - if I make a command line tool to allow manipulation of the driver or just to init it, there would be no way to access the keychain before you logged in (as far as I know) and it would make the commandline tool darwin incompatible. I'll take a look into this, this weekend and get back to you on Sunday on how long it will take me to get this done. -- Dave On Friday, December 14, 2001, at 07:55 PM, Curtis Laser wrote: > The 128 bit network is driven by HP branded Lucent Access Points that > are > stuffed with Orinoco Gold cards. > > As I remember the keychain API you pass in something like an account or > URL > and you get the password for it back. The network could obviously be the > "account". The only limitation would be one password per network but > that > doesn't seem all that restrictive. A big benefit of using the API is > that > the passwords are stored in an encrypted file. > > Curtis > > > on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: > >> Curtis, >> >> Interesting that the Orinoco Gold cards appear to be different >> from the WaveLAN gold cards. What type of access point is driving your >> 128 bit network? >> >> As far as keychain support for the prefpane is concerned, that >> is an interesting idea. I know that Dave was planning to implement a >> mechanism for saving passwords to a pref file (or pw file) but I don't >> know if he has considered keychain support. Do you think it would work >> well with saving multiple networks and passwords? If so, perhaps you >> and >> dave should discuss it. Please post any future development discussion >> to >> the devel list. >> >> Thanks for your feedback & interest in helping, >> >> Y >> >> On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: >> >> >>> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of >>> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. >>> >>> I connect to both a 128 bit and 40 bit encrypted networks. I have >>> tried a number of cards with this version of the software. >>> >>> Using an Orinoco Gold card I can connect to the 128 bit encrypted >>> network, but not to the 40 bit encrypted network. The WEP key for the >>> 128 bit network is a simple hex representation of the ASCII characters >>> in the key. I tried both this approach and getting the key from >>> Airport Config's utility with the 40 bit network and neither worked. >>> >>> I thought I might be doing something wrong, so I tried a Silver card >>> (HP branded but essentially a silver Orinoco card) and this was able >>> to connect to the 40 bit network (using the key from Airport Config) >>> without problems. I suspect that there is a problem for Orinoco Gold >>> cards accessing a 40 bit encrypted network. >>> >>> I can also confirm that I could connect to neither network using a >>> WaveLAN gold card. >>> >>> I have considered adding Keychain support to the Wireless Config >>> panel, but before I start mucking with the code I wanted to know how >>> much turmoil that part of the code is currently experiencing, I >>> wouldn't want to step on your toes. >>> >>> Thanks for all your hard work! >>> Curtis Laser >>> >> > |
|
From: Curtis L. <cur...@hp...> - 2001-12-15 00:55:12
|
The 128 bit network is driven by HP branded Lucent Access Points that are stuffed with Orinoco Gold cards. As I remember the keychain API you pass in something like an account or URL and you get the password for it back. The network could obviously be the "account". The only limitation would be one password per network but that doesn't seem all that restrictive. A big benefit of using the API is that the passwords are stored in an encrypted file. Curtis on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: > Curtis, > > Interesting that the Orinoco Gold cards appear to be different > from the WaveLAN gold cards. What type of access point is driving your > 128 bit network? > > As far as keychain support for the prefpane is concerned, that > is an interesting idea. I know that Dave was planning to implement a > mechanism for saving passwords to a pref file (or pw file) but I don't > know if he has considered keychain support. Do you think it would work > well with saving multiple networks and passwords? If so, perhaps you and > dave should discuss it. Please post any future development discussion to > the devel list. > > Thanks for your feedback & interest in helping, > > Y > > On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: > > >> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of >> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. >> >> I connect to both a 128 bit and 40 bit encrypted networks. I have >> tried a number of cards with this version of the software. >> >> Using an Orinoco Gold card I can connect to the 128 bit encrypted >> network, but not to the 40 bit encrypted network. The WEP key for the >> 128 bit network is a simple hex representation of the ASCII characters >> in the key. I tried both this approach and getting the key from >> Airport Config's utility with the 40 bit network and neither worked. >> >> I thought I might be doing something wrong, so I tried a Silver card >> (HP branded but essentially a silver Orinoco card) and this was able >> to connect to the 40 bit network (using the key from Airport Config) >> without problems. I suspect that there is a problem for Orinoco Gold >> cards accessing a 40 bit encrypted network. >> >> I can also confirm that I could connect to neither network using a >> WaveLAN gold card. >> >> I have considered adding Keychain support to the Wireless Config >> panel, but before I start mucking with the code I wanted to know how >> much turmoil that part of the code is currently experiencing, I >> wouldn't want to step on your toes. >> >> Thanks for all your hard work! >> Curtis Laser >> > |
|
From: yuriwho <yu...@ma...> - 2001-12-15 00:29:47
|
Curtis, Interesting that the Orinoco Gold cards appear to be different from the WaveLAN gold cards. What type of access point is driving your 128 bit network? As far as keychain support for the prefpane is concerned, that is an interesting idea. I know that Dave was planning to implement a mechanism for saving passwords to a pref file (or pw file) but I don't know if he has considered keychain support. Do you think it would work well with saving multiple networks and passwords? If so, perhaps you and dave should discuss it. Please post any future development discussion to the devel list. Thanks for your feedback & interest in helping, Y On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: > I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of > IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. > > I connect to both a 128 bit and 40 bit encrypted networks. I have tried > a number of cards with this version of the software. > > Using an Orinoco Gold card I can connect to the 128 bit encrypted > network, but not to the 40 bit encrypted network. The WEP key for the > 128 bit network is a simple hex representation of the ASCII characters > in the key. I tried both this approach and getting the key from Airport > Config's utility with the 40 bit network and neither worked. > > I thought I might be doing something wrong, so I tried a Silver card > (HP branded but essentially a silver Orinoco card) and this was able to > connect to the 40 bit network (using the key from Airport Config) > without problems. I suspect that there is a problem for Orinoco Gold > cards accessing a 40 bit encrypted network. > > I can also confirm that I could connect to neither network using a > WaveLAN gold card. > > I have considered adding Keychain support to the Wireless Config panel, > but before I start mucking with the code I wanted to know how much > turmoil that part of the code is currently experiencing, I wouldn't > want to step on your toes. > > Thanks for all your hard work! > Curtis Laser |
|
From: h1kari <h1...@da...> - 2001-12-13 01:05:19
|
Rob, Do you know if there's anyone working on making WirelessDriver work with the internal Airport cards? I've been having people ask me a lot about this, and I just want to know if it'll be implemented in the near future or if you could use some help with getting it in. Cheers, -h1kari On 12/12/01 11:28 AM, "Rob McKeever" <ro...@ma...> wrote: > This is good news. I've been preoccupied with other stuff > recently and haven't had much time to think about things here. > Anything that you have will be gladly rolled in to the code. > > I am working on a reorganized version of the driver that will > split off the 802.11 handling from the device-specific code > making things a lot easier to work on in the future. Should be > ready before Christmas... I'll keep everyone posted. > > -Rob > > On Wednesday, December 12, 2001, at 06:09 AM, h1kari wrote: > >> Greetings, >> >> I've been working on patches to WirelessDriver for most of the >> night and I >> should be able to submit some stuff in the next day or so. Just >> letting all >> of you know that I'm working on this, so there isn't any >> conflicting work >> going on. Exactly what I'm implementing includes: >> >> - Procframe Support >> Simple patch that disables stripping of the 802.11 hermes header that's >> provided by the card. >> >> - Prism2 Debug Mode Support >> Support for all 14 of the prism2 debug modes including monitor >> mode (I'll >> probably port prism2ctl over to use the IOKit interface for easy >> manipulation from the terminal) >> >> - Scan Mode Support for Both Prism2 and ORiNOCO Wavelan >> To detect Access Points in the area through the card's scan >> request/response >> mechanism. This will be made to be used through >> dstumbler/wicontrol/etc. >> >> Let me know if anyone else is working on this, so we might be >> able to double >> our efforts, and I'll keep the list posted on my progress. >> >> Thanks for the wonderful driver ! >> -h1kari >> >> >> _______________________________________________ >> Wirelessdriver-devel mailing list >> Wir...@li... >> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > |
|
From: Rob M. <ro...@ma...> - 2001-12-12 19:28:29
|
This is good news. I've been preoccupied with other stuff recently and haven't had much time to think about things here. Anything that you have will be gladly rolled in to the code. I am working on a reorganized version of the driver that will split off the 802.11 handling from the device-specific code making things a lot easier to work on in the future. Should be ready before Christmas... I'll keep everyone posted. -Rob On Wednesday, December 12, 2001, at 06:09 AM, h1kari wrote: > Greetings, > > I've been working on patches to WirelessDriver for most of the > night and I > should be able to submit some stuff in the next day or so. Just > letting all > of you know that I'm working on this, so there isn't any > conflicting work > going on. Exactly what I'm implementing includes: > > - Procframe Support > Simple patch that disables stripping of the 802.11 hermes header that's > provided by the card. > > - Prism2 Debug Mode Support > Support for all 14 of the prism2 debug modes including monitor > mode (I'll > probably port prism2ctl over to use the IOKit interface for easy > manipulation from the terminal) > > - Scan Mode Support for Both Prism2 and ORiNOCO Wavelan > To detect Access Points in the area through the card's scan > request/response > mechanism. This will be made to be used through > dstumbler/wicontrol/etc. > > Let me know if anyone else is working on this, so we might be > able to double > our efforts, and I'll keep the list posted on my progress. > > Thanks for the wonderful driver ! > -h1kari > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |
|
From: h1kari <h1...@da...> - 2001-12-12 14:10:23
|
Greetings, I've been working on patches to WirelessDriver for most of the night and I should be able to submit some stuff in the next day or so. Just letting all of you know that I'm working on this, so there isn't any conflicting work going on. Exactly what I'm implementing includes: - Procframe Support Simple patch that disables stripping of the 802.11 hermes header that's provided by the card. - Prism2 Debug Mode Support Support for all 14 of the prism2 debug modes including monitor mode (I'll probably port prism2ctl over to use the IOKit interface for easy manipulation from the terminal) - Scan Mode Support for Both Prism2 and ORiNOCO Wavelan To detect Access Points in the area through the card's scan request/response mechanism. This will be made to be used through dstumbler/wicontrol/etc. Let me know if anyone else is working on this, so we might be able to double our efforts, and I'll keep the list posted on my progress. Thanks for the wonderful driver ! -h1kari |
|
From: David R. <n1...@ma...> - 2001-11-20 11:43:52
|
The reason the WEP field is blank is for security reasons. Soon there will be an update that will fill the box with asterisks. At the moment there is no code to check to see if you changed the fields before pressing apply so that if you were to see the asterisks and pressed apply your connection would no longer work and you would wonder why. This seemed like the best interim solution. -- Dave On Saturday, November 17, 2001, at 03:39 PM, Michael Eckhoff wrote: > > Turn it over and get the model number. > > Then check it against this page: > > http://www.bookendzdocks.com/dockid.html > > As for the WEP password field being blank, I found that interesting as > well. My guess is that since the card is already programmed, it works > fine after sleep. But it doesn't show up in the box because you > probably can't retrieve your active code from the card itself -- just a > guess. > > Mike > >> From: Steve Wainstead <sw...@pa...> >> To: Rob McKeever <ro...@ma...> >> CC: Michael Eckhoff <mre...@ho...>, <wirelessdriver- >> de...@li...> >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >> Date: Sat, 17 Nov 2001 12:45:23 -0500 (EST) >> >> >> I've had no problems with sleep/awaken on my Powerbook. (I actually >> don't >> know if it's a Lombard or Wallstreet or whatever. If someone could >> point >> me to a resource that explains this, please do). >> >> However I find that after booting, the card won't work until I open the >> Preferences panel, and then it instantly connects to my router. (I >> don't >> have to take any action at all except open System Prefs and then >> WirelessConfig.) >> >> The other oddity is that I never have to enter the Network Equivalent >> Key, >> and the field is always blank. It would be more consistent with other >> interfaces if something like "*************" appeared in the box. I >> feel >> like I'm somehow using WEP without a password. >> >> Also, is there any reason why "Network Equivalent Key" isn't just >> called >> "Network Password"? >> >> ~swain >> >> On Wed, 14 Nov 2001, Rob McKeever wrote: >> >> > ...and I know what needs to be done to fix that problem, >> > too :-) That's one of the two main objectives for the next >> > revision. >> > >> > The problem with sleep was that many people were seeing the >> > powerbook go to sleep, then refusing to wake up. I've also >> > heard from a lot of people that are finding it to be working >> > just fine, so... ? I figured I'd error on the safe side. I'm >> > going to have the next version make the interface temporarily >> > unavailable and power down the card just to be on the safe side. >> > >> > I'll let you know when I've got stuff to test. Probably about a >> > week or so before I get any real time to play, though. >> > >> > -Rob >> > >> > >> > On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: >> > >> > > >> > > Heh... nice how that works, eh? >> > > >> > > Anything else that needs testing? >> > > >> > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume >> > > just fine. In fact, I can suspend, unplug my card, pack up and >> > > go home, put my card back in, and resume and everything works >> > > just fine. The card also appears to shutdown when the system >> > > goes to sleep since all the link lights go dark. What is >> > > everyone else seeing? >> > > >> > > Only thing I can't do is remove it and put it back in while the >> > > system is live (documented problem :). >> > > >> > > Mike >> > > >> > >> From: Rob McKeever <ro...@ma...> >> > >> To: "Michael Eckhoff" <mre...@ho...> >> > >> CC: wir...@li... >> > >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >> > >> Date: Wed, 14 Nov 2001 21:28:05 -0800 >> > >> >> > >> It's always nice to see that the patches I put in without >> > >> testing actually work :-) >> > >> >> > >> Thanks for the feedback! >> > >> >> > >> -Rob >> > >> >> > >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff >> wrote: >> > >> >> > >>> >> > >>> It looks like IP Multicast is working fine. I have not spent a >> > >>> lot of time testing, but here are my informal results: >> > >>> >> > >>> I was able to receive IP multicast packets with 100% success at >> > >>> about 40pps and 300k packets. >> > >>> I was able to receive IP multicast packets with 100% success at >> > >>> about 13pps and 512k packets. >> > >>> I was able to receive IP multicast packets with about 99% >> > >>> success at about 11pps and 1024k packets. >> > >>> >> > >>> No duplicate packets were detected - so the stack appers to be >> > >>> handling everything correctly. >> > >>> The program uses a very basic serialization to ensure that >> > >>> packet order and is maintained (on a LAN only - all bets are >> > >>> off for WAN) and data corruption does not occur. >> > >>> >> > >>> I havn't looked into tuning my AP for IP multicast. it is >> > >>> currently set to only allow 2 meg to be used for multicast. >> > >>> When I find time, I may try to adjust these settings to see >> > >>> what the max is that I can get. >> > >>> >> > >>> At any rate, it does appear that everything is working. >> > >>> >> > >>> Thanks! >> > >>> >> > >>> Mike >> > >>> >> > >>> _________________________________________________________________ >> > >>> Get your FREE download of MSN Explorer at >> > >>> http://explorer.msn.com/intl.asp >> > >>> >> > >>> >> > >>> _______________________________________________ >> > >>> Wirelessdriver-devel mailing list >> > >>> Wir...@li... >> > >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel >> > >> >> > > >> > > >> > > _________________________________________________________________ >> > > Get your FREE download of MSN Explorer at >> > > http://explorer.msn.com/intl.asp >> > > >> > >> > >> > _______________________________________________ >> > Wirelessdriver-devel mailing list >> > Wir...@li... >> > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel >> > >> >> --- >> http://www.panix.com/~swain/ >> "Without music to decorate it, time is just a bunch of boring >> production deadlines or dates by which bills must be paid." >> -- Frank Zappa >> >> >> _______________________________________________ >> Wirelessdriver-devel mailing list >> Wir...@li... >> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |
|
From: Steve W. <sw...@pa...> - 2001-11-17 21:19:22
|
Pismo. Thanks! :-) ~swain On Sat, 17 Nov 2001, Michael Eckhoff wrote: > > Turn it over and get the model number. > > Then check it against this page: > > http://www.bookendzdocks.com/dockid.html > > As for the WEP password field being blank, I found that interesting as well. > My guess is that since the card is already programmed, it works fine after > sleep. But it doesn't show up in the box because you probably can't > retrieve your active code from the card itself -- just a guess. > > Mike > > >From: Steve Wainstead <sw...@pa...> > >To: Rob McKeever <ro...@ma...> > >CC: Michael Eckhoff <mre...@ho...>, > ><wir...@li...> > >Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results > >Date: Sat, 17 Nov 2001 12:45:23 -0500 (EST) > > > > > >I've had no problems with sleep/awaken on my Powerbook. (I actually don't > >know if it's a Lombard or Wallstreet or whatever. If someone could point > >me to a resource that explains this, please do). > > > >However I find that after booting, the card won't work until I open the > >Preferences panel, and then it instantly connects to my router. (I don't > >have to take any action at all except open System Prefs and then > >WirelessConfig.) > > > >The other oddity is that I never have to enter the Network Equivalent Key, > >and the field is always blank. It would be more consistent with other > >interfaces if something like "*************" appeared in the box. I feel > >like I'm somehow using WEP without a password. > > > >Also, is there any reason why "Network Equivalent Key" isn't just called > >"Network Password"? > > > >~swain > > > >On Wed, 14 Nov 2001, Rob McKeever wrote: > > > > > ...and I know what needs to be done to fix that problem, > > > too :-) That's one of the two main objectives for the next > > > revision. > > > > > > The problem with sleep was that many people were seeing the > > > powerbook go to sleep, then refusing to wake up. I've also > > > heard from a lot of people that are finding it to be working > > > just fine, so... ? I figured I'd error on the safe side. I'm > > > going to have the next version make the interface temporarily > > > unavailable and power down the card just to be on the safe side. > > > > > > I'll let you know when I've got stuff to test. Probably about a > > > week or so before I get any real time to play, though. > > > > > > -Rob > > > > > > > > > On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: > > > > > > > > > > > Heh... nice how that works, eh? > > > > > > > > Anything else that needs testing? > > > > > > > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume > > > > just fine. In fact, I can suspend, unplug my card, pack up and > > > > go home, put my card back in, and resume and everything works > > > > just fine. The card also appears to shutdown when the system > > > > goes to sleep since all the link lights go dark. What is > > > > everyone else seeing? > > > > > > > > Only thing I can't do is remove it and put it back in while the > > > > system is live (documented problem :). > > > > > > > > Mike > > > > > > > >> From: Rob McKeever <ro...@ma...> > > > >> To: "Michael Eckhoff" <mre...@ho...> > > > >> CC: wir...@li... > > > >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results > > > >> Date: Wed, 14 Nov 2001 21:28:05 -0800 > > > >> > > > >> It's always nice to see that the patches I put in without > > > >> testing actually work :-) > > > >> > > > >> Thanks for the feedback! > > > >> > > > >> -Rob > > > >> > > > >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > > > >> > > > >>> > > > >>> It looks like IP Multicast is working fine. I have not spent a > > > >>> lot of time testing, but here are my informal results: > > > >>> > > > >>> I was able to receive IP multicast packets with 100% success at > > > >>> about 40pps and 300k packets. > > > >>> I was able to receive IP multicast packets with 100% success at > > > >>> about 13pps and 512k packets. > > > >>> I was able to receive IP multicast packets with about 99% > > > >>> success at about 11pps and 1024k packets. > > > >>> > > > >>> No duplicate packets were detected - so the stack appers to be > > > >>> handling everything correctly. > > > >>> The program uses a very basic serialization to ensure that > > > >>> packet order and is maintained (on a LAN only - all bets are > > > >>> off for WAN) and data corruption does not occur. > > > >>> > > > >>> I havn't looked into tuning my AP for IP multicast. it is > > > >>> currently set to only allow 2 meg to be used for multicast. > > > >>> When I find time, I may try to adjust these settings to see > > > >>> what the max is that I can get. > > > >>> > > > >>> At any rate, it does appear that everything is working. > > > >>> > > > >>> Thanks! > > > >>> > > > >>> Mike > > > >>> > > > >>> _________________________________________________________________ > > > >>> Get your FREE download of MSN Explorer at > > > >>> http://explorer.msn.com/intl.asp > > > >>> > > > >>> > > > >>> _______________________________________________ > > > >>> Wirelessdriver-devel mailing list > > > >>> Wir...@li... > > > >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > >> > > > > > > > > > > > > _________________________________________________________________ > > > > Get your FREE download of MSN Explorer at > > > > http://explorer.msn.com/intl.asp > > > > > > > > > > > > > _______________________________________________ > > > Wirelessdriver-devel mailing list > > > Wir...@li... > > > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > > > > >--- > > http://www.panix.com/~swain/ > >"Without music to decorate it, time is just a bunch of boring > >production deadlines or dates by which bills must be paid." > > -- Frank Zappa > > > > > >_______________________________________________ > >Wirelessdriver-devel mailing list > >Wir...@li... > >https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
|
From: Michael E. <mre...@ho...> - 2001-11-17 20:39:25
|
Turn it over and get the model number. Then check it against this page: http://www.bookendzdocks.com/dockid.html As for the WEP password field being blank, I found that interesting as well. My guess is that since the card is already programmed, it works fine after sleep. But it doesn't show up in the box because you probably can't retrieve your active code from the card itself -- just a guess. Mike >From: Steve Wainstead <sw...@pa...> >To: Rob McKeever <ro...@ma...> >CC: Michael Eckhoff <mre...@ho...>, ><wir...@li...> >Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >Date: Sat, 17 Nov 2001 12:45:23 -0500 (EST) > > >I've had no problems with sleep/awaken on my Powerbook. (I actually don't >know if it's a Lombard or Wallstreet or whatever. If someone could point >me to a resource that explains this, please do). > >However I find that after booting, the card won't work until I open the >Preferences panel, and then it instantly connects to my router. (I don't >have to take any action at all except open System Prefs and then >WirelessConfig.) > >The other oddity is that I never have to enter the Network Equivalent Key, >and the field is always blank. It would be more consistent with other >interfaces if something like "*************" appeared in the box. I feel >like I'm somehow using WEP without a password. > >Also, is there any reason why "Network Equivalent Key" isn't just called >"Network Password"? > >~swain > >On Wed, 14 Nov 2001, Rob McKeever wrote: > > > ...and I know what needs to be done to fix that problem, > > too :-) That's one of the two main objectives for the next > > revision. > > > > The problem with sleep was that many people were seeing the > > powerbook go to sleep, then refusing to wake up. I've also > > heard from a lot of people that are finding it to be working > > just fine, so... ? I figured I'd error on the safe side. I'm > > going to have the next version make the interface temporarily > > unavailable and power down the card just to be on the safe side. > > > > I'll let you know when I've got stuff to test. Probably about a > > week or so before I get any real time to play, though. > > > > -Rob > > > > > > On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: > > > > > > > > Heh... nice how that works, eh? > > > > > > Anything else that needs testing? > > > > > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume > > > just fine. In fact, I can suspend, unplug my card, pack up and > > > go home, put my card back in, and resume and everything works > > > just fine. The card also appears to shutdown when the system > > > goes to sleep since all the link lights go dark. What is > > > everyone else seeing? > > > > > > Only thing I can't do is remove it and put it back in while the > > > system is live (documented problem :). > > > > > > Mike > > > > > >> From: Rob McKeever <ro...@ma...> > > >> To: "Michael Eckhoff" <mre...@ho...> > > >> CC: wir...@li... > > >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results > > >> Date: Wed, 14 Nov 2001 21:28:05 -0800 > > >> > > >> It's always nice to see that the patches I put in without > > >> testing actually work :-) > > >> > > >> Thanks for the feedback! > > >> > > >> -Rob > > >> > > >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > > >> > > >>> > > >>> It looks like IP Multicast is working fine. I have not spent a > > >>> lot of time testing, but here are my informal results: > > >>> > > >>> I was able to receive IP multicast packets with 100% success at > > >>> about 40pps and 300k packets. > > >>> I was able to receive IP multicast packets with 100% success at > > >>> about 13pps and 512k packets. > > >>> I was able to receive IP multicast packets with about 99% > > >>> success at about 11pps and 1024k packets. > > >>> > > >>> No duplicate packets were detected - so the stack appers to be > > >>> handling everything correctly. > > >>> The program uses a very basic serialization to ensure that > > >>> packet order and is maintained (on a LAN only - all bets are > > >>> off for WAN) and data corruption does not occur. > > >>> > > >>> I havn't looked into tuning my AP for IP multicast. it is > > >>> currently set to only allow 2 meg to be used for multicast. > > >>> When I find time, I may try to adjust these settings to see > > >>> what the max is that I can get. > > >>> > > >>> At any rate, it does appear that everything is working. > > >>> > > >>> Thanks! > > >>> > > >>> Mike > > >>> > > >>> _________________________________________________________________ > > >>> Get your FREE download of MSN Explorer at > > >>> http://explorer.msn.com/intl.asp > > >>> > > >>> > > >>> _______________________________________________ > > >>> Wirelessdriver-devel mailing list > > >>> Wir...@li... > > >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > >> > > > > > > > > > _________________________________________________________________ > > > Get your FREE download of MSN Explorer at > > > http://explorer.msn.com/intl.asp > > > > > > > > > _______________________________________________ > > Wirelessdriver-devel mailing list > > Wir...@li... > > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > >--- > http://www.panix.com/~swain/ >"Without music to decorate it, time is just a bunch of boring >production deadlines or dates by which bills must be paid." > -- Frank Zappa > > >_______________________________________________ >Wirelessdriver-devel mailing list >Wir...@li... >https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
|
From: Steve W. <sw...@pa...> - 2001-11-17 18:04:29
|
On Sun, 11 Nov 2001, Rob McKeever wrote: > OK... > > I've giving it a bit of thought and I think this will help to > keep everyone happy with some small compromises. I want to > release the code as it stands right now without the network > search code as beta 3 and then start work on getting the code > reorganized and cleaned up for beta 4. This sounds like the best path. > > If I add the network search code to the driver as is, it'll > likely be limited to the Lucent Silver cards for now, and don't > want to make the code any more product specific. The other > option is to name this release as 3A and then to a 3B release > with search code for specific cards at some point shortly down > the road, but before the code rewrite is complete. I don't think playing with the version numbers makes much difference.. most users will go straight for the latest revision number, and then flame you when it doesn't work. Perhaps it's reached a point of stability that you could release a 1.0, and then start a new dev branch (1.1)? ~swain > So... for the next revision, I'm aiming for: > 1) Isolation of all of the 802.11 code from the > vendor-specific hardware code > ** This is the biggest and most important change that > needs to be made. > > 2) Automatic detection of networks > > 3) Clean removal and re-insertion of the card. > There may still be issues with interface naming, but at > least you wont crash anymore > > 4) Better behaviour during sleep. > > I'll make this new installer available to the members of this > list later on today, unless anybody's got any major objections. > Once I've had a few of you verify that it works OK, I'll release > it to the public witht he appropriate announcements. > > -Rob McKeever > ro...@ma... > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
|
From: Steve W. <sw...@pa...> - 2001-11-17 17:45:27
|
I've had no problems with sleep/awaken on my Powerbook. (I actually don't know if it's a Lombard or Wallstreet or whatever. If someone could point me to a resource that explains this, please do). However I find that after booting, the card won't work until I open the Preferences panel, and then it instantly connects to my router. (I don't have to take any action at all except open System Prefs and then WirelessConfig.) The other oddity is that I never have to enter the Network Equivalent Key, and the field is always blank. It would be more consistent with other interfaces if something like "*************" appeared in the box. I feel like I'm somehow using WEP without a password. Also, is there any reason why "Network Equivalent Key" isn't just called "Network Password"? ~swain On Wed, 14 Nov 2001, Rob McKeever wrote: > ...and I know what needs to be done to fix that problem, > too :-) That's one of the two main objectives for the next > revision. > > The problem with sleep was that many people were seeing the > powerbook go to sleep, then refusing to wake up. I've also > heard from a lot of people that are finding it to be working > just fine, so... ? I figured I'd error on the safe side. I'm > going to have the next version make the interface temporarily > unavailable and power down the card just to be on the safe side. > > I'll let you know when I've got stuff to test. Probably about a > week or so before I get any real time to play, though. > > -Rob > > > On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: > > > > > Heh... nice how that works, eh? > > > > Anything else that needs testing? > > > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume > > just fine. In fact, I can suspend, unplug my card, pack up and > > go home, put my card back in, and resume and everything works > > just fine. The card also appears to shutdown when the system > > goes to sleep since all the link lights go dark. What is > > everyone else seeing? > > > > Only thing I can't do is remove it and put it back in while the > > system is live (documented problem :). > > > > Mike > > > >> From: Rob McKeever <ro...@ma...> > >> To: "Michael Eckhoff" <mre...@ho...> > >> CC: wir...@li... > >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results > >> Date: Wed, 14 Nov 2001 21:28:05 -0800 > >> > >> It's always nice to see that the patches I put in without > >> testing actually work :-) > >> > >> Thanks for the feedback! > >> > >> -Rob > >> > >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > >> > >>> > >>> It looks like IP Multicast is working fine. I have not spent a > >>> lot of time testing, but here are my informal results: > >>> > >>> I was able to receive IP multicast packets with 100% success at > >>> about 40pps and 300k packets. > >>> I was able to receive IP multicast packets with 100% success at > >>> about 13pps and 512k packets. > >>> I was able to receive IP multicast packets with about 99% > >>> success at about 11pps and 1024k packets. > >>> > >>> No duplicate packets were detected - so the stack appers to be > >>> handling everything correctly. > >>> The program uses a very basic serialization to ensure that > >>> packet order and is maintained (on a LAN only - all bets are > >>> off for WAN) and data corruption does not occur. > >>> > >>> I havn't looked into tuning my AP for IP multicast. it is > >>> currently set to only allow 2 meg to be used for multicast. > >>> When I find time, I may try to adjust these settings to see > >>> what the max is that I can get. > >>> > >>> At any rate, it does appear that everything is working. > >>> > >>> Thanks! > >>> > >>> Mike > >>> > >>> _________________________________________________________________ > >>> Get your FREE download of MSN Explorer at > >>> http://explorer.msn.com/intl.asp > >>> > >>> > >>> _______________________________________________ > >>> Wirelessdriver-devel mailing list > >>> Wir...@li... > >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > >> > > > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at > > http://explorer.msn.com/intl.asp > > > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
|
From: Rob M. <ro...@ma...> - 2001-11-15 05:41:17
|
...and I know what needs to be done to fix that problem, too :-) That's one of the two main objectives for the next revision. The problem with sleep was that many people were seeing the powerbook go to sleep, then refusing to wake up. I've also heard from a lot of people that are finding it to be working just fine, so... ? I figured I'd error on the safe side. I'm going to have the next version make the interface temporarily unavailable and power down the card just to be on the safe side. I'll let you know when I've got stuff to test. Probably about a week or so before I get any real time to play, though. -Rob On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: > > Heh... nice how that works, eh? > > Anything else that needs testing? > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume > just fine. In fact, I can suspend, unplug my card, pack up and > go home, put my card back in, and resume and everything works > just fine. The card also appears to shutdown when the system > goes to sleep since all the link lights go dark. What is > everyone else seeing? > > Only thing I can't do is remove it and put it back in while the > system is live (documented problem :). > > Mike > >> From: Rob McKeever <ro...@ma...> >> To: "Michael Eckhoff" <mre...@ho...> >> CC: wir...@li... >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >> Date: Wed, 14 Nov 2001 21:28:05 -0800 >> >> It's always nice to see that the patches I put in without >> testing actually work :-) >> >> Thanks for the feedback! >> >> -Rob >> >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: >> >>> >>> It looks like IP Multicast is working fine. I have not spent a >>> lot of time testing, but here are my informal results: >>> >>> I was able to receive IP multicast packets with 100% success at >>> about 40pps and 300k packets. >>> I was able to receive IP multicast packets with 100% success at >>> about 13pps and 512k packets. >>> I was able to receive IP multicast packets with about 99% >>> success at about 11pps and 1024k packets. >>> >>> No duplicate packets were detected - so the stack appers to be >>> handling everything correctly. >>> The program uses a very basic serialization to ensure that >>> packet order and is maintained (on a LAN only - all bets are >>> off for WAN) and data corruption does not occur. >>> >>> I havn't looked into tuning my AP for IP multicast. it is >>> currently set to only allow 2 meg to be used for multicast. >>> When I find time, I may try to adjust these settings to see >>> what the max is that I can get. >>> >>> At any rate, it does appear that everything is working. >>> >>> Thanks! >>> >>> Mike >>> >>> _________________________________________________________________ >>> Get your FREE download of MSN Explorer at >>> http://explorer.msn.com/intl.asp >>> >>> >>> _______________________________________________ >>> Wirelessdriver-devel mailing list >>> Wir...@li... >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel >> > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > |
|
From: Michael E. <mre...@ho...> - 2001-11-15 05:34:13
|
Heh... nice how that works, eh? Anything else that needs testing? BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume just fine. In fact, I can suspend, unplug my card, pack up and go home, put my card back in, and resume and everything works just fine. The card also appears to shutdown when the system goes to sleep since all the link lights go dark. What is everyone else seeing? Only thing I can't do is remove it and put it back in while the system is live (documented problem :). Mike >From: Rob McKeever <ro...@ma...> >To: "Michael Eckhoff" <mre...@ho...> >CC: wir...@li... >Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >Date: Wed, 14 Nov 2001 21:28:05 -0800 > >It's always nice to see that the patches I put in without >testing actually work :-) > >Thanks for the feedback! > >-Rob > >On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > >> >>It looks like IP Multicast is working fine. I have not spent a >>lot of time testing, but here are my informal results: >> >>I was able to receive IP multicast packets with 100% success at >>about 40pps and 300k packets. >>I was able to receive IP multicast packets with 100% success at >>about 13pps and 512k packets. >>I was able to receive IP multicast packets with about 99% >>success at about 11pps and 1024k packets. >> >>No duplicate packets were detected - so the stack appers to be >>handling everything correctly. >>The program uses a very basic serialization to ensure that >>packet order and is maintained (on a LAN only - all bets are >>off for WAN) and data corruption does not occur. >> >>I havn't looked into tuning my AP for IP multicast. it is >>currently set to only allow 2 meg to be used for multicast. >>When I find time, I may try to adjust these settings to see >>what the max is that I can get. >> >>At any rate, it does appear that everything is working. >> >>Thanks! >> >>Mike >> >>_________________________________________________________________ >>Get your FREE download of MSN Explorer at >>http://explorer.msn.com/intl.asp >> >> >>_______________________________________________ >>Wirelessdriver-devel mailing list >>Wir...@li... >>https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
|
From: Rob M. <ro...@ma...> - 2001-11-15 05:28:05
|
It's always nice to see that the patches I put in without testing actually work :-) Thanks for the feedback! -Rob On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > > It looks like IP Multicast is working fine. I have not spent a > lot of time testing, but here are my informal results: > > I was able to receive IP multicast packets with 100% success at > about 40pps and 300k packets. > I was able to receive IP multicast packets with 100% success at > about 13pps and 512k packets. > I was able to receive IP multicast packets with about 99% > success at about 11pps and 1024k packets. > > No duplicate packets were detected - so the stack appers to be > handling everything correctly. > The program uses a very basic serialization to ensure that > packet order and is maintained (on a LAN only - all bets are > off for WAN) and data corruption does not occur. > > I havn't looked into tuning my AP for IP multicast. it is > currently set to only allow 2 meg to be used for multicast. > When I find time, I may try to adjust these settings to see > what the max is that I can get. > > At any rate, it does appear that everything is working. > > Thanks! > > Mike > > _________________________________________________________________ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |
|
From: Michael E. <mre...@ho...> - 2001-11-15 05:19:30
|
It looks like IP Multicast is working fine. I have not spent a lot of time testing, but here are my informal results: I was able to receive IP multicast packets with 100% success at about 40pps and 300k packets. I was able to receive IP multicast packets with 100% success at about 13pps and 512k packets. I was able to receive IP multicast packets with about 99% success at about 11pps and 1024k packets. No duplicate packets were detected - so the stack appers to be handling everything correctly. The program uses a very basic serialization to ensure that packet order and is maintained (on a LAN only - all bets are off for WAN) and data corruption does not occur. I havn't looked into tuning my AP for IP multicast. it is currently set to only allow 2 meg to be used for multicast. When I find time, I may try to adjust these settings to see what the max is that I can get. At any rate, it does appear that everything is working. Thanks! Mike _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
|
From: David R. <n1...@ma...> - 2001-11-15 01:07:06
|
Hello- I fixed the crashing bug when the preference pane was loaded and there was no card inserted. It is now in the current CVS. -- Dave |
|
From: Michael E. <mre...@ho...> - 2001-11-14 05:57:15
|
Hello! Just wanted to let everyone know that the Cabletron/Enterasys card is working flawlessly with the driver under 40-bit WEP mode. I need to find another 128bit card before I can test that mode as well. I also have a series of multicast test applications that I wrote a while back to test cisco router throughput. When I get into work tomorrow, I'll compile them up and test the multicast as well. My access point is a Cabletron/Enterasys RoamAbout with a 128bit encryption card in it. My keys are only set to 40bit at this time. Thanks so much for all of your hard work on this driver!! It has been a complete lifesaver. Without it, I not only wouldn't have wireless access at home, I would have given up on OS X and this powerbook alltogether! Mike _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
|
From: yuriwho <yu...@ma...> - 2001-11-13 02:04:21
|
The latest installer. Works fine for me. I tried installing the prefpane with and without additional login items and it works fine in both cases. If you subsequently click on hide for the WirelessConfig prefpane that also works properly indicating that your postflight works fine. These installers are a go for me. I'll prepare the web page for the release, removing my notes about the version in cvs and changing the WEP indication for all cards except Wavelan/ORiNOCO silver to: no* unconfirmed. Wolfgang.. Are you using a custom font size? Do you have another prefpane installed in any of the possible sites e.g. /Library/PreferencePanes, ~/Library/PreferencePanes, /System/Library/PreferencePanes? Unfortunately I don't have languages installed on my system to try and reproduce the problem. Can you post a screenshot? You can see how it looks on my system in the installation instructions on the home page. Y On Monday, November 12, 2001, at 06:20 PM, Rob McKeever wrote: > OK, I've updated the installer a bit by adding postflight scripts to > both the WirelessDriver installer (tries to remove the kext cache > record) and the WirelessPrefPane installer (tries to install the > preference pane to start at login) > > 2 things: > 1) the preference pane is being installed into > /System/Library/PreferencePanes. I'll look at changing this to > /Library/PreferencePanes > 2) When installing itself into the login items, we can't reliably > set the "Hidden" flag, so we're living it visible right now. The best > way around this is likely to be modifying the preference pane to do > this itself like the iTunes helper does. > > Modified installers available at the same places as before. Once I've > gotten confirmation that it works OK for a few people, I'll post it to > SourceForge and make announcements. > > -Rob > |
|
From: Wolfgang F. <wf...@wf...> - 2001-11-13 01:13:45
|
I downloaded and installed the driver and the configuration tool. The driver works perfectly (PB G4, SMC card, Airport, no WEP). The configuration tool does not work. It installs itself and it is found in the System Preferences app, but it is taking to much space for its name, writing into the next pref app (tinkertool). If I click on it, nothing shows up, the window of the Syst-Pref app stays clean. I check with the last version from CVS I build, which still works if I start it directly out of the CVS tree. (My system is running in German, perhaps that is part of the problem?) Wolfgang Am Montag den, 12. November 2001, um 04:50, schrieb Rob McKeever: > Alrighty! > > I've got an image with installers ready for inspection. If a couple of > you could verify this works OK, I'll tweak the ReadMe in the disk image > a bit and post it to the public. > my Mac.com homepage as: > <http://homepage.mac.com/robm/WirelessDriver_b3.sit> > > ...or something like that... > > Let me know how it works for you and if you have any suggestions. > > -Rob McKeever > ro...@ma... |
|
From: Rob M. <ro...@ma...> - 2001-11-12 03:50:43
|
Alrighty! I've got an image with installers ready for inspection. If a couple of you could verify this works OK, I'll tweak the ReadMe in the disk image a bit and post it to the public. You can find it at: My iDisk named WirelessDriver_b3.dmg.gz my Mac.com homepage as: <http://homepage.mac.com/robm/WirelessDriver_b3.sit> ...or something like that... Let me know how it works for you and if you have any suggestions. -Rob McKeever ro...@ma... |
