From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: [solved] Re: replace udhcpc
Date: Sat, 10 May 2014 11:01:22 +0200 [thread overview]
Message-ID: <lkkpt3$lj0$1@ger.gmane.org> (raw)
In-Reply-To: <lkcshi$dep$1@ger.gmane.org>
Found a very simple solution to the original problem (after reading
through the busybox source code). Just add this small recipe to your
layer, and udhcpc will fork in to the background to gain the IP as soon
as the network is available:
diff --git a/recipes-core/busybox/busybox_%.bbappend
b/recipes-core/busybox/busybox_%.bbappend
new file mode 100644
index 0000000..14e4e37
--- /dev/null
+++ b/recipes-core/busybox/busybox_%.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_append := "${THISDIR}/files:"
+
+SRC_URI += "file://udhcpc-opts.cfg \
+ "
diff --git a/recipes-core/busybox/files/udhcpc-opts.cfg
b/recipes-core/busybox/files/udhcpc-opts.cfg
new file mode 100644
index 0000000..d02ba19
--- /dev/null
+++ b/recipes-core/busybox/files/udhcpc-opts.cfg
@@ -0,0 +1 @@
+CONFIG_IFUPDOWN_UDHCPC_CMD_OPTIONS="-R -b"
Am 07.05.2014 10:57, schrieb Neuer User:
> Hi
>
> I encounter a problem with the DHCP network setup during boot:
>
> System starts. During start ifup is called. ifup calls udhcpc. Network
> is, however, not yet up! udhcpc exits with failure. Then network is up.
> But, of course, no connection, because no IP address.
>
> In earlier times I used debian based system, which seem to rely on
> dhclient3. My experiences here were that dhclient remained as a deamon
> continuing trying to get a dhcp address.
>
> What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
> should that be done?
>
> Or can udhcpc be configured to remain in the background and try to get
> an IP address when network is finally up?
>
> Thanks for any help
>
> Michael
>
prev parent reply other threads:[~2014-05-10 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:57 replace udhcpc Neuer User
2014-05-07 9:27 ` Søren Holm
2014-05-08 3:54 ` Neuer User
2014-05-08 13:38 ` Joe MacDonald
2014-05-07 10:24 ` Burton, Ross
2014-05-08 3:58 ` Neuer User
2014-05-08 10:27 ` Burton, Ross
2014-05-09 10:28 ` Neuer User
2014-05-09 13:06 ` Andrea Galbusera
2014-05-09 13:21 ` Auslands-KV
2014-05-09 15:27 ` Andrea Galbusera
2014-05-09 16:51 ` Neuer User
2014-05-09 16:57 ` Neuer User
2014-05-09 18:37 ` Burton, Ross
2014-05-10 8:55 ` Neuer User
2014-05-09 15:15 ` Neuer User
2014-05-09 15:22 ` Burton, Ross
2014-05-09 15:24 ` Neuer User
2014-05-10 9:01 ` Neuer User [this message]
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='lkkpt3$lj0$1@ger.gmane.org' \
--to=auslands-kv@gmx.de \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.