Erik Mouw wrote:
> On Thu, Dec 28, 2006 at 05:07:42PM +0100, topi wrote:
>> El Thu, 28 Dec 2006 13:47:59 +0100 Erik Mouw <mouw@xxxxxxxxxxxx> ha
>> escrit:
>>> On Thu, Dec 28, 2006 at 05:37:36AM -0500, Mark Hounschell wrote:
>>>> Does/can the linux kernel (2.6.x) support multiple lo devices?
>>> Sure: ifconfig lo:1 10.0.0.138
>> sure this is correct... but, now that i've been thinking of that, i
>> have some doubts...
>>
>> are you sure that it's a second device instead of a second address on
>> same device? ('lo:1' will be seen by the kernel as a different device
>> from 'lo')
>
> Second device or second address on the same device, it doesn't matter
> because the result will be the same: packets for that adress will loop
> back to the local host.
>
>
> Erik
>
Well, I did ifconfig lo:1 128.0.0.1 and it shows up as
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1956 (1.9 Kb) TX bytes:1956 (1.9 Kb)
lo:1 Link encap:Local Loopback
inet addr:128.0.0.1 Mask:255.255.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
However when I set an app to write to lo:1 I can see the packets on lo using
ethereal. In fact with 2 applications one reading lo and the other writing lo:1,
the data written to lo:1 gets read by the reader of lo. So this is not giving me
2 seperate lo devices???
Mark
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
