On Thu, 2006-03-23 at 08:45 -0500, Robert Love wrote: > > If I setup wifi (dynamic WEP, switching not tested with other wifi > > network) using "Connect to other ...." and get connected, n-m doesn't > > switch back to wired when I plug the wired network's cable back in > > (pulled out previously before setting up wifi). > > What does `nm-tool` say for "Carrier detection" on your network card?
eth0 (wired): Carrier Detect: yes > > Also, n-m doesn't remember the settings for the dynamic WEP network. If > > I pull out the cable, n-m tries to connect to the right wi-fi network > > (it does remeber essid :-)) but it doesn't set the network right. > > What does it think the network is? Hrm. I plugged the cable out, this is the log. It also shows that carrier detection works, doesn't it? Mar 23 15:00:09 localhost NetworkManager: <information>^ISWITCH: found better connection 'eth1' than current connection 'eth0'. Mar 23 15:00:09 localhost kernel: [4311151.553000] tg3: eth0: Link is down. Mar 23 15:00:09 localhost NetworkManager: <information>^IWill activate connection 'eth1/XXXXXX'. Mar 23 15:00:09 localhost NetworkManager: <information>^IDevice eth1 activation scheduled... Mar 23 15:00:09 localhost NetworkManager: <information>^IDeactivating device eth0. Mar 23 15:00:09 localhost dhclient: DHCPRELEASE on eth0 to 10.0.0.15 port 67 Mar 23 15:00:10 localhost avahi-daemon[4310]: Withdrawing address record for 10.0.1.124 on eth0. Mar 23 15:00:10 localhost avahi-daemon[4310]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.124. Mar 23 15:00:10 localhost avahi-daemon[4310]: iface.c: interface_mdns_mcast_join() called but no local address available. Mar 23 15:00:10 localhost avahi-daemon[4310]: Interface eth0.IPv4 no longer relevant for mDNS. Mar 23 15:00:10 localhost dhcdbd: dhclient 7737 down (9) but si_code == 0 and releasing==0 ! Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) started... Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) started... Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) scheduled... Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) complete. Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) starting... Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1/wireless): access point 'XXXXXX' is encrypted, but NO valid key exists. New key needed. Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) New wireless user key requested for network 'XXXXX'. Mar 23 15:00:10 localhost NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) complete. It looks like n-m sees that XXXXXX is WEP-protected and tries to find a key. No wonder, it fails. And the other way (from manually - via "connect to other ...." - set up wifi network to wired one): I plug the cable in and this is in my log: Mar 23 15:10:14 localhost kernel: [4311756.806000] tg3: eth0: Link is up at 100 Mbps, full duplex. Mar 23 15:10:14 localhost kernel: [4311756.806000] tg3: eth0: Flow control is on for TX and on for RX. Mar 23 15:10:14 localhost kernel: [4311756.818000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 23 15:10:25 localhost kernel: [4311767.648000] eth0: no IPv6 routers present It looks like libnl doesn't know about this change. Thanks for your effort! Regards, Pogo -- Jan Mynarik <[EMAIL PROTECTED]> ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
