From: Daniel Seifert (dseifert_at_dseifert.de)
Date: 2002-06-28 08:14:04 UTC
Am Fre, 2002-06-28 um 09.44 schrieb Frank Weigel:
> had the same problem and it took me 2 days to get a clue:
> the airport software on the ibook expects you to put the password in "".
> So if your password is password you type in "password" (with the ""!)
> when Mac OS asks for it. Everything should work then.
It doesn't. OTOH, how do I enter the password anyway? When I use "iwconfig wlan0 key 01:02:03:04:05" do I enter "01:02:03:04:05" or "0102030405" (tried both without success).
Anyway, it should work without encryption as well. I start to suspect that the AirPort card is not able to send anything to the linux server. This would explain why it sees the network and its setting, but cannot connect or authenticate.
The airport card is fine, I am using it at another place with a real access point (not configured by me ;)) and it works without any problem (I do not need to put quotes around the password there, either!?) The D-Link card is untested, though, but fresh out-of-the-box.
As said previously, I haven't yet enabled bridging, only the wlan0
interface is up (ip 192.168.2.1) and the ibook's interface en1 (ip
192.168.2.2). I now set everything to ad-hoc and they seem to connect
just fine. But I still cannot ping :-(
Using tcpdump -i en1 and -i wlan0 respectively, I see that messages from the linux server reach (sometimes) the ibook (arp who-has 192.168.2.2 tell 192.168.2.1) and the ibook answers (is-at 0:30:etc) but on the linux machine arp -a shows only "(incomplete)" for 192.168.2.2. This all in ad-hoc mode (both with the Prism2 driver as well as the wlan-ng driver). The ibook's "arp -a" output is correct (it displays the correct mac address).
Does this sound like a hardware problem or a setup problem? Maybe there is some incompatibility? Again, it looks like the ibook cannot reach the D-Link card. Do I need to modify some other settings? (channel, etc?)
With kind regards,