Problems with dhcpcd 5.5.4?

revellion · 2012-02-10 07:04:22

Anyone else getting segfaults in dmesg with the latest dhcpcd 5.5.4 ?.

It results in loss of connectivity in the hosts i run.

Reverting to the older version in core solves the problem.

erdk · 2012-02-14 11:15:27

When connectiong first time it's ok, but later (probably when renewing lease) dhcpd staring consuming lots of cpu time and network connectivity is lost, also logs 'received SIGPIPE' to syslog.

UJ-x51 · 2012-02-15 17:08:35

I have the same problem and like revellion, I solved it by downgrading dhcpcd 5.5.4 to 5.2.12-4. Is anyone aware of a better solution?

LongHairedHacker · 2012-02-16 12:08:24

Moin

Encountered the same problem today.

After upgarding to dhcpcd 5.5.4 I was unable to connect to eduroam networks.
While poking around in dhcpcd and wicd, I found segfaults in my dmesg output.

Came here via google.
A downgrade to 5.2.12-4 seems to have solved the probelm. (As a matter of fact im posting this from the affected system.)

Greetings
Sebastian

Avant-texte · 2012-02-16 23:45:12

Are you sure the bug is with DHCPCD? Logs? Are you talking about DHCPCD running over a wireless NIC? What chipset/driver are you using?

A lot of people have been having some trouble as of late. I believe something was broken upstream and there's now a driver issue for a number of people. For instance, ath9k and rt2800pci users have been experiencing an array of problems.

Ex:
I use rt2800pci and have been having some big connectivity issues. Thankfully, they've gotting better since today's updates, but I'm still having trouble and had to manually double-reload my driver a few times today.

Last edited by Avant-texte (2012-02-16 23:46:51)

UJ-x51 · 2012-02-17 01:56:19

I'm a bit of a noob so I can't say for sure, but what I can tell you is when I upgraded to dhcpcd-5.5.4, wireless stopped working. I downgraded it to dhcpcd-5.2.12 and it works just fine. I repeated that process today with the same results. Any insight/advice you can provide would be appreciated.

falconindy · 2012-02-17 02:34:23

Anyone care to actually report this on the bug tracker rather than just downgrade and ignore it?

UJ-x51 · 2012-02-17 03:24:26

Bug report submitted just now.

Avant-texte · 2012-02-17 06:29:54

UJ-x51 wrote:

I'm a bit of a noob so I can't say for sure, but what I can tell you is when I upgraded to dhcpcd-5.5.4, wireless stopped working. I downgraded it to dhcpcd-5.2.12 and it works just fine. I repeated that process today with the same results. Any insight/advice you can provide would be appreciated.

Your hardware & logs are good things to look at if you want to troubleshoot.

UJ-x51 wrote:

Bug report submitted just now.

Great.

UJ-x51 · 2012-02-18 01:34:49

After looking at the logs, the problem appears to be something related to IPv6 (see below). I'm using wicd as my network manager and never had any problems before this. I suspect there is a configuration change I need to make somewhere but am not sure where.

Logs with dhcpcd-5.5.4, using wicd to attempt a wireless connection:

Feb 17 09:22:48 localhost dhcpcd[1568]: version 5.5.4 starting
Feb 17 09:22:48 localhost dhcpcd[1568]: wlan0: sending IPv6 Router Solicitation
Feb 17 09:22:48 localhost dhcpcd[1568]: wlan0: sendmsg: Cannot assign requested address
Feb 17 09:22:48 localhost dhcpcd[1568]: wlan0: broadcasting for a lease
Feb 17 09:22:48 localhost dhcpcd[1568]: received RA for unexpected interface from fe80::c2c1:c0ff:fe0a:fa78
Feb 17 09:22:48 localhost dhcpcd[1568]: wlan0: Router Advertisement from fe80::c2c1:c0ff:fe0a:fa78
Feb 17 09:22:48 localhost dhcpcd[1568]: forked to background, child pid 1586
Feb 17 09:22:48 localhost dhcpcd[1590]: sending signal 1 to pid 1586
Feb 17 09:22:48 localhost dhcpcd[1590]: waiting for pid 1586 to exit
Feb 17 09:22:48 localhost dhcpcd[1586]: received SIGHUP, releasing
Feb 17 09:22:48 localhost dhcpcd[1586]: wlan0: removing interface
Feb 17 09:22:48 localhost kernel: [ 297.724514] wlan0: deauthenticating from c0:c1:c0:0a:fa:7b by local choice (reason=3)
Feb 17 09:22:48 localhost kernel: [ 297.783957] cfg80211: Calling CRDA to update world regulatory domain
Feb 17 09:22:49 localhost kernel: [ 297.846453] iwlwifi 0000:12:00.0: L1 Disabled; Enabling L0S
Feb 17 09:22:49 localhost kernel: [ 297.846597] iwlwifi 0000:12:00.0: Radio type=0x1-0x2-0x0
Feb 17 09:22:49 localhost kernel: [ 297.971128] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 17 09:22:49 localhost dhcpcd[1606]: dhcpcd not running
Feb 17 09:22:49 localhost kernel: [ 298.025806] r8169 0000:13:00.0: eth0: link down
Feb 17 09:22:49 localhost kernel: [ 298.025812] r8169 0000:13:00.0: eth0: link down
Feb 17 09:22:49 localhost kernel: [ 298.026436] ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 17 09:22:50 localhost kernel: [ 299.620856] r8169 0000:13:00.0: eth0: link up
Feb 17 09:22:50 localhost kernel: [ 299.621495] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

skunktrader · 2012-02-18 01:38:08

UJ-x51 wrote:

After looking at the logs, the problem appears to be something related to IPv6 (see below). I'm using wicd as my network manager and never had any problems before this. I suspect there is a configuration change I need to make somewhere but am not sure where.

Try disabling ipv6 https://wiki.archlinux.org/index.php/Disabling_IPv6

UJ-x51 · 2012-02-18 02:07:28

Thanks skunktrader! I added the line "net.ipv6.conf.all.disable_ipv6 = 1" to my /etc/sysctl.conf file and eveything is working fine. I guess my only remaining question is, why is this an issue now? Prior to the upgrade to dhcpcd-5.5.4, I never had this problem. Just curious I guess.

skunktrader · 2012-02-18 02:30:41

Probably because IPv6 support is built in the kernel starting from 3.2.6-2

ryooichi · 2012-03-01 15:20:20

As mentioned at http://roy.marples.name/projects/dhcpcd … #comment:2, I added "noipv6rs" to my /etc/dhcpcd.conf and that fixed my not getting an address.

LadFromWales · 2012-03-07 13:51:09

I have an issue with dhcpcd 5.5.4 also, related to IPv6, but I actually have IPv6!
dhcpcd forks to background as soon as it receives a router advertisement (pretty much instantly), which in turn causes two daemons that run soon after 'network', which are 'samba' and 'minidlna' to fail to work properly.
dhcpcd 5.2.12 forks to background after it has obtained an IPv4 from the DHCP server, which allows 'samba' and 'minidlna' to start correctly.

Samba starts fine but is inaccessible as it didn't have an IPv4 interface to bind to at the time it started. A restart of Samba fixes this.
Minidlna fails to start, stating that the selected device isn't available. Starting Minidlna again fixes this.

I have downgraded to 5.2.12 for now, but also tested adding a sleep before Samba starts, which is hit or miss as sometimes obtaining an IP from DHCP takes longer than it should, leaving me back where I started!

Leonid.I · 2012-03-07 15:26:47

dhcpcd 5.5.4 is fine here with ipv4 and completely disabled ipv6 (ipv6.disable=1 in the bot line). However, changing this to ipv6.disable_ipv6=1 renders my connection very unstable even though no ipv6 adress is actually assigned to any interface.

Arch Linux

#1 2012-02-10 07:04:22

Problems with dhcpcd 5.5.4?

#2 2012-02-14 11:15:27

Re: Problems with dhcpcd 5.5.4?

#3 2012-02-15 17:08:35

Re: Problems with dhcpcd 5.5.4?

#4 2012-02-16 12:08:24

Re: Problems with dhcpcd 5.5.4?

#5 2012-02-16 23:45:12

Re: Problems with dhcpcd 5.5.4?

#6 2012-02-17 01:56:19

Re: Problems with dhcpcd 5.5.4?

#7 2012-02-17 02:34:23

Re: Problems with dhcpcd 5.5.4?

#8 2012-02-17 03:24:26

Re: Problems with dhcpcd 5.5.4?

#9 2012-02-17 06:29:54

Re: Problems with dhcpcd 5.5.4?

#10 2012-02-18 01:34:49

Re: Problems with dhcpcd 5.5.4?

#11 2012-02-18 01:38:08

Re: Problems with dhcpcd 5.5.4?

#12 2012-02-18 02:07:28

Re: Problems with dhcpcd 5.5.4?

#13 2012-02-18 02:30:41

Re: Problems with dhcpcd 5.5.4?

#14 2012-03-01 15:20:20

Re: Problems with dhcpcd 5.5.4?

#15 2012-03-07 13:51:09

Re: Problems with dhcpcd 5.5.4?

#16 2012-03-07 15:26:47

Re: Problems with dhcpcd 5.5.4?

Board footer