On Tue, Feb 16, 2021 at 11:51:12PM +0100, Riccardo Mottola wrote: > Hi Stefan, > > > Stefan Sperling wrote: > > Sounds like a wrong key, or the wrong type of crypto. > > Are you the AP is using WEP? Perhaps you need 'wpakey' instead of 'nwkey'? > > If the key is wrong or the crypto is wrong, would the interface still be > active and connected?
With WEP, if the key is wrong, the interface will appear connected but it will be unable to communicate. There is no setup phase in WEP. You either encrypt and decrypt packets with the correct key, or you don't. With WPA, the link should no reach 'active' state unless you are using the correct passphrase. This is because the AP and client will try to negotiate a per-client session key, and if this key cannot be obtained, the link will stay down. The interface flags will show UP, however. > I am sure the AP is using WEP: I connect to that access point with many > computer since years. > Also, I tried connectiong to another access point which has WPA, same > failure. OK, thanks for confirming. > The script proves that the network settings if applied are correct and do > work and that I do not "mistype"! Yes, since the WPA link is 'active' the key should be correct. The next step is getting a DHCP lease. If DHCP does not manage to obtain a lease, something is wrong. Perhaps this driver was broken somehow for multicast encryption or decryption. What does this command print before, and after, an attempt to connect? netstat -W ipw0 What does this command display while you are trying to connect? tcpdump -n -i ipw0 -y IEEE802_11_RADIO -D in -s 4096
