From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Networking broke after update: We only hotplug for ethernet interfaces
Date: Tue, 14 Oct 2008 15:47:07 +0200 [thread overview]
Message-ID: <200810141547.07387.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <gd26pk$r8k$1@ger.gmane.org>
On Tuesday 14 October 2008 15:28:20 Grant Edwards wrote:
> My last "emerge -auvND world" appears to have broken the
> networking setup on my machine.
>
> I use tun/tap networking in order to allow Qemu virtual
> machines to show up on the network, so my /etc/conf.d/net looks
> like this:
>
> bridge_br0="eth0"
>
> config_br0=( "dhcp" )
> dhcpcd_br0=( "-L" )
> config_eth0=( "null" )
>
> # To be able to access internet on current machine
> depend_br0() {
> need net.eth0
> }
>
> That has worked fine for ages, but now when my system starts up
> it says:
>
> rc.scripts: rc-scripts: We only hotplug for ethernet interfaces.
>
> And then the br0 interface is disabled (leaving the machine
> disconnected from the network).
>
> Is hotplug now broken so that it can't be used the way it used
> to?
from 'cat /etc/rc.conf'
# Some people want a finer grain over hotplug/coldplug. rc_plug_services is a
# list of services that are matched in order, either allowing or not. By
# default we allow services through as rc_coldplug/rc_hotplug has to be YES
# anyway.
# Example - rc_plug_services="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
rc_plug_services=""
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2008-10-14 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:28 [gentoo-user] Networking broke after update: We only hotplug for ethernet interfaces Grant Edwards
2008-10-14 13:47 ` Alan McKinnon [this message]
2008-10-14 13:59 ` [gentoo-user] " Grant Edwards
2008-10-14 14:13 ` Alan McKinnon
2008-10-14 14:27 ` Grant Edwards
2008-10-14 14:37 ` Daniel da Veiga
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=200810141547.07387.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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