You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(38) |
Dec
(37) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(91) |
Feb
(53) |
Mar
(62) |
Apr
(53) |
May
(29) |
Jun
(57) |
Jul
(63) |
Aug
(154) |
Sep
(182) |
Oct
(154) |
Nov
(111) |
Dec
(83) |
2003 |
Jan
(77) |
Feb
(110) |
Mar
(66) |
Apr
(34) |
May
(41) |
Jun
(57) |
Jul
(47) |
Aug
(39) |
Sep
(28) |
Oct
(37) |
Nov
(27) |
Dec
(28) |
2004 |
Jan
(34) |
Feb
(12) |
Mar
(15) |
Apr
(16) |
May
(6) |
Jun
(17) |
Jul
(12) |
Aug
(14) |
Sep
(18) |
Oct
(5) |
Nov
(14) |
Dec
(19) |
2005 |
Jan
(15) |
Feb
(12) |
Mar
(1) |
Apr
(4) |
May
(16) |
Jun
(12) |
Jul
(3) |
Aug
(11) |
Sep
(2) |
Oct
(4) |
Nov
(2) |
Dec
(3) |
2006 |
Jan
(11) |
Feb
(6) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(1) |
2007 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andrew G. <gre...@ya...> - 2003-02-15 22:42:24
|
Also limited success with Lombard + Orinoco/Silver + 10.2.4 + Airport. I'm using my friends' hub and she wants to use WEP encryption. I installed, reinstalled, set up DHCP and WEP, had it fail, restarted, restarted until I got a signal and it worked! Problem: The signal is terrible. My other computer gets a strong signal if I put the same card in that, but my mac won't. Any ideas? > Hi, > > I just wanted to report that I am successfully using the current > 1.0.0b5 WirelessDriver under MacOS X 10.2.4 with an Orinoco WaveLAN > Silver PCMCIA card in my Lombard Powerbook to talk to a new Airport > Extreme Base Station. > > I foolishly bought the Orinico WaveLAN Silver card yesterday without > realizing that it's not officially supported under MacOS X. Orinoco > tech support helpfully directed me to the WirelessDriver site at > SourceForge. Unfortunately, getting it going wasn't completetly > automatic. > > The first hangup was that the installer did not successfully install > the driver, and there was no message warning me that there was a > problem. I had to untar the Archive.pax.gz file from the > WirelessDriver.pkg bundle and install the WirelessDriver.kext file in > the /System/Library/Extensions/ directory by hand. Only after doing > this (and rebooting) did a second interface ("Ethernet Adaptor (en1)") > show up in Network preferences panel. I found the hint that that might > be necessary on the list archives here somewhere, but now I can't find > the message that suggested this. Whoever you are - thanks! > > The second issue was in switching the Powerbook from a direct ethernet > connection on my LAN to a wireless connection. To connect to my LAN > directly, I had been using manual configuration, using the fixed > addresses that I have defined for my local 192.168.*.* network. The > Airport (I didn't realize at first) creates yet another local network - > by default this is 10.0.1.*. So, I had to assign the Airport base > station the 192.168.*.* address I had been using for my Powerbook, and > configure the Powerbook "Using DHCP", with the Airport Base Station's > default 10.0.1.1 address as the router address. > > I don't remember anymore exactly what sequence of restarts, etc., were > necessary to get the BaseStation recognized in the Airport Admin > Utility, but the aforementioned two items were the only non-obvious > things I believe I had to do to get things running. If anyone's > struggling with this, let me know and I'll try to help. > > A huge thanks to you guys who've provided this driver for us! If there > were a PayPal account to support this effort, I'd happily toss in $10 > or so. > > Cheers, > > Tom > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support |
From: Robert N. <ro...@el...> - 2003-02-15 16:58:22
|
I've have an 800 DVI Tibook and I'm in my friends apartment where he uses a graphite airport basestation. Anyway, I find the reception more reliable with my Orinoco Silver card and the wireless driver. I'm soon to move into the same building and sign up for cable and I'm in the market for a WAP. I'm not sure Apple airport is the best bang for the buck with many people favoring the cheaper Linksys WAPs which seem to offer better range. Anyway, how do you configure these non apple WAPs from a Powerbook? |
From: MichaelM <mic...@ha...> - 2003-02-15 12:05:24
|
I am attempting to get a D-Link DWL-650 working with WirelessDriver. After doing some research it appears that there are two version of the DWL-650. Someone please correct me or provide additional information if I am wrong. There appears to be the DWL-650 and the DWL-650 cardbus. I am assuming the DWL-650 cardbus is the newer card. It also says 2.4Ghz Wireless on the box (I don't think it says that on the old one). The card does not seem to work with Wireless Driver and the lights on the card don't even light up. Has anyone gotten this card to work? Does anyone have any additional information on this subject? Michael |
From: Tom & M. P. <mlp...@ea...> - 2003-02-15 03:14:59
|
Hi, I just wanted to report that I am successfully using the current 1.0.0b5 WirelessDriver under MacOS X 10.2.4 with an Orinoco WaveLAN Silver PCMCIA card in my Lombard Powerbook to talk to a new Airport Extreme Base Station. I foolishly bought the Orinico WaveLAN Silver card yesterday without realizing that it's not officially supported under MacOS X. Orinoco tech support helpfully directed me to the WirelessDriver site at SourceForge. Unfortunately, getting it going wasn't completetly automatic. The first hangup was that the installer did not successfully install the driver, and there was no message warning me that there was a problem. I had to untar the Archive.pax.gz file from the WirelessDriver.pkg bundle and install the WirelessDriver.kext file in the /System/Library/Extensions/ directory by hand. Only after doing this (and rebooting) did a second interface ("Ethernet Adaptor (en1)") show up in Network preferences panel. I found the hint that that might be necessary on the list archives here somewhere, but now I can't find the message that suggested this. Whoever you are - thanks! The second issue was in switching the Powerbook from a direct ethernet connection on my LAN to a wireless connection. To connect to my LAN directly, I had been using manual configuration, using the fixed addresses that I have defined for my local 192.168.*.* network. The Airport (I didn't realize at first) creates yet another local network - by default this is 10.0.1.*. So, I had to assign the Airport base station the 192.168.*.* address I had been using for my Powerbook, and configure the Powerbook "Using DHCP", with the Airport Base Station's default 10.0.1.1 address as the router address. I don't remember anymore exactly what sequence of restarts, etc., were necessary to get the BaseStation recognized in the Airport Admin Utility, but the aforementioned two items were the only non-obvious things I believe I had to do to get things running. If anyone's struggling with this, let me know and I'll try to help. A huge thanks to you guys who've provided this driver for us! If there were a PayPal account to support this effort, I'd happily toss in $10 or so. Cheers, Tom |
From: MichaelM <mic...@ha...> - 2003-02-14 08:28:29
|
This is an update to the problem I was having where my PCMCIA flash card reader would not mount on the desktop. Maybe someone having the same problem can document the solution better than me. Basically the source of the problem was an invisible file in the /Volumes directory. It was called .Unlabled (which is the same name as the smart card I was trying to read). After deleting the file .Unlabled my flash card was able to be mounted on my desktop as normal. I believe I was only able to see the file while logged in with root privileges. If someone else is having the same problem maybe they can document it a bit better. I already deleted the file so I can't provide much more information. Michael |
From: Nick S. <ns...@qu...> - 2003-02-14 05:46:43
|
I don't know if this is off-topic for this list or not. If it is, tell me and I'll go away. Apple's 3.0.3 AppleAirPort2 driver attempts to disable "Linksys compatibility," but their attempt was rather easy to defeat. The big question is whether or not they'll try and call it a DMCA violation. Jerks. Anyway, go read (and mirror) the new hack at http://www.kfu.com/~nsayer/mac/ and make your Linksys Cardbus and PCI devices work with Apple's Airport Extreme driver. |
From: Mike M. <mi...@ma...> - 2003-02-13 20:01:04
|
Actually it is fixed with a : sudo kextload /System/Library/Extensions/WirelessDriver.kext and a restart.. I think this should be done in the installer or at least have it listed in the FAQ... Just a suggestion, Thanks Mike On Thursday, February 13, 2003, at 02:05 PM, Mike Marcucio wrote: > hello all, I hope someone out there can give me a hand... > > First off here are me specs: > - Powerbook G4 > - Jaguar > - driver version 1.0.0b5 > - card = NL-2511CD Plus Ext2 (Intersil Prism 2.5 chipset) > > I run the driver installer, reboot, go into network preferences and > en2 (i already have airport) is not in the list of devices.. All I > have listed is: IrDA Modem, Internal Modem, built-In ethernet and > Airport... All of which were there before I instaled the driver.... > Please Help!!! > Thanks, > mike > |
From: Mike M. <mi...@ma...> - 2003-02-13 19:07:36
|
hello all, I hope someone out there can give me a hand... First off here are me specs: - Powerbook G4 - Jaguar - driver version 1.0.0b5 - card = NL-2511CD Plus Ext2 (Intersil Prism 2.5 chipset) I run the driver installer, reboot, go into network preferences and en2 (i already have airport) is not in the list of devices.. All I have listed is: IrDA Modem, Internal Modem, built-In ethernet and Airport... All of which were there before I instaled the driver.... Please Help!!! Thanks, mike |
From: Kevin G. <ke...@pa...> - 2003-02-13 18:58:23
|
Has anyone gotten a DWL-650 to work with a 1ghz Powerbook??? It's on the list as working, but I can't get it to light up. Lights up on an IBM thinkpad though... Card's not dead. Any success out there??? Thanks Kevin |
From: Graham O. <gra...@3c...> - 2003-02-13 18:03:20
|
I have had the 10.0.4 driver installed on my PB for some time and working perfectly =AD therein lies a truth =AD if it aint broke don=B9t try and fix it. I am running 10.1.5 on PB Ti with an Orinoco Gold Card. I decided to install an airport card but couldn=B9t when I found I had left m= y Torx drivers somewhere else so after re-installing the Sourceforge drivers = I had to re-install them. All appears fine ..... No error messages, however there is not preference pane so I cannot change to wireless network name to my own one and so cannot get online. Any suggestions please.... Thanks graham |
From: Bent S. <ber...@ho...> - 2003-02-13 11:29:51
|
Hi there everybody As you may recall I had some shut down problems a while ago. I had problems with my Orinoco-driver for my silver card running on a PB G3, system 9.1. Following the questions and answers on the list made me try The IOXperts 802.11b Driver.I tried out the demo version supplied at <http://www.ioxperts.com/80211b.html> I installed on top of all my old junk. And tried shutting down and removing the card while the machine was still live (another thing I couldn't do before. Always had to shut down to remove and change card) Both things worked with out problems, but the old orinoco driver still shows up in the toolbar and the orinoco card logo on the desktop. Are they supposed to do that when the new driver is working? Or did I do something wrong. I am looking forward to test the whole thing again when I come home I am not wireless at work (security reasons). I will buy the driver if it continues to work this well. Thank you everybody for all your help. An especially you Dave. Berit Møller _________________________________________________________________ Hold kontakten med dine venner med MSN Messenger http://messenger.msn.dk |
From: Dave K. <dav...@io...> - 2003-02-13 01:52:08
|
On Wednesday, February 12, 2003, at 10:35 AM, Loren L. wrote: > I went out and purchased a LinkSYS WPC11 Wireless card, popped > it on and it > worked right off the bat. I decided to try the RangeLAN-DS card > again, and > it too now works...go figure... Thanks for all your help! > Do you know of a Mac OS 9 driver for wireless pc cards? And, are there > add-ons to allow for a signal meter on the menu bar? Thanks! The IOXperts 802.11b Driver includes Mac OS 9 and Mac OS X versions. You can download demo versions from our website. See <http://www.ioxperts.com/80211b.html> for information on the Mac OS 9 version. Dave Koziol VP Engineering IOXperts, Inc |
From: Pradip M. <pm...@se...> - 2003-02-12 21:59:52
|
Hi. Thanks for the driver for Jaguar. I am running it on a Pizmo PB G3, OSX 10.2.3. Followed all the install instructions, rebooted, and opened the Network Pref pane as directed. The EN1 or EN2 options do not show up in the drop down menu as indicated. A small PC card icon does appear in the menu bar, with only one option available: eject card. I rebooted in OS 9.2.2 to check that the card was running okay. It picked up the Airport network just fine. So, do you have any suggestions? I need to run OSX. Thanks. Pradip Malde |
From: Loren L. <ety...@mc...> - 2003-02-12 15:35:21
|
Hi Rob, I went out and purchased a LinkSYS WPC11 Wireless card, popped it on and it worked right off the bat. I decided to try the RangeLAN-DS card again, and it too now works...go figure... Thanks for all your help! Do you know of a Mac OS 9 driver for wireless pc cards? And, are there add-ons to allow for a signal meter on the menu bar? Thanks! All the Best, Loren on 2/6/03 7:22 PM, Robert Engstr=F6m at ro...@sp... wrote: > Hello Loren, >=20 > I have no idea why it doesn't work. It should work. The only thing that > I can think of is to place the <string>pccard126,8000</string> in the > info.plist file to be in the first place before the 156,2 entry. You > should also move the WirelessDriver PPane.prefPane from > /System/Library/PreferencePanes/ to /Library/PreferencePanes/ as that > is where it should be stored. >=20 > //Rob >=20 > On torsdag, feb 6, 2003, at 04:51 Europe/Stockholm, Loren L. wrote: >=20 >> Hi Rob, >> ::chuckles:: >> When the card is inserted, it lights up exactly as it does on the PC >> laptops >> we've used it in. When in the PC laptops, neither lights blink unless >> we >> were doing something over the internet or LAN with the wireless card. >>=20 >> Thank you so much for all your assistance:). >>=20 >> Loren >>=20 >> The "textfile.txt" document is attached to the email. Here is the info >> from >> the troubleshooting script: >>=20 >> Last login: Wed Feb 5 14:31:27 on ttyp2 >> /Users/lorenl/Desktop/WirelessDriver\ beta\ >> 5.1/Utilities/Troubleshooting\ >> Info.command; exit >> Welcome to Darwin! >> [PowerBook-G3:~] lorenl% /Users/lorenl/Desktop/WirelessDriver\ beta\ >> 5.1/Utilities/Troubleshooting\ Info.command; exit >>=20 >> ### system info >>=20 >> ProductName: Mac OS X >> ProductVersion: 10.2.3 >> BuildVersion: 6G30 >> Darwin PowerBook-G3.local. 6.3 Darwin Kernel Version 6.3: Sat Dec 14 >> 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC Power >> Macintosh >> powerpc >> ppc750 >>=20 >> ### wireless driver files installed >>=20 >> drwxr-xr-x 3 root wheel 102 Feb 4 20:07 WirelessDriver.kext >> drwxr-xr-x 3 root wheel 102 Dec 14 18:23 IOPCCardFamily.kext >> ls: /Library/PreferencePanes: No such file or directory >>=20 >> ### wirelesscard info >>=20 >> | | "VersionOneInfo" =3D ("PROXIM","RangeLAN-DS/LAN PC >> CARD","") >> | | +-o pccard126,8000@0,0 <class IOPCCard16Device> >> | | "IOName" =3D "pccard126,8000" >>=20 >> ### network info >>=20 >> lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> inet 127.0.0.1 netmask 0xff000000 >> gif0: flags=3D8010<POINTOPOINT,MULTICAST> mtu 1280 >> stf0: flags=3D0<> mtu 1280 >> en0: flags=3D8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> inet6 fe80::250:e4ff:fed0:fe14%en0 prefixlen 64 scopeid 0x4 >> ether 00:50:e4:d0:fe:14 >> media: autoselect (none) status: inactive >> supported media: none autoselect 10baseT/UTP <half-duplex> >> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX >> <full-duplex> >>=20 >> ### wd command line tool status >>=20 >> /Users/lorenl/Desktop/WirelessDriver beta 5.1/Utilities/Troubleshooting >> Info.command: WirelessConfig: command not found >> logout >> [Process completed] > -- =20 > To be is to do. - Socrates > To do is to be. - Sartre > Do be do be do. - Sinatra >=20 |
From: Rob M. <ro...@ma...> - 2003-02-12 08:54:16
|
yes. This has been in the works privately for a while and will be released shortly. Much of this work was done on a sponsored basis and it seems only fair that the company paying for the updates gets the first release before it gets folded into the public code. -Rob On Tuesday, February 11, 2003, at 07:30 PM, Norm Rechtman wrote: > any chance that there will be an update or utility that will let me > easily choose from available wireless networks easily just like with > the little applets in the apple software where all I have to do is > pull down a window and look at the different choices and then pick the > one I want to connect to? > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support > -- "Quidquid latine dictum sit, altum viditur." |
From: Norm R. <no...@ma...> - 2003-02-12 03:28:26
|
any chance that there will be an update or utility that will let me easily choose from available wireless networks easily just like with the little applets in the apple software where all I have to do is pull down a window and look at the different choices and then pick the one I want to connect to? |
From: Thomas T. <to...@ta...> - 2003-02-12 02:51:40
|
I just set-up an Extreme base station network under 10.2. It's working great with all my machines but 1. I dropped a WaveLAN silver card in my PowerBook G3. After installing the latest driver about ten times - it finally recognized the card. I can see my network and the signal is strong - but I can't connect. I'm using 128 Bit WEP. I type in the password and it shows me the WEP Key to the base station just fine. But when I quit out and try to run my browser, nothing happens. I reopen WireLessConfig and it defaults back to 40 bit. Everything else is set right (TCP/IP, Ethernet etc..). It seems to not want to stay in 128 Bit mode. I also don't understand the difference between the "WirelessDriver Configuration" and the "WirelessConfig" apps. Thanks Tom |
From: Paul J. T. <pt...@ma...> - 2003-02-10 06:05:30
|
I finally got it working this evening. I was perusing Apple's Knowledge Base article on Airport Channel selection and overlap, # 58550. It occurred to me that the new 3.0 version of Airport Admin Utility has a couple different features. 1. Mode - 3 options are given. i) 802.11b Only, ii) 802.11b/g Compatible, and iii) 802.11g Only. Obviously, the choice here depends on your clients. I have 3 802.11b clients and may experiment with some 802.11g clients in the future, so I chose ii). 2. Channel - options 1-11 are provided. The default appeared to be 10. What made my Orinoco card work with the Airport Extreme base station was a channel change. As soon as I switched the channel from 10 to 1, the Orinoco client had *no* problem acquiring a DHCP supplied address from the base station. Anyone have any idea as to why this made a difference? Thanks for all the help and ideas. I knew it was only a matter of time and permutations... Paul Teeter pt...@ma... |
From: Cliff S. <cl...@st...> - 2003-02-09 03:04:40
|
I've run into a problem with linksys and other non-apple product and the airport extreem with wep. If I entered the key as ascii, non-airport drivers (and sometimes I saw it with airport drivers) will not be able to use wep. The solution I found was to enter the key in hex on the airportextreme base station. So convert your password to hex and enter it with a "$" at the front. Cheers, Cliff On Saturday, Feb 8, 2003, at 10:03 US/Pacific, Paul J. Teeter wrote: > Can someone tell me... > > Should my WallStreet Powerbook G3 running 10.2.3, using the 5.1Beta > Wireless driver, be able to talk to my new AirportExtreme base station > via an Orinoco Gold card? > > I have WEP on, am using MAC access control, am using DHCP + NAT, and > have 802.11b/g compatibility enabled. > > The Powerbook continually assigns itself a bogus DHCP address. > > I couldn't find a conclusive answer in the mailing list archives. > > Any one have any ideas? > > Let me know and thanks. > > Paul Teeter > pt...@ma... > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support |
From: Paul J. T. <pt...@ma...> - 2003-02-09 00:58:08
|
Marc - Thanks for the reply. The address is definitely of the 169.x.x.x variety....curses. I tried filling in the "DHCP Client ID (optional)" field. Unfortunately, I got the same result. Any other thoughts? Has anyone else seen similar problems with this type of setup? The Orinoco Gold + Wallstreet PB worked great with my old Airport Base Station (dual ethernet), the only difference with the new setup is the Airport Extreme base station. From time to time in the past with the old Airport Base Station, this PB would self-assign itself a 169.x.x.x address. I used to be able to disable and enable the interface to fix the problem. Such steps don't seem to make a difference now. Any help would be appreciated. Thanks. PJT On Saturday, February 8, 2003, at 01:40 PM, Marc Silverman wrote: > If the "bogus" address starts with 169 it means that it is not > connecting at > all. > > If this helps, I found that one thing I had to do to make it work (but > with > the Linksys) that might work for the Airport too: > > There must be something in the "DHCP Client ID (optional)" - put in > anything, just don't leave it blank. > > --Marc > > >> Can someone tell me... >> >> Should my WallStreet Powerbook G3 running 10.2.3, using the 5.1Beta >> Wireless driver, be able to talk to my new AirportExtreme base station >> via an Orinoco Gold card? >> >> I have WEP on, am using MAC access control, am using DHCP + NAT, and >> have 802.11b/g compatibility enabled. >> >> The Powerbook continually assigns itself a bogus DHCP address. >> >> I couldn't find a conclusive answer in the mailing list archives. >> >> Any one have any ideas? >> >> Let me know and thanks. >> >> Paul Teeter >> pt...@ma... |
From: Marc S. <ma...@si...> - 2003-02-08 22:19:34
|
I just spent an afternoon with my "Network Guru" and found that in order to make the Orinoco Gold Card work, we had to do a bunch of idiotic things (and some have to be done at logon each time.) I am not the most knowledgeable in all of this, but here are the things I had to do. Perhaps it will help others. Powerbook Bronze G3 - OS 10.2.3 Linksys BEFW1154 (4 Port & Wireless) 1. In the Lisksys Admin: In the "WEP Key Setting" we set it to "128bit" and entered our own 26 character number (make it easy, like "11122211122211122211122211" 2. In the System Preferences: In the "WirelessConfig" panel we check-marked "Use WEP Encryption; selected "with hex key"; entered our 26 character number; and selected "Key Slot 1 (default)" In the TCP/IP panel we used "Configure Using DHCP" made sure something was in the "DHCP Client ID Optional" field (I used "laptop" - just don't leave it empty.) When we hit "Apply Now" we no longer received the "169.xxx.xxx.xxx" and instead, finally, saw our actual router address! NOW, each time I boot up the Laptop, I have to go into the "WirelessConfig" panel and repeat step 2. For some reason, the entries DON'T stick... If anyone knows whether this is an OS X bug or a Beta 5_1 bug, I'd gladly report it... If this helps somebody, terrific! --Marc February 8, 2003 @ 5:17 PM |
From: Marc S. <met...@si...> - 2003-02-08 21:40:51
|
If the "bogus" address starts with 169 it means that it is not connecting at all. If this helps, I found that one thing I had to do to make it work (but with the Linksys) that might work for the Airport too: There must be something in the "DHCP Client ID (optional)" - put in anything, just don't leave it blank. --Marc February 8, 2003 @ 4:39 PM On 2/8/03 1:03 PM, Paul J. Teeter at pt...@ma... wrote: > Can someone tell me... > > Should my WallStreet Powerbook G3 running 10.2.3, using the 5.1Beta > Wireless driver, be able to talk to my new AirportExtreme base station > via an Orinoco Gold card? > > I have WEP on, am using MAC access control, am using DHCP + NAT, and > have 802.11b/g compatibility enabled. > > The Powerbook continually assigns itself a bogus DHCP address. > > I couldn't find a conclusive answer in the mailing list archives. > > Any one have any ideas? > > Let me know and thanks. > > Paul Teeter > pt...@ma... |
From: c.wilshere <ch...@un...> - 2003-02-08 20:27:50
|
I am having a similar problem to other people running my farallon skyline 11mb card. I have also tried to install it several times here is the output from the troubleshooting script Last login: Sat Feb 8 18:36:24 on console /Volumes/WirelessDriver\ beta\ 5.1/Utilities/Troubleshooting\ Info.command; exit Welcome to Darwin! [WallStreet:~] chas% /Volumes/WirelessDriver\ beta\ 5.1/Utilities/Troubleshooting\ Info.command; exit ### system info ProductName: Mac OS X ProductVersion: 10.2.3 BuildVersion: 6G30 Darwin WallStreet.local. 6.3 Darwin Kernel Version 6.3: Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC Power Macintosh powerpc ppc750 ### wireless driver files installed drwxr-xr-x 3 root wheel 102 Nov 6 06:04 IOPCCardFamily.kext ls: /Library/PreferencePanes: No such file or directory ### wirelesscard info | | | "VersionOneInfo" = ("INTERSIL","HFA384x/IEEE","Version 01.0$ | +-o pccard@13 <class IOPCIDevice> | | | "device_type" = <"pccard"> | | | "name" = <"pccard"> | | | +-o pccard156,2@0,0 <class IOPCCard16Device> | | | "IOName" = "pccard156,2" | +-o pccard@13,1 <class IOPCIDevice> | | "device_type" = <"pccard"> | | "name" = <"pccard"> ### network info lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 tunnel inet --> ether 00:50:e4:80:84:63 media: autoselect (<unknown type>) supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX <full-duplex> ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet 62.30.183.215 --> 62.30.182.2 netmask 0xff000000 ### wd command line tool status /Volumes/WirelessDriver beta 5.1/Utilities/Troubleshooting Info.command: WirelessConfig: command not found logout [Process completed] FRom Chas cha...@uk... |
From: Paul J. T. <pt...@ma...> - 2003-02-08 18:03:23
|
Can someone tell me... Should my WallStreet Powerbook G3 running 10.2.3, using the 5.1Beta Wireless driver, be able to talk to my new AirportExtreme base station via an Orinoco Gold card? I have WEP on, am using MAC access control, am using DHCP + NAT, and have 802.11b/g compatibility enabled. The Powerbook continually assigns itself a bogus DHCP address. I couldn't find a conclusive answer in the mailing list archives. Any one have any ideas? Let me know and thanks. Paul Teeter pt...@ma... |
From: Konrad G. <kon...@at...> - 2003-02-08 07:44:37
|
Someone just informed me off list that the archive contained an easier method called kextload'ing, which I had obviously not read back far enough to find. So my most important point, then, becomes that the most effective procedure known ought to be added to the FAQ to save a lot of people running into the same problem over and over again. If no mention of this software has made it into the FAQ with the distribution, it seems reasonable for a new reader/would-be user to assume it hasn't been clearly resolved. I read back far enough in the archives to find two separate and similar suggestions on how to proceed, neither of which mentioned kextload'ing. Combined with no mention in the FAQ, there are thus indications as one reads the archives backwards that nothing better is likely to be found earlier. And so the cycle will go 'round until the FAQ is updated. Anyway, the driver works great now and I appreciate the work that has gone into creating it and making it available. |