From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/initscripts: S40network: wait for network interfaces to appear
Date: Mon, 26 Oct 2015 21:23:35 +0100 [thread overview]
Message-ID: <87io5tcraw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAMQcK5K7pKFBoN9N2hv4oLscew6qTWvj9RhfiCviLako0VzdRg@mail.gmail.com> (Ryan Barnett's message of "Mon, 26 Oct 2015 15:07:14 -0500")
>>>>> "Ryan" == Ryan Barnett <ryan.barnett@rockwellcollins.com> writes:
> Peter, Yann, All,
> On Fri, Oct 16, 2015 at 2:16 AM, Peter Korsgaard <peter@korsgaard.com> wrote:
> [...]
>>
>> diff --git a/package/initscripts/init.d/S40network b/package/initscripts/init.d/S40network
>> index 7b11d8b..a8d7c5d 100755
>> --- a/package/initscripts/init.d/S40network
>> +++ b/package/initscripts/init.d/S40network
>> @@ -6,8 +6,37 @@
>> # Debian ifupdown needs the /run/network lock directory
>> mkdir -p /run/network
>>
>> +# In case we have a slow-to-appear interface (e.g. eth-over-USB),
>> +# and we need to configure it, wait until it appears, but not too
>> +# long either. WAIT_DELAY is in seconds.
>> +WAIT_DELAY=15
>> +
>> +wait_for_interfaces() {
>> + IFACES=$(awk '/^auto/ { print $2 }' /etc/network/interfaces)
> This new way to handle bringing up interfaces doesn't work well if you
> have defined virtual interfaces in your /etc/network/interfaces.
> Having virtual interfaces in your /etc/network/interfaces file I
> believe is a valid use case that I think buildroot's default
> S40network should handle. The specific use case that will fail is
> outlined below:
> In the actual use case demonstrated below, the network interfaces file
> contains 2 virtual interfaces on eth3. Virtual interfaces do not get
> a unique entry in /sys/class/net. The function "wait_for_interfaces"
> added to /package/initscripts/init.d/S40network makes an assumption
> that all interfaces that may be "auto" will have a /sys/class/net
> entry. In the case of a virtual interface, the function will always
> timeout, and "ifup -a" is never called.
Ok, I suggest we do two things:
We change to awk statement to only consider interface names up to ':':
awk '/^auto/ { split($2, iface, ":"); print iface[1] }' /etc/network/interfaces
And we still continue with ifup -a even if we time out by changing the
exit 1 to a return 1 in wait_for_interfaces().
Would that work for you?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2015-10-26 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 7:16 [Buildroot] [git commit] package/initscripts: S40network: wait for network interfaces to appear Peter Korsgaard
2015-10-26 20:07 ` Ryan Barnett
2015-10-26 20:23 ` Peter Korsgaard [this message]
[not found] ` <CADZ9A7pN8Tq8NzDbnNDjjSP0Y7Edvo7TbngcFNhttO+v+ybMXg@mail.gmail.com>
2015-10-26 20:56 ` Peter Korsgaard
2015-10-26 21:04 ` Yann E. MORIN
2015-10-26 21:24 ` Ryan Barnett
2015-10-27 9:22 ` Nicolas Cavallari
2015-10-27 22:39 ` Arnout Vandecappelle
2015-10-27 22:46 ` Peter Korsgaard
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=87io5tcraw.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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