after upgrading to net-misc/dhcpcd-6.4.4 i lost any connection. " 2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6 Title dhcpcd >= 6.4.2 changes defaults for IPv6 Author William Hubbs <williamh@gentoo.org> Posted 2014-07-17 Revision 1 dhcpcd-6.4.2 and newer supports IPv6 stable private addresses when using IPv6 stateless address autoconfiguration (SLAAC) as described in RFC-7217 [1]. The configuration file shipped with dhcpcd activates this feature by default, because it means that a machine cannot be tracked across multiple networks since its address will no longer be based on the hardware address of the interface. I received a report in testing that IPv6 connectivity was lost due to this change [2]. If you are concerned about losing IPv6 connectivity, temporarily comment out the line in dhcpcd.conf that says "slaac private" until you can adjust to the new configuration. See the references below for why the upstream default is " this is the notes, but commenting out the section also not work. i dont get any connection Reproducible: Always Actual Results: work around: down grading to version 6.4.3 Portage 2.2.13 (python 3.3.5-final-0, default/linux/amd64/13.0/desktop, gcc-4.8.3, glibc-2.19-r1, 3.16.2-gentoo x86_64) ================================================================= System uname: Linux-3.16.2-gentoo-x86_64-Intel-R-_Core-TM-_i7-3740QM_CPU_@_2.70GHz-with-gentoo-2.2 KiB Mem: 24627196 total, 23372448 free KiB Swap: 25461756 total, 25461756 free Timestamp of tree: Wed, 17 Sep 2014 19:30:01 +0000 ld GNU ld (Gentoo 2.24 p1.4) 2.24 app-shells/bash: 4.2_p47 dev-java/java-config: 2.2.0 dev-lang/python: 2.7.8, 3.3.5-r1, 3.4.1 dev-util/cmake: 3.0.2 dev-util/pkgconfig: 0.28-r2 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.13.1 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.14.1 sys-devel/binutils: 2.24-r3 sys-devel/gcc: 4.8.3 sys-devel/gcc-config: 1.8 sys-devel/libtool: 2.4.2-r1 sys-devel/make: 4.0-r1 sys-kernel/linux-headers: 3.16 (virtual/os-headers) sys-libs/glibc: 2.19-r1 Repositories: gentoo bitcoin steam-overlay bumblebee printer-drivers lokal ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="*" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=corei7 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.6/ext-active/ /etc/php/cgi-php5.6/ext-active/ /etc/php/cli-php5.6/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-march=corei7 -O2 -pipe" DISTDIR="/mnt/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LANG="de_DE.UTF-8" LC_ALL="" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j9" PKGDIR="/mnt/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/mnt/portage"
While I can't say for sure if we're facing exactly the same problem, I can confirm that since upgrading to dhcpcd 6.4.4 on my ~x86 system, I don't get an IP assigned for my wifi connection (didn't yet try wired) during boot. However, I find this in the logs: dhcpcd[2572]: segfault at 6d8 ip 0806517f sp bfe14308 error 4 in dhcpcd[8048000+37000] Funnily, manually issuing a "dhcpcd" as root gets me an IP assigned, so that's what I currently do as a workaround.
Same issue here. Downgrading to 6.4.3 is also a quick fix.
Also getting no connection with 6.4.4, downgrading works fine. Worth noting I'm using net-misc/networkmanager-0.9.8.10-r1 as well. (There are newer versions of NM out too) Manually using dhcpcd seemed to work, but I kept getting the connection dropped after a while.
Since the reporter has not defined the problem he has found, adding me-toos isn't going to be helpful at all. Please file separate bug reports for singular issues. "no network connection" is not the bug - it's the result you're seeing and it is by no means specific enough. When you find the actual bug, please do reopen this bug report once you have added that information.
here is the log of the bug: Sep 18 09:54:20 TuX slim[1826]: (==) Using config directory: "/etc/X11/xorg.conf.d" Sep 18 09:54:20 TuX slim[1826]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Sep 18 09:54:20 TuX NetworkManager[1812]: keyfile: read connection 'Auto Ethernet' Sep 18 09:54:20 TuX NetworkManager[1812]: keyfile: parsing .keep_net-misc_networkmanager-0 ... Sep 18 09:54:20 TuX NetworkManager[1812]: Connection failed to verify: (unknown) Sep 18 09:54:20 TuX NetworkManager[1812]: keyfile: error: invalid or missing connection property '(null)/connection Sep 18 09:54:20 TuX NetworkManager[1812]: keyfile: parsing phantomschmerz ... Sep 18 09:54:20 TuX NetworkManager[1812]: keyfile: read connection 'phantomschmerz' Sep 18 09:54:20 TuX NetworkManager[1812]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or Sep 18 09:54:20 TuX NetworkManager[1812]: <info> monitoring kernel firmware directory '/lib/firmware'. Sep 18 09:54:20 TuX NetworkManager[1812]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000: Sep 18 09:54:20 TuX NetworkManager[1812]: <info> WiFi hardware radio set enabled Sep 18 09:54:20 TuX dbus[1820]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Sep 18 09:54:20 TuX dbus[1820]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org Sep 18 09:54:20 TuX NetworkManager[1812]: <info> WiFi enabled by radio killswitch; enabled by state file Sep 18 09:54:20 TuX NetworkManager[1812]: <info> WWAN enabled by radio killswitch; enabled by state file Sep 18 09:54:20 TuX NetworkManager[1812]: <info> WiMAX enabled by radio killswitch; enabled by state file Sep 18 09:54:20 TuX NetworkManager[1812]: <info> Networking is enabled by state file Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): using nl80211 for WiFi device control Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): driver supports Access Point (AP) mode Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3) Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/0 Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'manag Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): bringing up device. Sep 18 09:54:20 TuX systemd[1]: Started Network Manager. Sep 18 09:54:20 TuX systemd[1]: Starting Multi-User System. Sep 18 09:54:20 TuX systemd[1]: Reached target Multi-User System. Sep 18 09:54:20 TuX systemd[1]: Starting Graphical Interface. Sep 18 09:54:20 TuX systemd[1]: Reached target Graphical Interface. Sep 18 09:54:20 TuX systemd[1]: Starting Network. Sep 18 09:54:20 TuX systemd[1]: Reached target Network. Sep 18 09:54:20 TuX systemd[1]: Startup finished in 4.214s (kernel) + 1.445s (userspace) = 5.659s. Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): preparing device. Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): deactivating device (reason 'managed') [2] Sep 18 09:54:20 TuX dbus[1820]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplic Sep 18 09:54:20 TuX NetworkManager[1812]: <warn> failed to allocate link cache: (-26) Protocol mismatch Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): carrier is OFF Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): new Ethernet device (driver: 'r8169' ifindex: 2) Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): device state change: unmanaged -> unavailable (reason 'man Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): bringing up device. Sep 18 09:54:20 TuX kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Sep 18 09:54:20 TuX kernel: r8169 0000:04:00.2: Direct firmware load failed with error -2 Sep 18 09:54:20 TuX kernel: r8169 0000:04:00.2: Falling back to user helper Sep 18 09:54:20 TuX kernel: r8169 0000:04:00.2 enp4s0f2: unable to load firmware patch rtl_nic/rtl8411-1.fw (-12) Sep 18 09:54:20 TuX systemd[1]: Starting WPA supplicant... Sep 18 09:54:20 TuX dbus[1820]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Sep 18 09:54:20 TuX systemd[1]: Started WPA supplicant. Sep 18 09:54:20 TuX kernel: r8169 0000:04:00.2 enp4s0f2: link down Sep 18 09:54:20 TuX kernel: r8169 0000:04:00.2 enp4s0f2: link down Sep 18 09:54:20 TuX kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0f2: link is not ready Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): preparing device. Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (enp4s0f2): deactivating device (reason 'managed') [2] Sep 18 09:54:20 TuX NetworkManager[1812]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignorin Sep 18 09:54:20 TuX NetworkManager[1812]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignorin Sep 18 09:54:20 TuX NetworkManager[1812]: <info> wpa_supplicant started Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0) supports 4 scan SSIDs Sep 18 09:54:20 TuX NetworkManager[1812]: <warn> Trying to remove a non-existant call id. Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): supplicant interface state: starting -> ready Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'su Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0): supplicant interface state: ready -> disconnected Sep 18 09:54:20 TuX NetworkManager[1812]: <info> (wlp3s0) supports 4 scan SSIDs Sep 18 09:54:20 TuX slim[1826]: The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 18 09:54:20 TuX slim[1826]: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols Sep 18 09:54:20 TuX slim[1826]: > Ignoring extra symbols Sep 18 09:54:20 TuX slim[1826]: Errors from xkbcomp are not fatal to the X server Sep 18 09:54:20 TuX kernel: ACPI Error: Field [TMPB] at 282624 exceeds Buffer [ROM1] size 262144 (bits) (20140424/dsopc Sep 18 09:54:20 TuX kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP._ROM] (Node ffff88062e869ea Sep 18 09:54:20 TuX kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI r Sep 18 09:54:21 TuX kernel: cfg80211: Calling CRDA to update world regulatory domain Sep 18 09:54:21 TuX kernel: cfg80211: World regulatory domain updated: Sep 18 09:54:21 TuX kernel: cfg80211: DFS Master region: unset Sep 18 09:54:21 TuX kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_tim Sep 18 09:54:21 TuX kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A) Sep 18 09:54:21 TuX kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A) Sep 18 09:54:21 TuX kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Sep 18 09:54:21 TuX kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A) Sep 18 09:54:21 TuX kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Sep 18 09:54:21 TuX kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Sep 18 09:54:21 TuX kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Sep 18 09:54:21 TuX kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Sep 18 09:54:21 TuX slim[1826]: The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 18 09:54:21 TuX slim[1826]: > Warning: Compat map for group 2 redefined Sep 18 09:54:21 TuX slim[1826]: > Using new definition Sep 18 09:54:21 TuX slim[1826]: > Warning: Compat map for group 3 redefined Sep 18 09:54:21 TuX slim[1826]: > Using new definition Sep 18 09:54:21 TuX slim[1826]: > Warning: Compat map for group 4 redefined Sep 18 09:54:21 TuX slim[1826]: > Using new definition Sep 18 09:54:21 TuX slim[1826]: Errors from xkbcomp are not fatal to the X server Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): carrier now ON (device state 20) Sep 18 09:54:22 TuX kernel: r8169 0000:04:00.2 enp4s0f2: link up Sep 18 09:54:22 TuX kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0f2: link becomes ready Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): device state change: unavailable -> disconnected (reason ' Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Auto-activating connection 'Auto Ethernet'. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) starting connection 'Auto Ethernet' Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): device state change: disconnected -> prepare (reason 'none Sep 18 09:54:22 TuX NetworkManager[1812]: <info> NetworkManager state is now CONNECTING Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 1 of 5 (Device Prepare) scheduled... Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 1 of 5 (Device Prepare) started... Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 2 of 5 (Device Configure) scheduled... Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 1 of 5 (Device Prepare) complete. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 2 of 5 (Device Configure) starting... Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): device state change: prepare -> config (reason 'none') [40 Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 2 of 5 (Device Configure) successful. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 3 of 5 (IP Configure Start) scheduled. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 2 of 5 (Device Configure) complete. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 3 of 5 (IP Configure Start) started... Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): device state change: config -> ip-config (reason 'none') [ Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Beginning DHCPv4 transaction (timeout in 45 seco Sep 18 09:54:22 TuX NetworkManager[1812]: <info> dhcpcd started with pid 1849 Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Beginning IP6 addrconf. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 3 of 5 (IP Configure Start) complete. Sep 18 09:54:22 TuX dhcpcd[1849]: version 6.4.3 starting Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): DHCPv4 state changed nbi -> preinit Sep 18 09:54:22 TuX dhcpcd[1849]: DUID 00:01:00:01:1a:07:99:cc:00:90:f5:d9:a4:76 Sep 18 09:54:22 TuX dhcpcd[1849]: enp4s0f2: IAID f5:d9:a4:76 Sep 18 09:54:22 TuX dhcpcd[1849]: enp4s0f2: rebinding lease of 192.168.1.2 Sep 18 09:54:23 TuX bumblebeed[1816]: [ 8.550733] [ERROR]Unloading nvidia driver timed out. Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Auto-activating connection 'phantomschmerz'. Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) starting connection 'phantomschmerz' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled... Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started... Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled... Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete. Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting... Sep 18 09:54:24 TuX NetworkManager[1812]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 5 Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0/wireless): connection 'phantomschmerz' has security Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: added 'ssid' value 'phantomschmerz' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: added 'scan_ssid' value '1' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: added 'auth_alg' value 'OPEN' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: added 'psk' value '<omitted>' Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete. Sep 18 09:54:24 TuX NetworkManager[1812]: <info> Config: set interface ap_scan to 1 Sep 18 09:54:24 TuX NetworkManager[1812]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
i have it as well. running sudo dhcpcd eth0 will crash with segfault. pastebin from gdb with stacktrace: http://pastebin.com/YDdnAyZL
Sep 18 09:54:22 TuX NetworkManager[1812]: <info> dhcpcd started with pid 1849 Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Beginning IP6 addrconf. Sep 18 09:54:22 TuX NetworkManager[1812]: <info> Activation (enp4s0f2) Stage 3 of 5 (IP Configure Start) complete. Sep 18 09:54:22 TuX dhcpcd[1849]: version 6.4.3 starting Sep 18 09:54:22 TuX NetworkManager[1812]: <info> (enp4s0f2): DHCPv4 state changed nbi -> preinit Sep 18 09:54:22 TuX dhcpcd[1849]: DUID 00:01:00:01:1a:07:99:cc:00:90:f5:d9:a4:76 Sep 18 09:54:22 TuX dhcpcd[1849]: enp4s0f2: IAID f5:d9:a4:76 Sep 18 09:54:22 TuX dhcpcd[1849]: enp4s0f2: rebinding lease of 192.168.1.2 Thats' not the same version as in the Summary. All others: please file your own bug report.
(In reply to Märt Bakhoff from comment #6) > i have it as well. > running sudo dhcpcd eth0 will crash with segfault. > pastebin from gdb with stacktrace: http://pastebin.com/YDdnAyZL Fixed upstream here: http://roy.marples.name/projects/dhcpcd/ci/b46ab4d1255aed89010ab4d695fad664a55c52fc?sbs=0
This should be fixed in 6.4.5.
