public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] rfc: only the loopback interface should provide net
Date: Mon, 6 Feb 2012 15:04:51 -0600	[thread overview]
Message-ID: <20120206210451.GA1940@linux1> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]

All,

I've been pondering for a while why All of OpenRC's network interfaces
provide net.

My understanding of the "net" service is that it is there to signal that
a generic network connection is active.

What I would like to do in OpenRC is change the network scripts so that
only the loopback interface provides net.

The down side of this approach will be that if a daemon uses a specific
ip address in its configuration, or if it binds to a specific address,
the user will have to set up the appropriate configuration options in
/etc/conf.d. For example, if I setup sshd to use 192.168.10.1 and eth0 has
this address, I have to put the following line in /etc/conf.d/sshd:

rc_need="net.eth0"

One advantage I see of this approach is it will provide a fix for bugs like
http://bugs.gentoo.org/show_bug.cgi?id=228973 by requiring users to
configure services like this to start after the interface they use
is started.

Attached to this message you will find the patch I want to apply to
OpenRC to make this change.

Any thoughts, comments, or suggestions would be helpful.

William


[-- Attachment #1.2: 0001-Only-the-loopback-interface-should-provide-net.patch --]
[-- Type: text/plain, Size: 683 bytes --]

From cf57aa084dfa3020c9f0ae1f3a07e2fbf2e588dc Mon Sep 17 00:00:00 2001
From: William Hubbs <williamh@gentoo.org>
Date: Mon, 6 Feb 2012 09:24:52 -0600
Subject: [PATCH] Only the loopback interface should provide net

---
 init.d/net.lo.in |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/init.d/net.lo.in b/init.d/net.lo.in
index bf2d848..b3d2b1a 100644
--- a/init.d/net.lo.in
+++ b/init.d/net.lo.in
@@ -20,11 +20,10 @@ depend()
 
 	need localmount
 	after bootmisc
-	provide net
 	keyword -jail -prefix -vserver
 
 	case "${IFACE}" in
-		lo|lo0);;
+		lo|lo0) provide net;;
 		*) after net.lo net.lo0 dbus;;
 	esac
 
-- 
1.7.3.4


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2012-02-06 21:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 21:04 William Hubbs [this message]
2012-02-06 21:36 ` [gentoo-dev] rfc: only the loopback interface should provide net Zac Medico
2012-02-06 23:15 ` Alexandre Rostovtsev
2012-02-07  1:41   ` William Hubbs
2012-02-07  2:33     ` Alexandre Rostovtsev
2012-02-07  3:21       ` [gentoo-dev] " Duncan
2012-02-07  6:43   ` [gentoo-dev] " William Hubbs
2012-02-07  8:28     ` Alexandre Rostovtsev
2012-02-07 14:39       ` Ian Stakenvicius
2012-02-07 16:44         ` William Hubbs
2012-02-07 16:58           ` Alec Warner
2012-02-07 16:46         ` [gentoo-dev] " Duncan
2012-02-07 17:12           ` Ian Stakenvicius
2012-02-07 17:33           ` William Hubbs
2012-02-07 18:31             ` Alexandre Rostovtsev
2012-02-22 21:19   ` [gentoo-dev] " William Hubbs

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=20120206210451.GA1940@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@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