Something like:
# ifconfig lo:1 127.0.0.2
# ifconfig
...
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:1400 errors:0 dropped:0 overruns:0 frame:0
TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
lo:1 Link encap:Local Loopback
inet addr:127.0.0.2 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
$ ping 127.0.0.2
PING 127.0.0.2 (127.0.0.2): 56 data bytes
64 bytes from 127.0.0.2: icmp_seq=0 ttl=255 time=1.1 ms
64 bytes from 127.0.0.2: icmp_seq=1 ttl=255 time=1.2 ms
--- 127.0.0.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.1/1.1/1.2 ms
or what?
Include alias network support in the kernel in that case.
Regards,
/Karl
-----------------------------------------------------------------------
Karl Hammar Asp� Data [EMAIL PROTECTED]
Lilla Asp� 2340 +46 173 140 57 Networks
S-742 94 �sthammar +46 10 270 26 67 Computers
Sweden Consulting
-----------------------------------------------------------------------
From: [EMAIL PROTECTED] (Scott Bronson)
Subject: multiple loopback devices?
Date: Thu, 5 Apr 2001 03:44:28 -0700
> Do any of you know if Linux, specifically my Debian firewall, supports
> multiple network loopback devices?
>
> Here's why: djb's dnscache is currently listening on the firewall's
> loopback device, caching all local dns lookups. Now, I'd like dnscache
> to forward local cache misses to a tinydns process, also local.
> I'd therefore like to have tinydns listen on ANOTHER loopback device.
>
> Possible? Thanks,
>
> - Scott
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
