Usinage loopback addresses

Any reason not to use multiple loopback addresses, like 127.0.1.1 and
such? I'm doing some interesting port forwarding, and need to have the
application use different IPs to satisfy it's host-key vs. IP checking.
I can have multiple copies listening on separate ports, so connections
will appear to go to multiple machines if the port also changes.

127.0.1.1:6800 - one copy of app, host key #1
127.0.1.2:6801 - different copy of app, host key #2

This seems to work, I just don't want to find out later there is some
"feature" lurking in the weeds.

--
bill davidsen <(E-Mail Removed)>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979

On Mon, 08 Dec 2003 23:26:01 -0500, Bill Davidsen <(E-Mail Removed)> wrote:
> Any reason not to use multiple loopback addresses, like 127.0.1.1 and
> such? I'm doing some interesting port forwarding, and need to have the
> application use different IPs to satisfy it's host-key vs. IP checking.
> I can have multiple copies listening on separate ports, so connections
> will appear to go to multiple machines if the port also changes.
>
> 127.0.1.1:6800 - one copy of app, host key #1
> 127.0.1.2:6801 - different copy of app, host key #2
>
> This seems to work, I just don't want to find out later there is some
> "feature" lurking in the weeds.

If it is just for local use, you are free to use any loopback IP between,
but not including 127.0.0.0 and 127.255.255.255. Note that since its
netmask is 255.0.0.0, you are perfectly free to use IPs within that range
like 127.0.0.255 or 127.0.255.0, etc. Of course loopback IPs are not
directly accessible from outside of that box.

--
David Efflandt - All spam ignored http://www.de-srv.com/