Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] adding dhcpcd
Date: Fri, 01 Mar 2013 15:47:38 -0300	[thread overview]
Message-ID: <5130F7CA.6090203@zacarias.com.ar> (raw)
In-Reply-To: <1362163072.19802.25.camel@genx.eng.msli.com>

On 03/01/2013 03:37 PM, John Stile wrote:

> I have a need for an RFC2131 compliant DHCP client, which dhcpcd
> advertises to be (specifically  it needs to detect if a dhcp server
> becomes available).
> 
> I am using buildroot-2011.11.
> 
> I tried to add my own package to buildroot, to build dhcpcd, but I have
> no idea how to go about integrating into the system.
> 
> I configure static vs. dynamic via /etc/network/interfaces, but should I
> do next?  
> 
> How does the default system decide what to do with networking?
> What is the default dhcp client, and why isn't it RFC2131 compliant?

Hi.
If you're using a default buildroot skeleton without touching much then
/etc/init.d/S40network is called on system startup (from
/etc/init.d/rcS, which is invoked by init [/etc/inittab]).
S40network does an "ifup -a" (interface up, all) which is a busybox
applet/command that reads /etc/network/interfaces and does what it's
appropiate according to the configuration.
If your busybox config is default then udhcpc is built (busybox's dhcp
client) and that's what's used for DHCP.
For dhcpcd you probably don't want to use ifup nor S40network, you
probably want to run dhcpcd directly, something like "dhcpcd -b eth0" or
so. If link status messages are available it'll wait until carrier is
detected, and do the usual DHCP dance.
Regards.

  reply	other threads:[~2013-03-01 18:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 18:37 [Buildroot] adding dhcpcd John Stile
2013-03-01 18:47 ` Gustavo Zacarias [this message]
2013-03-05 16:21   ` John Stile
2013-03-05 18:47     ` Thomas Petazzoni
2013-03-06 18:01       ` John Stile
2013-03-06 18:58         ` Thomas Petazzoni
2013-03-06 19:50           ` John Stile
2013-03-06 20:05             ` Reuben Dowle
2013-03-06 20:08               ` Thomas Petazzoni
2013-03-06 20:41                 ` John Stile
2013-03-06 20:54                   ` Thomas Petazzoni
2013-03-06 21:02                     ` John Stile
2013-03-06 21:14                       ` Thomas Petazzoni
2013-03-06 21:20                         ` John Stile
2013-03-06 21:29                           ` Thomas Petazzoni
2013-03-06 22:57                             ` John Stile
2013-03-06 23:48                               ` Gilles Talis
2013-03-07  1:44                                 ` John Stile
2013-03-07  4:51                                   ` Gilles Talis
2013-03-07  7:31                                     ` John Stile
2013-03-07  8:53                                       ` Gilles Talis
2013-03-07 14:53                                         ` John Stile
2013-03-07 15:03                                           ` Thomas Petazzoni
2013-03-07 15:30                                             ` John Stile
2013-03-07 17:15                                               ` Thomas Petazzoni
2013-03-06 20:06             ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5130F7CA.6090203@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox