| 1 |
On Tuesday 22 Dec 2015 01:12:10 Kai Krakow wrote: |
| 2 |
> Am Tue, 22 Dec 2015 00:54:35 +0000 |
| 3 |
> |
| 4 |
> schrieb Mick <michaelkintzios@×××××.com>: |
| 5 |
> > On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote: |
| 6 |
> > > On Mon, 21 Dec 2015 23:55:06 +0000, Mick wrote: |
| 7 |
> > > > > Are you trying to run ifplugd from its init script? It's not |
| 8 |
> > > > > meant to be used like that with openrc. |
| 9 |
> > > > |
| 10 |
> > > > I don't have any init scripts for ifplugd. I wondered what starts |
| 11 |
> > > > it/stops it, and found /lib64/netifrc/net/ifplugd.sh |
| 12 |
> > > |
| 13 |
> > > It should be started by the net.eth* scripts, so you need to start |
| 14 |
> > > the network interface first. |
| 15 |
> > |
| 16 |
> > Thanks again Neil. I don't think this is as you suggest. I never |
| 17 |
> > had wired or wireless interfaces enabled to start at boot time, |
| 18 |
> > because ifplugd started them up as necessary. |
| 19 |
> > |
| 20 |
> > From the README file: |
| 21 |
> > The network interface which is controlled by ifplugd should not be |
| 22 |
> > configured automatically by your distribution's network subsystem, |
| 23 |
> > since ifplugd will do this for you if needed. |
| 24 |
> |
| 25 |
> But that doesn't apply here because the "net.* plugin" starts ifplugd, |
| 26 |
> and defers further initializations until ifplugd detects a link. |
| 27 |
> |
| 28 |
> This is what I meant when I talked about pushing ifplugd further down |
| 29 |
> the layer. I just didn't remember that this is now solved by a plugin |
| 30 |
> in net.* itself. |
| 31 |
> |
| 32 |
> Don't enable ifplugd service. Openrc will do its magic. |
| 33 |
|
| 34 |
There is no means of enabling or disabling the ifplugd service that I have |
| 35 |
found, because there is no /etc/init.d/ifplugd script. Once installed ifplugd |
| 36 |
always starts at boot and daemonizes, configuring or tearing down connections |
| 37 |
as a link is detected or lost. |
| 38 |
|
| 39 |
To make it clearer, this is how it used to work on two laptops: |
| 40 |
|
| 41 |
I install ifplugd and remove from rc-update any net.<iface> that I have |
| 42 |
configured. ifplugd will always start at boot as a daemon and will bring up |
| 43 |
and configure the wired NIC once a cable is detected. There is no start up |
| 44 |
script in /etc/init.d/ installed by default, although the man page mentions |
| 45 |
it, along with /etc/ifplugd/ifplugd.conf, which is also not installed. This |
| 46 |
is the only file that installed on my systems: |
| 47 |
|
| 48 |
# find /etc -iname *ifplug* |
| 49 |
/etc/ifplugd |
| 50 |
/etc/ifplugd/ifplugd.action |
| 51 |
|
| 52 |
|
| 53 |
I started this thread because recently I have to start my wired interface |
| 54 |
manually, after which point ipfplugd also starts, daemonizes and manages the |
| 55 |
connection. This is not how it used to work - I never had to start the wired |
| 56 |
interface myself. |
| 57 |
|
| 58 |
Furthermore, starting ifplugd on a terminal now shows that it is listening on |
| 59 |
eth0 instead of enp11s0, but hadn't tried this before things broke. According |
| 60 |
to the man page eth0 is the default, but I can't recall manually specifying a |
| 61 |
different interface for ifplugd in the past. It always brought up the wired |
| 62 |
interface, no matter what it was called. |
| 63 |
|
| 64 |
-- |
| 65 |
Regards, |
| 66 |
Mick |
Archives