-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alex Prinsier wrote: > How sure are you that wpa_supplicant is able to connect to your access > point? It can only do ip stuff (like acquiring an ip) once it's > connected (associated) to your ap. > > Run wpa_gui to verify.
I am very sure that it is able, since after calling dhcpcd eth1 manually I can browse the internet and do other networky type things. wpa_gui gives the status 4_WAY_HANDSHAKE until I give this command manually, and then it says ASSOCIATED. Interestingly enough, however, I frequently see Last Message as "Diconnected" for a very brief period, and then it will say "Associated with <MAC address>" Another strange thing that I have noticed is that when I try to ping my laptop from another machine, it sometimes works and sometimes does not. It seems that using the laptop to ping the other machine first helps for some reason, but that may also just be coincidence. Mick wrote: >> On Thursday 31 May 2007 12:05, Randy Barlow wrote: > [snip...] >> RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0 >> TX packets:3 errors:0 dropped:0 overruns:0 carrier:8 >> collisions:0 txqueuelen:1000 >> RX bytes:10960814 (10.4 Mb) TX bytes:393094968 (374.8 Mb) >> Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff > > I'm afraid that I can't really help either, but it is clear from the number > of > received packet errors and dropped packets received that something is amiss > big time. Having suffered similarly in the past (with different hardware) > I'd say that the problem is with the driver. I agree that something is really wrong here, and the interesting thing that I've noted is that the errors are always in RX packets and never in TX packets. I'm using the kernel provided driver for the Intel 2200. Perhaps I will try removing encryption from my network temporarily to see if that helps with the packet errors or not. This might be a good test to see if it is a driver problem or if it is an encryption problem (is the driver involved at all in the encryption, or is that done outside of the driver code?) Mick wrote: > Somebody re-emerged wpa_supplicant earlier today and fixed his problem > (second > time round) - did you try it at all? I did just try this and it didn't work, but thanks for the suggestion! Randy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGYVx17So1xaF/eR8RAs42AKCyZmmVsZh2hrpNNMS5gUm3XSR/3gCfciFN Tbx26N2bQg7epGzBaqBa2cE= =tWLq -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
