> > eth1 IEEE 802.11-DS ESSID:"rover" Nickname:"eric-ibook" > > Mode:Managed Frequency:2.457GHz Access Point: 44:44:44:44:44:44 > > > > Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3 > > Retry limit:4 RTS thr:off Fragment thr:off > > Encryption key:off > > Power Management:off > > Link Quality:0/92 Signal level:134/153 Noise level:134/153 > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > and nothing works (I can't ping anything). > > > > Access Point is now 44:44:44:44:44:44, which I don't explain. More > > importantly, "Link Quality" is 0/92 and "Noise level" is 134/153. I > > don't know what this exactly means but that doesn't sound good to me! > > if the access point has a bogus value (like 44:44:... or 00:00:... you had > up there), the airport card did not find it. > Not finding it means that it also does get a zero link quality > and signal/noise both in the same range.
Ok. > There might be numerous reasons for that; Most probably it's some > problem between the setup of both wireless stations. > > What kind of hardware is used for the base station? The base station we have here is a Cisco Aironet (340 or 350). > Were you able to connect there by wireless LAN using some > other hardware (eg. another laptop? or using OS X)? People using x86 laptops have succeeded in making their wireless connection work. > If possible, I suggest also booting into OS X and checking if/what > networks are visible there; that helped me quite a bit when > I set up my own environment. Oops. I forgot to mention that my wireless connection does not work either from within OS X. I got the same symptoms, i.e. a bogus access point value (44:44:...) and a base station not seeing anything. That's what made me think I may have an antenna problem. The antenna cable seems well plugged though. Thx. -- Eric
