On 9/27/07, Ralf Ertzinger <fedora@xxxxxxxxxxxxxx> wrote: > Hi. > > On Fri, 28 Sep 2007 00:28:06 -0400, Dan Williams wrote: > > > > That NM only accepts hex keys is going to be a big problem for me, > > > too, as my WPA2 AP only even lets me set a passphrase. > > > > /usr/sbin/wpa_passphrase <ssid> <passphrase> > > That's nice, but no solutionn. > I can verify that with latest NM and 'wpa_passphrase' I can connect once to my WPA AP. On second attempt, I get: Sep 28 07:13:41 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2 Sep 28 07:13:41 localhost kernel: iwl3945: Microcode SW error detected. Restarting 0x82000008. Sep 28 07:13:41 localhost kernel: iwl3945: Error Reply type 0x00000000 cmd REPLY_SCAN_CMD (0x80) seq 0x44A7 ser 0x00000000 Sep 28 07:13:42 localhost kernel: iwl3945: Can't stop Rx DMA. Sep 28 07:13:43 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0 Sep 28 07:13:43 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2 Sep 28 07:13:51 localhost ntpd[3533]: sendto(193.224.70.42) (fd=21): Invalid argument Sep 28 07:14:03 localhost ntpd[3533]: sendto(194.88.2.88) (fd=21): Invalid argument Sep 28 07:14:06 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long, asking for new key. Sep 28 07:14:06 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0 Progress! This issue known? tom -- Tom London -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
