From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15486] New: raspberrypi3: eth0 configuration by ifplugd.action script fails since 2023.02/busybox v1.36.0
Date: Sat, 25 Mar 2023 08:08:12 +0000 [thread overview]
Message-ID: <bug-15486-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15486
Bug ID: 15486
Summary: raspberrypi3: eth0 configuration by ifplugd.action
script fails since 2023.02/busybox v1.36.0
Product: buildroot
Version: 2023.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: freemp@freenet.de
CC: buildroot@uclibc.org
Target Milestone: ---
Network interface setup via ifplugd.action script fails since 2023.02.
The script tries to configure the interface via DHCP first. If this fails it
applies some static settings.
/etc/ifplugd/ifplugd.action:
----------------------------
#!/bin/bash
if [ "$2" = 'up' ]; then
ifup -v eth0 && ping -Ieth0 -c1 -W1 google.com && exit 0
echo 'eth0 setup failed. applying static settings...'
ifconfig eth0 192.168.0.1 netmask 255.255.255.0
elif [ "$2" = 'down' ]; then
ifdown -f eth0
fi
----------------------------
/etc/network/interfaces:
------------------------
iface eth0 inet dhcp
------------------------
udhcpc runs with modified options:
CONFIG_FEATURE_UDHCPC_ARPING=n
CONFIG_IFUPDOWN_UDHCPC_CMD_OPTIONS="-R -n -O search"
Right after system startup, no network connection available yet, the network
cable is plugged in. DHCP setup actually succeeds but for some reason DNS does
not. This works smoothly in the 2022.11.x branch (busybox v1.35.0).
# journalctl -fu ifplugd
Dec 20 19:15:58 buildroot systemd[1]: Starting network cable plug detection
service...
Dec 20 19:15:58 buildroot systemd[1]: Started network cable plug detection
service.
Dec 20 19:15:58 buildroot ifplugd[203]: ifplugd 0.28 initializing.
Dec 20 19:15:58 buildroot ifplugd[203]: Using interface eth0/B8:28:EB:17:F7:B8
with driver <smsc95xx> (version: 5.10.92-v7)
Dec 20 19:15:59 buildroot ifplugd[203]: Using detection mode: SIOCETHTOOL
Dec 20 19:15:59 buildroot ifplugd[203]: Initialization complete, link beat not
detected.
Dec 20 19:16:26 buildroot ifplugd[203]: Link beat detected.
Dec 20 19:16:27 buildroot ifplugd[203]: Executing '/etc/ifplugd/ifplugd.action
eth0 up'.
Dec 20 19:16:27 buildroot ifplugd[203]: client: run-parts
/etc/network/if-pre-up.d
Dec 20 19:16:27 buildroot ifplugd[203]: client: ip link set eth0 up
Dec 20 19:16:27 buildroot ifplugd[203]: client: udhcpc -R -n -O search -p
/var/run/udhcpc.eth0.pid -i eth0
Dec 20 19:16:27 buildroot ifplugd[203]: client: udhcpc: started, v1.36.0
Dec 20 19:16:27 buildroot ifplugd[203]: client: udhcpc: broadcasting discover
Dec 20 19:16:28 buildroot ifplugd[203]: client: udhcpc: broadcasting select for
10.0.0.133, server 10.0.0.1
Dec 20 19:16:28 buildroot ifplugd[203]: client: udhcpc: lease of 10.0.0.111
obtained from 10.0.0.1, lease time 21600
Dec 20 19:16:28 buildroot ifplugd[203]: client: deleting routers
Dec 20 19:16:28 buildroot ifplugd[203]: client: adding dns 10.0.0.1
Dec 20 19:16:28 buildroot ifplugd[203]: client: run-parts /etc/network/if-up.d
Dec 20 19:16:28 buildroot ifplugd[203]: client: ping: bad address 'google.com'
Dec 20 19:16:28 buildroot ifplugd[203]: client: eth0 setup failed. applying
static settings...
Dec 20 19:16:28 buildroot ifplugd[203]: Program executed successfully.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-03-25 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 8:08 bugzilla [this message]
2023-04-01 6:55 ` [Buildroot] [Bug 15486] raspberrypi3: eth0 configuration by ifplugd.action script fails since 2023.02/busybox v1.36.0 bugzilla
2024-06-15 15:07 ` bugzilla
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=bug-15486-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox