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
pgpyR1mkY1woF.pgp
Description: PGP signature
