IP Loopback through DLPI instead of lo0

by stad.. » Fri, 02 Aug 1996 04:00:00

Hi,

Is there any way to prevent IP from short circuiting local
addresses in the IP modules. While this method is clearly
the most efficient, it would be nice to be able to perform
the loopback in either a DLPI or custom pseudo driver. This
would allow testing of link layer protocols on a single machine,
while the current approach requires two machines because the link
layer never sees packets that are addressed locally.

Thanks,
Scott

Top

1. Mapping two IP addresses onto loopback lo0 --- HOWTO?

I want to be able to map two IP addresses onto a loopback address -
the reason? To be able to achieve redundant networking between to
hosts:

I'm running Solaris 2.5.1

-------------------------------
| |
192.168.1.2 | | 192.168.1.1
------------ ------------
| | | |
lo0 | | | | lo0
----------| | | |--------
192.168.253.1 | | | | 192.168.254.1
| | | |
------------ ------------
192.168.2.2 | | 192.168.2.1
| |
-------------------------------

By associating separate network addresses with the loopback ports of
the two machines, I can then use a routing system to route traffic
between the two hosts by whichever network is open (if anybody can
suggest a better way of achieving this sort of redundancy then I'm
open to suggestions).

My questions:

1) Is it possible to map a second IP address onto lo0? My
attempts at "ifconfig lo0:1 192.168.254.1" failed dismally,
producing only a POINTTOPOINT entry.

2) If not, what are the consequences of having an address
*other* than 127.0.0.1 on lo0?

Dunstan Vavasour

2. Newbie question about Msg Ques

3. problem pinging, or with local loopback, or with lo0

4. not on console

5. why 2 lo0 (loopbacks)

6. Sympa error

7. lots off activity on de lo0 (loopback interface)

8. Building XFREE86 3.1.1 shared libs

9. Picasso and loopback configuration (lo vs. lo0).

10. broadcast on lo0 loopback interface

11. snoop(1M) on loopback lo0, Solaris???