loopback was down and with no IP
Hi
Something strange has just happened to me. I've installed two very
different boxes (nela is K7/1.3 GHz, yolanda is IBM Pentium 100) using
ReiserFS boot disks for Woody, and one CD, and later upgraded via iNet.
After finishing installation of base system, and adding some other
packages (postfix, screen, bitchx, nmap, links-ssl, libncurses5-dev and
little more), I nmapped me and this is what I got:
yolanda:~# nmap localhost
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
WARNING: Could not determine what interface to route packets through to
127.0.0.1, changing ping scantype to ICMP ping only
pcap_open_live: bind: No such device
There are several possible reasons for this, depending on your operating
system:LINUX: If you are getting Socket type not supported, try modprobe
af_packet or recompile your kernel with SOCK_PACKET enabled.
*BSD: If you are getting device not configured, you need to recompile
your kernel with Berkeley Packet Filter support. If you are getting No
such file or directory, try creating the device (eg cd /dev; MAKEDEV
<device>; or use mknod).
SOLARIS: If you are trying to scan localhost and getting '/dev/lo0: No
such file or directory', complain to Sun. I don't think Solaris can
support advanced localhost scans. You can probably use "-P0 -sT
localhost" though.
QUITTING!
yolanda:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:FC:4C:B6:51
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39080 errors:0 dropped:0 overruns:0 frame:0
TX packets:20737 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:56575180 (53.9 MiB) TX bytes:1424432 (1.3 MiB)
Interrupt:11 Base address:0xfc00
yolanda:~# nmap 127.0.0.1
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
WARNING: Could not determine what interface to route packets through to
127.0.0.1, changing ping scantype to ICMP ping only
pcap_open_live: bind: No such device
There are several possible reasons for this, depending on your operating
system:LINUX: If you are getting Socket type not supported, try modprobe
af_packet or recompile your kernel with SOCK_PACKET enabled.
*BSD: If you are getting device not configured, you need to recompile
your kernel with Berkeley Packet Filter support. If you are getting No
such file or directory, try creating the device (eg cd /dev; MAKEDEV
<device>; or use mknod).
SOLARIS: If you are trying to scan localhost and getting '/dev/lo0: No
such file or directory', complain to Sun. I don't think Solaris can
support advanced localhost scans. You can probably use "-P0 -sT
localhost" though.
QUITTING!
yolanda:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:50:FC:4C:B6:51
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39153 errors:0 dropped:0 overruns:0 frame:0
TX packets:20783 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:56581294 (53.9 MiB) TX bytes:1430956 (1.3 MiB)
Interrupt:11 Base address:0xfc00
lo Link encap:Local Loopback
LOOPBACK MTU:3924 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
yolanda:~# ifconfig lo up
yolanda:~# nmap 127.0.0.1
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
WARNING: Could not determine what interface to route packets through to
127.0.0.1, changing ping scantype to ICMP ping only
pcap_open_live: bind: No such device
There are several possible reasons for this, depending on your operating
system:LINUX: If you are getting Socket type not supported, try modprobe
af_packet or recompile your kernel with SOCK_PACKET enabled.
There are several possible reasons for this, depending on your operating
system:
LINUX: If you are getting Socket type not supported, try modprobe
af_packet or recompile your kernel with SOCK_PACKET enabled.
*BSD: If you are getting device not configured, you need to recompile
your kernel with Berkeley Packet Filter support. If you are getting No
such file or directory, try creating the device (eg cd /dev; MAKEDEV
<device>; or use mknod).
SOLARIS: If you are trying to scan localhost and getting '/dev/lo0: No
such file or directory', complain to Sun. I don't think Solaris can
support advanced localhost scans. You can probably use "-P0 -sT
localhost" though.
QUITTING!
yolanda:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:FC:4C:B6:51
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39236 errors:0 dropped:0 overruns:0 frame:0
TX packets:20838 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:56588116 (53.9 MiB) TX bytes:1438778 (1.3 MiB)
Interrupt:11 Base address:0xfc00
lo Link encap:Local Loopback
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
yolanda:~# ifconfig lo 127.0.0.1
yolanda:~# nmap 127.0.0.1
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on yolanda (127.0.0.1):
(The 1545 ports scanned but not shown below are in state: closed)
Port State Service
9/tcp open discard
13/tcp open daytime
22/tcp open ssh
25/tcp open smtp
37/tcp open time
110/tcp open pop-3
111/tcp open sunrpc
113/tcp open auth
515/tcp open printer
Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
It is strange, you see? Interface "lo" had no IP assigned (and so, it
was down). I think I've done nothing strange for this to happen (after
finishing installing from CD, just ifconfig eth0, route add default gw,
and echo "namerserver xxx">/etc/resolv.conf).
Any ideas?
Regards,
Pope
--
Luis Gómez Miralles
InfoEmergencias - Technical Department
Phone (+34) 654 24 01 34
Fax (+34) 963 49 31 80
lgomez@infoemergencias.com
PGP Public Key available at http://www.infoemergencias.com/lgomez.asc
--
To UNSUBSCRIBE, email to debian-security-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: