© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5c6b958
demo site
(Get the code!)
Hi
I'm the dhcpcd author and I'd like to take a moment to discuss how dhcpcd works, and how wicd should interact with it.
dhcpcd is designed to listen to kernel interace events (carrier, interface added, removed, etc) and auto configure that interface as best it can with rules set via dhcpcd.conf(5). As such, it is best run as a single process instead of per interface. wicd could start if it's not running.
Then wicd could listen to dhcpcd generated events via dhcpcd-run-hooks(8) to work out if an interface is configured for DHCP, IPv4LL, RA or any combination of. This is important as dhcpcd is currently dual stack - ipv4 and ipv6. The next major version will add dhcpv6 to the ipv6 stack.
> It appears that the dhcpcd devels don't care about this problem--they have
> this immature idea that as soon as we start using ipv6,
> ipv4 will magically go away.
This is untrue. Once it's configured one protocol, it will attempt to configure the other in the background. We fork once one interface has been configured for one protocol. We don't really care which protocol as modern day applications should support ipv6 anyway.