Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14425 - providing dhcpcd 3.X
Attached to Project:
Arch Linux
Opened by amir (pika) - Wednesday, 22 April 2009, 10:51 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 07 May 2009, 07:55 GMT
Opened by amir (pika) - Wednesday, 22 April 2009, 10:51 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 07 May 2009, 07:55 GMT
|
Detailsdhcpcd 4.X does not work properly on arch in some systems
places where it can be seen : 1. see 2. start the computer with the network cable unplugged and at the desktop / login screen plug in the cable. you won't get connection to the internet 3. with some routers dhcpcd won't connect on startup intermittently everything works fine in all of the above cases with dhcpcd 3.X (in point 2 if network-deamon is working you will get connected in few seconds) 4. as pointed to me by another user (i did not check) upstream dhcpcd 4.X is less configurable than 3.X i suggest holding a package dhcpcd3-3.X.X (33 KB) in the repository and arch install cd for the users who have trouble getting dhcpcd to work or need the dropped config options the dhcpcd3 package provides dhcpcd=3 and confilcts with dhcpcd (dhcpcd=4) in the install cd add option to choose dhcpcd 3 in place of dhcpcd 4. this way a case wn't happen where users cannot install dhcpcd3 with pacman cause they cannot get online with dhcpcd 4 this package can be created once and does not need maintenance/attention or (as far as i know) block upgrades of other packages. i can create and upload this package |
This task depends upon
Closed by Ronald van Haren (pressh)
Thursday, 07 May 2009, 07:55 GMT
Reason for closing: Won't implement
Additional comments about closing: You are free to add a dhcpcd3 package to AUR if you really see a fit for it. dhcpcd5 will be in the repos shortly.
Thursday, 07 May 2009, 07:55 GMT
Reason for closing: Won't implement
Additional comments about closing: You are free to add a dhcpcd3 package to AUR if you really see a fit for it. dhcpcd5 will be in the repos shortly.
1) default dhcpcd timeout is shorter than default bridge learning time
dhcpcd-5 is now a full daemon that handles DHCP for all interfaces instead of one instance per interface.
This effectively removes any timeout. There's still a timeout -> IPv4LL, but 60 seconds later DHCP is attempted again. Eventually it will come up on slow bridges.
2) I'm guessing Arch has some interaction between ifplugd/netplug/wpa_supplicant and dhcpcd which handles carrier status.
dhcpcd-4.x upwards has it's own carrier status that relies purely on kernel netlink messages.
If this doesn't work, then the kernel network interface driver is faulty.
3) You should attach a full tcpdump/wireshark trace of the DHCP transaction between dhcpcd and your faulty router.
dhcpcd-4.0.13 had a fix to drop DHCP messages without a ServerID. The ServerID is a DHCP requirement, but some routers broadcast a faulty NAK without a ServerID which could be what you describe.
If dhcpcd-4.0.13 does not fix your issue, only a trace will tell why.
4) This is the whole point of this post :)
dhcpcd-4 is infinitely more configurable than dhcpcd-3, and dhcpcd-5 moreso than dhcpcd-4.
dhcpcd-4 has a config file per interface. dhcpcd-5 has the same, but now has profiles per ssid, arping address, static and fallback.