From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0144D1384B4 for ; Tue, 22 Dec 2015 15:16:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5CEBE21C0EC; Tue, 22 Dec 2015 15:16:15 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0B2DD21C0E4 for ; Tue, 22 Dec 2015 15:16:14 +0000 (UTC) Received: by mail-wm0-f45.google.com with SMTP id p187so114627306wmp.0 for ; Tue, 22 Dec 2015 07:16:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=4f4A6kZpa1TlDBN4Ctk34wB+Jgv/X9fU+hNME9WM+vw=; b=CZf21cAmALWtBZZoiENrdMAbeEXC125pF3Elw+Re1VcdkQDEEHfBa33VzO7h1TbAiK S+zW3egwEt7DehmAgmi3RJWuLum6gl7zYqG46iqPsEQDK5l9b/2gtOXu7TQEVMbSB3En QZPEeA3KyIYus/pGEpWGTrKZc+86zggVq2jbPrFp/BJLw2Wlp7HceN9i3FtN8RwDakNA gPY9CQHrZ+0MGmJ4qXHYvRlmeLvFp59LqoJ49+1xPnkGLtxJqbf3yxOSSdwNjIO+TkMN /6i0Dy4R+v27BNQBbpJAwOObFvu8Wtg/CdJXOCY/PnhjEKwnYBeuOM367Y+24NZJGQMe c7gg== X-Received: by 10.28.14.78 with SMTP id 75mr29123745wmo.84.1450797372770; Tue, 22 Dec 2015 07:16:12 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id id1sm32803868wjb.19.2015.12.22.07.16.11 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 22 Dec 2015 07:16:11 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd Date: Tue, 22 Dec 2015 15:15:57 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) References: <201512201826.31348.michaelkintzios@gmail.com> <201512221404.21979.michaelkintzios@gmail.com> <20151222152026.5162b855@jupiter.sol.kaishome.de> In-Reply-To: <20151222152026.5162b855@jupiter.sol.kaishome.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2548984.vkPTpVAtKi"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201512221516.10319.michaelkintzios@gmail.com> X-Archives-Salt: 90726929-7eb5-4ff2-8445-4a915d9fd3a3 X-Archives-Hash: 04108edacb5cc2fc6ff450c9cc9b5042 --nextPart2548984.vkPTpVAtKi Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tuesday 22 Dec 2015 14:20:26 Kai Krakow wrote: > Am Tue, 22 Dec 2015 14:04:12 +0000 >=20 > schrieb Mick : > > There is no means of enabling or disabling the ifplugd service that I > > have found, because there is no /etc/init.d/ifplugd script. Once > > installed ifplugd always starts at boot and daemonizes, configuring > > or tearing down connections as a link is detected or lost. >=20 > As far as I understood, you now start ifplugd using the associated > net.* init script. Openrc will detect that ifplugd is installed and > then wait until a cable is plugged, plus starting an instance listening > on the device. No, this is not how ifplugd worked, for as long as I can remember. I never= =20 started the interface, or had to start ifplugd by an init.d script or=20 manually. > Its clear how it used to work but I think the semantics changed. Since > I do no longer use openrc I cannot confirm how the rest of the services > react to and activated net.* init script if ifplugd is active through > the plugin. I suppose dependent scripts should only be triggered after > the cable is plugged in. >=20 > This is also why there is no config file: Its configured dynamically > through the plugin and the interface specific init script. I can confirm that the config file is only used by the /etc/init.d/ifplugd= =20 script - which however does not exist on Gentoo. I created a config file, specified the enp11s0 there, started=20 /usr/sbin/ifplugd manually and it still tried to bring up the default eth0= =20 interface. Starting ifplugd manually with '-i enp11s0' works as intended. It brings u= p=20 the NIC and configures the interface: ifplugd(enp11s0)[4275]: ifplugd 0.28 initializing. ifplugd(enp11s0)[4275]: Using interface enp11s0/00:26:B9:20:B4:9C with dri= ver=20 (version: 3.137) ifplugd(enp11s0)[4275]: Using detection mode: SIOCETHTOOL ifplugd(enp11s0)[4275]: Initialization complete, link beat not detected. kernel: IPv6: ADDRCONF(NETDEV_UP): enp11s0: link is not ready kernel: tg3 0000:0b:00.0 enp11s0: Link is up at 100 Mbps, full duplex kernel: tg3 0000:0b:00.0 enp11s0: Flow control is on for TX and on for RX kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp11s0: link becomes ready ifplugd(enp11s0)[4275]: Link beat detected. ifplugd(enp11s0)[4275]: Executing '/etc/ifplugd/ifplugd.action enp11s0 up'. > > I started this thread because recently I have to start my wired > > interface manually, after which point ipfplugd also starts, > > daemonizes and manages the connection. This is not how it used to > > work - I never had to start the wired interface myself. >=20 > This is how it works now: ifplugd is started through the interface > script. I hear what you say. However, this makes me ask - what changed to cause th= is? =20 Things changed since dev-libs/libgudev-230 and sys-fs/udev-225 were install= ed. =20 <=3Dsys-fs/udev-216 and friends used to bring up ifplugd(enp11s0) without a= ny=20 intervention from me or from /etc/init.d/ scripts. So I have to guess that= =20 something changed in udev to cause this change in behaviour. Thank you for helping me walk through this. I'm going to raise a bug repor= t=20 and see what the devs think. =2D-=20 Regards, Mick --nextPart2548984.vkPTpVAtKi Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWeWk6AAoJELAdA+zwE4YeZmMIAIPJRcbeQlwOstiR47KudxJ8 U5ANRcops8SLBRv42s9Tfle3FA1OPGsxuI+DCUlWwh0GNmcbRmRpbuiTif3y41kL nMAwsLGmPwK/vbVgkzbgg71/RDndpdfuZ/ll4NFNlvUPKbqivzJFuRWr/+yoecw0 u/ovmLSvtuR6tqRYMqW1QGJg/MXwR09D1TVdeT3GJpuKLLCcxE5x+eEBpnhIyo88 /1qs6w3peW2KJXzSf3D7gLFQA733XWk3vlT7SfDWBBMDOB9CpUe6ig6gSrCS3pTo STTjrlDq2b0mRHA7qrL+C3uivGbxPy6QGqYPKgODC9Mtoez/sI4Md7ap2gSfRHM= =fx+r -----END PGP SIGNATURE----- --nextPart2548984.vkPTpVAtKi--