eth0:1 and nmap?

I'm trying to troubleshoot a network, and ifconfig gave me a response
I've never seen:


eth0 Link encap:Ethernet HWaddr 00:01:03:34:6C:B4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34648 errors:0 dropped:0 overruns:1 frame:0
TX packets:21424 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3085669 (2.9 Mb) TX bytes:3113240 (2.9 Mb)
Interrupt:10 Base address:0xec00

eth0:1 Link encap:Ethernet HWaddr 00:01:03:34:6C:B4
inet addr:192.168.238.60 Bcast:192.168.238.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34648 errors:0 dropped:0 overruns:1 frame:0
TX packets:21426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3085669 (2.9 Mb) TX bytes:3113572 (2.9 Mb)
Interrupt:10 Base address:0xec00


1) What does eth0:1 mean? Could it be ip aliasing? I'm running RH9 - a
stock kernel I believe, which I don't think has ip aliasing support
because its deprecated, but I'm not sure.

2) How can I fix nmap in this case:
/usr/local> nmap -p 389 192.168.238.61

Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Failed to lookup device subnet/netmask: eth0: no IPv4 address assigned
QUITTING!

/usr/local> nmap -e eth0:1 -p 389 192.168.238.61

Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
I cannot figure out what source address to use for device eth0:1, does
it even exist?
QUITTING!

Any ideas?
iksrazal

Hi,

> I'm trying to troubleshoot a network, and ifconfig gave me a response
> I've never seen:
>
> eth0 Link encap:Ethernet HWaddr 00:01:03:34:6C:B4
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:34648 errors:0 dropped:0 overruns:1 frame:0
> TX packets:21424 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:3085669 (2.9 Mb) TX bytes:3113240 (2.9 Mb)
> Interrupt:10 Base address:0xec00
>
> eth0:1 Link encap:Ethernet HWaddr 00:01:03:34:6C:B4
> inet addr:192.168.238.60 Bcast:192.168.238.255
>
>
> 1) What does eth0:1 mean? Could it be ip aliasing? I'm running RH9 - a
> stock kernel I believe, which I don't think has ip aliasing support
> because its deprecated, but I'm not sure.

I think I've seen this in context of VLAN or bridge devices.
But maybe I'm mistaken...

Regards,
Andreas

--

Dipl.-Biol. Andreas Wilm
wilm <AT> biophys <DOT> uni-duesseldorf <DOT> de
================================================
Heinrich-Heine-Universitaet Duesseldorf
Institut fuer Physikalische Biologie
http://www.biophys.uni-duesseldorf.de/~wilm