From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: only the loopback interface should provide net
Date: Tue, 7 Feb 2012 00:43:48 -0600 [thread overview]
Message-ID: <20120207064348.GA3036@linux1> (raw)
In-Reply-To: <1328570113.8348.53.camel@rook>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Hi again Alexander, another question for you.
On Mon, Feb 06, 2012 at 06:15:13PM -0500, Alexandre Rostovtsev wrote:
> 1. Services that connect to remote machines via any available network
> interface.
> 2. Services that listen to connections from remote machines on any
> available network interface, and run correctly even if no non-lo
> interfaces are up.
> 3. Services that require a specific network interface, bind to a
> specific address, or connect to a specific machine on the local subnet.
>
> Category 1 includes things like ntp-client (in the typical use case).
> Category 2 includes things like sshd (in the typical use case).
> Category 3 includes things like netmount (in the typical use case), or
> your example of sshd that's bound to a specific static IP.
>
> The proposal to provide net only from loopback may help with startup
> issues for Category 2, but would break Category 1.
How would this break category 1? I see category 1 as being
operationally similar to category 3. Here is why.
My understanding of networking is that you can't have two interfaces
with ip addresses in the same subnet on the same computer. Correct?
If that is the case, more than likely, the service you want to connect
to will be on one subnet or the other, but not both. So, again,
depending on net is eroneous because your service could start at the
wrong time, or try to connect through the wrong interface.
What do you think?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-07 6:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 21:04 [gentoo-dev] rfc: only the loopback interface should provide net William Hubbs
2012-02-06 21:36 ` 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 ` William Hubbs [this message]
2012-02-07 8:28 ` [gentoo-dev] " 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=20120207064348.GA3036@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