Similar thing here, but with a difference: my network IS IPv6-Enabled. When I plug an ethernet cable, it DOES get its IPv4 configuration using DHCP and its IPv6 configuration via rtadvd:
Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit Oct 7 20:52:44 eeepc2jordi dhclient: Listening on LPF/eth1/aa:00:04:00:4b:04 Oct 7 20:52:44 eeepc2jordi dhclient: Sending on LPF/eth1/aa:00:04:00:4b:04 Oct 7 20:52:44 eeepc2jordi dhclient: Sending on Socket/fallback Oct 7 20:52:44 eeepc2jordi dhclient: DHCPREQUEST of 192.168.0.132 on eth1 to 255.255.255.255 port 67 Oct 7 20:52:44 eeepc2jordi dhclient: DHCPACK of 192.168.0.132 from 192.168.0.127 Oct 7 20:52:44 eeepc2jordi dhclient: bound to 192.168.0.132 -- renewal in 18665 seconds. Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> DHCP: device eth1 state changed preinit -> reboot Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled... Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started... Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> address 192.168.0.132 Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> prefix 24 (255.255.255.0) Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> gateway 192.168.0.127 Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> nameserver '192.168.0.127' Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> nameserver '80.58.61.250' Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> nameserver '80.58.61.254' Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> domain name 'jguillaumes.dyndns.org' Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> wins '192.168.0.127' Oct 7 20:52:44 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete. (...) Oct 7 20:52:45 eeepc2jordi avahi-daemon[1068]: Registering new address record for fe80::a800:4ff:fe00:4b04 on eth1.*. Oct 7 20:52:45 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) scheduled... Oct 7 20:52:45 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) started... Oct 7 20:52:45 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Oct 7 20:52:45 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) complete. Oct 7 20:52:45 eeepc2jordi NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Oct 7 20:52:45 eeepc2jordi avahi-daemon[1068]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.132. Oct 7 20:52:45 eeepc2jordi avahi-daemon[1068]: New relevant interface eth1.IPv4 for mDNS. Oct 7 20:52:45 eeepc2jordi avahi-daemon[1068]: Registering new address record for 192.168.0.132 on eth1.IPv4. Oct 7 20:52:47 eeepc2jordi NetworkManager: <info> (eth1): device state change: 7 -> 8 (reason 0) Oct 7 20:52:47 eeepc2jordi NetworkManager: <info> Policy set 'Ethernet a casa' (eth1) as default for routing and DNS. Oct 7 20:52:47 eeepc2jordi NetworkManager: <info> Activation (eth1) successful, device activated. In my case the problem appears when I enable the automatic option on the wireless interface (which is also IPv6 enabled). There is no problem in the pairing process, the IPv4 parameter arrive via DHCP, but then it times out getting the IPv6 config and the interface is marked as not available: Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> (wlan1): device state change: 4 -> 5 (reason 0) Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Activation (wlan1/wireless): connection 'WLAN de casa' has security, and secrets exist. No new secrets needed. Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Config: added 'ssid' value 'jgpTC' Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Config: added 'scan_ssid' value '1' Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Config: added 'psk' value '<omitted>' Oct 7 20:53:25 eeepc2jordi NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Oct 7 20:53:25 eeepc2jordi NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 2 of 5 (Device Configure) complete. Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> Config: set interface ap_scan to 1 Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> (wlan1): supplicant connection state: scanning -> disconnected Oct 7 20:53:25 eeepc2jordi NetworkManager: <info> (wlan1): supplicant connection state: disconnected -> scanning Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: CTRL-EVENT-SCAN-RESULTS Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: WPS-AP-AVAILABLE Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: Trying to associate with 00:1f:5b:89:0f:a1 (SSID='jgpTC' freq=2462 MHz) Oct 7 20:53:26 eeepc2jordi NetworkManager: <info> (wlan1): supplicant connection state: scanning -> associating Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: Associated with 00:1f:5b:89:0f:a1 Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: WPA: Key negotiation completed with 00:1f:5b:89:0f:a1 [PTK=CCMP GTK=TKIP] Oct 7 20:53:26 eeepc2jordi wpa_supplicant[1311]: CTRL-EVENT-CONNECTED - Connection to 00:1f:5b:89:0f:a1 completed (reauth) (...) Oct 7 20:53:26 eeepc2jordi dhclient: Listening on LPF/wlan1/00:25:d3:36:da:10 Oct 7 20:53:26 eeepc2jordi dhclient: Sending on LPF/wlan1/00:25:d3:36:da:10 Oct 7 20:53:26 eeepc2jordi dhclient: Sending on Socket/fallback Oct 7 20:53:30 eeepc2jordi dhclient: DHCPREQUEST of 192.168.0.4 on wlan1 to 255.255.255.255 port 67 Oct 7 20:53:30 eeepc2jordi dhclient: DHCPACK of 192.168.0.4 from 192.168.0.127 Oct 7 20:53:30 eeepc2jordi dhclient: bound to 192.168.0.4 -- renewal in 21194 seconds. Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> DHCP: device wlan1 state changed preinit -> reboot Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP4 Configure Get) scheduled... Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP4 Configure Get) started... Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> address 192.168.0.4 Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> prefix 24 (255.255.255.0) Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> gateway 192.168.0.127 Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> nameserver '192.168.0.127' Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> nameserver '80.58.61.250' Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> nameserver '80.58.61.254' Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> domain name 'jguillaumes.dyndns.org' Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> wins '192.168.0.127' Oct 7 20:53:30 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP4 Configure Get) complete. Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Device 'wlan1' IP6 addrconf timed out or failed. Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP6 Configure Timeout) scheduled... Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP6 Configure Timeout) started... Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP6 Configure Timeout) started... Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> (wlan1): device state change: 7 -> 9 (reason 5) Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) failed for access point (jgpTC) Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Marking connection 'WLAN de casa' invalid. Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) failed. Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> Activation (wlan1) Stage 4 of 5 (IP6 Configure Timeout) complete. Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> (wlan1): device state change: 9 -> 3 (reason 0) Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> (wlan1): deactivating device (reason: 0). Oct 7 20:53:37 eeepc2jordi NetworkManager: <info> (wlan1): canceled DHCP transaction, dhcp client pid 2578 The workaround is, obviously, to disable IPv6 on the wireless interface. -- IP6 automatic on non-IP6 network prevents wired interface IP4 configuration https://bugs.launchpad.net/bugs/430899 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
