From: Stefan Agner <stefan@agner.ch>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: Stefan Agner <stefan.agner@toradex.com>,
openembedded-core@lists.openembedded.org
Subject: Re: busybox: udhcpc: fix IPv6 support when using udhcpc
Date: Mon, 20 Jan 2020 13:57:36 +0100 [thread overview]
Message-ID: <4e98fdb7ff73df6804e58f2f4339c816@agner.ch> (raw)
In-Reply-To: <20200120123246.o5abx73ehcoqbbim@qschulz>
On 2020-01-20 13:32, Quentin Schulz wrote:
> Hi all,
>
> On Mon, Jan 13, 2020 at 03:57:31PM +0100, Quentin Schulz wrote:
>> Hi all,
>>
>> On Mon, May 14, 2018 at 04:44:15PM +0200, Stefan Agner wrote:
>> > From: Stefan Agner <stefan.agner@toradex.com>
>> >
>> > The udhcpc script calls ip addr flush .. which flushes addresses
>> > of any address family, including IPv6. However, busybox udhcpc is
>> > IPv4 only and should not influence IPv6 addressing. Hence use ip
>> > addr flush with family constrait.
>> >
>> > The script particularly broke IPv6 SLAAC: Typically when udhcpc
>> > calls the script the kernel already assigned the IPv6 link-local
>> > address. The flush removes the link-local IPv6 address again and
>> > prohibits proper IPv6 operation such as SLAAC since neighbor
>> > discovery protocol relies on IPv6 link-local addressing.
>> >
>> > Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
>> > ---
>> > meta/recipes-core/busybox/files/simple.script | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/meta/recipes-core/busybox/files/simple.script b/meta/recipes-core/busybox/files/simple.script
>> > index 6ed0293525..8b5eb53633 100644
>> > --- a/meta/recipes-core/busybox/files/simple.script
>> > +++ b/meta/recipes-core/busybox/files/simple.script
>> > @@ -28,7 +28,7 @@ case "$1" in
>> > fi
>> > if ! root_is_nfs ; then
>> > if [ $have_bin_ip -eq 1 ]; then
>> > - /SBIN_DIR/ip addr flush dev $interface
>> > + /SBIN_DIR/ip -4 addr flush dev $interface
>> > /SBIN_DIR/ip link set dev $interface up
>> > else
>> > /SBIN_DIR/ifconfig $interface 0.0.0.0
>>
>> Kindly pinging, happened to us as well many times.
>>
>
> Kindly pinging.
Just checked, we still override that script in our layer, so definitely
would be happy if this gets merged upstream so I can get rid of our
custom script downstream.
--
Stefan
next prev parent reply other threads:[~2020-01-20 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:44 [PATCH] busybox: udhcpc: fix IPv6 support when using udhcpc Stefan Agner
2019-06-24 12:24 ` Stefan Agner
2020-01-13 14:57 ` Quentin Schulz
2020-01-20 12:32 ` Quentin Schulz
2020-01-20 12:57 ` Stefan Agner [this message]
2020-01-20 19:26 ` Khem Raj
2020-01-21 9:23 ` Quentin Schulz
2020-01-21 18:08 ` Khem Raj
2020-01-22 10:06 ` Quentin Schulz
2020-06-16 9:50 ` [OE-core] " Quentin Schulz
2020-06-17 9:12 ` Stefan Agner
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=4e98fdb7ff73df6804e58f2f4339c816@agner.ch \
--to=stefan@agner.ch \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@streamunlimited.com \
--cc=stefan.agner@toradex.com \
/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