I took the src rpm :NetworkManager-0.6.5-7.fc7.src.rpm and recompiled it using the LEAP patch NetworkManager-0.6.5-LEAP_passwd.patch developed by Jon Escombe. Nothing improved. The behavior is the same.
The first time I can configure the LEAP authentication. After reboot the LEAP authentication just hangs with the syslog messages: ------------------------------------------------------------ Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'TrinityAP'. Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) New wireless user key for network 'TrinityAP' received. Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Jul 10 10:19:37 localhost NetworkManager: <info> Activation (eth1/wireless): access point 'TrinityAP' is encrypted, but NO valid key exists. New key needed. ------------------------------------------------------------------------------ I suppose I could be just incompetent. Any further advice would be welcome. My kludge still works. -- Aaron Konstam <[EMAIL PROTECTED]> _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
