On Mon, Oct 06, 2003 at 04:27:30PM -0400, Charles Shapiro wrote: > 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 > file, as:
depending on the issues, somethimes the other way is very handy too xxx.yyy.zzz.vvv realname localhost localhost.localdomain YMMV, Herbert > > 127.0.0.1 localhost localhost.localdomain realname > realname.realdomain > > This ain't perfect, but maybe it will get you over. > > -- CHS > > 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? > > [EMAIL PROTECTED]: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 > > > > QUITTING! > > > > 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? > > > > --Luke > > Montana State University - Bozeman > > Computer Science > > System Administrator > > Bozeman MT
