| 1 |
Hi again Alexander, another question for you. |
| 2 |
|
| 3 |
On Mon, Feb 06, 2012 at 06:15:13PM -0500, Alexandre Rostovtsev wrote: |
| 4 |
> 1. Services that connect to remote machines via any available network |
| 5 |
> interface. |
| 6 |
> 2. Services that listen to connections from remote machines on any |
| 7 |
> available network interface, and run correctly even if no non-lo |
| 8 |
> interfaces are up. |
| 9 |
> 3. Services that require a specific network interface, bind to a |
| 10 |
> specific address, or connect to a specific machine on the local subnet. |
| 11 |
> |
| 12 |
> Category 1 includes things like ntp-client (in the typical use case). |
| 13 |
> Category 2 includes things like sshd (in the typical use case). |
| 14 |
> Category 3 includes things like netmount (in the typical use case), or |
| 15 |
> your example of sshd that's bound to a specific static IP. |
| 16 |
> |
| 17 |
> The proposal to provide net only from loopback may help with startup |
| 18 |
> issues for Category 2, but would break Category 1. |
| 19 |
|
| 20 |
How would this break category 1? I see category 1 as being |
| 21 |
operationally similar to category 3. Here is why. |
| 22 |
|
| 23 |
My understanding of networking is that you can't have two interfaces |
| 24 |
with ip addresses in the same subnet on the same computer. Correct? |
| 25 |
|
| 26 |
If that is the case, more than likely, the service you want to connect |
| 27 |
to will be on one subnet or the other, but not both. So, again, |
| 28 |
depending on net is eroneous because your service could start at the |
| 29 |
wrong time, or try to connect through the wrong interface. |
| 30 |
|
| 31 |
What do you think? |
| 32 |
|
| 33 |
William |
Archives