You are not logged in.
So I'm currently running arch on two machines, a laptop and a desktop, and I noticed a few days ago that the laptop couldn't get a network connection (using wicd). I traced the issue to the version of dhcpcd I was using from the testing repo, so I went back to the stable version and it worked fine. I recently ran my updates again on the desktop and laptop, and now dhcpcd won't acquire an address on either machine, so I have to do everything manually. Anyone else having this issue, or is it just me?
Offline
Just you. Anything in the journal after a failed connection attempt? No other network services running?
Offline
Actually, just yesterday I had the new version of dhcpcd core dump on me. I had been meaning to switch to connman on that machine anyway though, and promptly forgot about the dhcpcd issue. Connman just seems to handle ipv6 beautifully, which I set up the other day. (Comcast may have terrible customer service and be something of an oligopoly with TW, but I have to say that their native dual stack is a good thing.)
Offline
was getting core dumps on the testing version, this is the journal output from trying again just now "[13722.597384] dhcpcd[16552]: segfault at 10 ip 000000000042086c sp 00007fffc7802db0 error 4 in dhcpcd[400000+30000]"
I've been running with wicd disabled for testing this, shouldn't have any other network services since these are both clean installs.
Offline
I would say report it and then have wicd switch to dhclient for now.
Offline
Yeah, me too. Out of interest, where are you getting the lease from. I ask because my laptop seems to get a lease correctly when I'm in work, however I get the same error while at home. My router is running OpenWRT. Just wondering if you happen to be running the same?
Last edited by Knasher (2014-03-12 11:58:29)
Offline
Barrier Breaker here...
BARRIER BREAKER (Bleeding Edge, r39757)
Offline
hmm, I'm running openwrt barrier breaker as well...
BARRIER BREAKER (Bleeding Edge, r39582)
but for now, dhclient is working wonders (and it's way faster), so I'll probably not be switching back when it is fixed.
Last edited by ZHoob2004 (2014-03-12 20:00:53)
Offline
I'm not sure if its the same issue but I had to roll back to dhcpcd-6.2.1-1 due to a variety of issues.
I am using wicd as well but my router runs dd wrt
Offline
Also is dhclient really that good? Because this is my boot:
gsilvers@gsgalag pkg systemd-analyze blame 22:26:05
541ms dhcpcd.service
189ms systemd-vconsole-setup.service
177ms wicd.service
That's a hot half a second of my life I'd love to get back!
Offline
Also is dhclient really that good?
I don't have any numbers, but I no longer have any wait for network connection upon login (had to wait a few seconds before). Transition from wired to wireless and back is also much faster. It makes me want to look into why it isn't the default for wicd.
Offline
It is a dhcpcd bug and probably already fixed upstream https://bugs.archlinux.org/task/39381
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
BARRIER BREAKER (Bleeding Edge, r39582)
The DHCPv6 server they ship is has a fault with reconfigure authentication which triggered a fault in dhcpcd.
Both upstreams have now been fixed.
but for now, dhclient is working wonders (and it's way faster), so I'll probably not be switching back when it is fixed.
dhclient is only faster because it doesn't do any ARP checking.
You can turn this off in dhcpcd if you know no-one else has stupidly assigned themselves the IP the DHCP client wants to give you.
See dhcpcd.conf(5) for the noarp option.
Offline
Thanks for the info Roy. Its great to have your direct feedback in these threads!
Offline