From: Charles Shapiro (cshapiro_at_nubridges.com)
Date: Mon 06 Oct 2003 - 21:27:30 BST
Hmm. We have also had Troubles with lo: here trying to run our software
on vservers. Specifically, our software doesn't seem to see it even
though an "ifconfig -a" from inside a vserver shows it. Of course, that
command also shows "eth0:" information, and we can't touch it either.
So far our solution has been to force references to localhost by adding
the vserver's real hostname to the "127.0.0.1" line in the /etc/hosts
127.0.0.1 localhost localhost.localdomain realname
This ain't perfect, but maybe it will get you over.
On Mon, 2003-10-06 at 14:27, Lucas Albers wrote:
> I have been very happy with vserver, it has been up for 55 days without a
> single problem; running 3 vservers on one machine.
> One of my machines is my local security scanner, running nessus.
> When I run nmap it complains about not being able to find lo interface.
> Any ideas how to fix this?
> [root_at_vserver:sara logs]nmap -v -sP computer
> Starting nmap 3.30 ( http://www.insecure.org/nmap/ ) at 2003-10-06 12:34 MDT
> Failed to find interface lo mentioned in /proc/net/route
> I have tried and called nmap and define the interface in the call, but it
> still complains:
> nmap -e eth0 -v -sP computer
> Any ideas?
> Montana State University - Bozeman
> Computer Science
> System Administrator
> Bozeman MT