All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: confused by netbase/udev
Date: Tue, 09 Feb 2010 16:38:04 +0100	[thread overview]
Message-ID: <4B71815C.6050208@dresearch.de> (raw)
In-Reply-To: <20100209132913.GC24852@ibawizard.net>

Petr Štetiar wrote:
> man 5 interfaces?
> 
> Quote:
> 
> " lines beginning with the word "auto" are used to identify the physical
> interfaces to be brought up when ifup is run with  the  -a  option.   (This
> option  is  used  by  the  system  boot scripts.)  Physical interface names
> should follow the word "auto" on the same line.  There can be multiple "auto"
> stanzas.  ifup brings the named interfaces up in the order listed.  "

OK, i try to solve one problem after the other. Let's accept that
every new USB-NIC gets a new name for now (using a pool of interface names).

I've tried to create a /etc/network/interfaces which fits my wishes:

------------->snip<----------------
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# the loopback interface
auto lo
iface lo inet loopback

# interfaces to bring up at boot time
auto eth0

# the onboard NIC
iface eth0 inet dhcp

# interfaces to bring up when hotplugging
allow-hotplug eth1 eth2 eth3 eth4 eth5 eth6 eth7 eth8

# additional USB-NIC's
iface eth1 inet dhcp
iface eth2 inet dhcp
iface eth3 inet dhcp
iface eth4 inet dhcp
iface eth5 inet dhcp
iface eth6 inet dhcp
iface eth7 inet dhcp
iface eth8 inet dhcp
------------->snip<----------------

This works fine when hotplugging, but the USB-NIC is not recognised
when connected while booting up. :(

I tried to change the one line responsible for that to

  auto eth0 eth1 eth2 eth3 eth4 eth5 eth6 eth7 eth8

This works better but leads to dirty errors messages while booting
and shutdown for disconnected interfaces:

boot:
eth1: unknown interface: No such device
eth2: unknown interface: No such device
eth3: unknown interface: No such device
eth4: unknown interface: No such device
eth5: unknown interface: No such device
eth6: unknown interface: No such device
eth7: unknown interface: No such device
eth8: unknown interface: No such device

shutdown:
Deconfiguring network interfaces... cat: /var/run/udhcpc.eth0.pid: No such file or directory
cat: /var/run/udhcpc.eth1.pid: No such file or directory
eth1: unknown interface: No such device
cat: /var/run/udhcpc.eth2.pid: No such file or directory
eth2: unknown interface: No such device
cat: /var/run/udhcpc.eth3.pid: No such file or directory
eth3: unknown interface: No such device
cat: /var/run/udhcpc.eth4.pid: No such file or directory
eth4: unknown interface: No such device
cat: /var/run/udhcpc.eth5.pid: No such file or directory
eth5: unknown interface: No such device
cat: /var/run/udhcpc.eth6.pid: No such file or directory
eth6: unknown interface: No such device
cat: /var/run/udhcpc.eth7.pid: No such file or directory
eth7: unknown interface: No such device
cat: /var/run/udhcpc.eth8.pid: No such file or directory
eth8: unknown interface: No such device
done.

I'm not really happy with that. :(

Steffen




  parent reply	other threads:[~2010-02-09 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 11:23 confused by netbase/udev Steffen Sledz
2010-02-09 11:59 ` Paul Menzel
2010-02-09 13:18   ` Steffen Sledz
2010-02-09 13:29     ` Petr Štetiar
2010-02-09 13:38       ` Steffen Sledz
2010-02-09 13:47         ` Petr Štetiar
2010-02-09 15:38       ` Steffen Sledz [this message]
2010-02-09 22:58         ` Paul Menzel
2010-02-09 21:14 ` Cliff Brake
2010-02-10  7:43   ` Steffen Sledz

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=4B71815C.6050208@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.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.