It appears from the message below that SuSe has fixed the kernel IP
checksum problem that was causing Nmap to fail. Apparently upgrading
to their 2.4.21-199 kernel resolves the issue.
If upgrading kernels makes you nervous, you can alternatively still
set HAVE_IP_IP_SUM in nbase/nbase_config.h in the source tree to zero
after you run ./configure but before "make". But this approach will
only fix the problem for Nmap and not other low-level packet tools.
-Fyodor
----- Forwarded message from "John S. Gaythorpe" <jsg_at_metrocast.net> -----
Date: Tue, 23 Mar 2004 13:26:31 -0500
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
From: "John S. Gaythorpe" <jsg_at_metrocast.net>
To: <nessus_at_list.nessus.org>
Subject: RE: Nessus and Suse 9.0 again...
Thank you for the idea!
I ran the update and the 2.4.21-199 kernel does fix the problem!
>===== Original Message From "John S. Gaythorpe" <jsg_at_metrocast.net>
>===== Well I know nessus and Suse 9.0 aren't playing well together. I
>did get nmap
>3.48 compiled and running with the recommended option (in NBASE:
>nbase_config.h define: HAVE_IP_IP_SUM 0)
>
>But nessus will not run (dead host thing.) Now I know it's a SUSE
>problem, but is there a workaround (like for NMAP?)
>
I had the same problem on SuSE 9.0. However, after upgrading the kernel to
"2.4.21-199smp4G," Nessus is happy again.
Note: I have an SMP machine, so that kernel may be compiled with different
options for a single processor box.
-C
_______________________________________________
Nessus mailing list
Nessus_at_list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
Nessus_at_list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
----- End forwarded message -----
---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to
nmap-dev-help@insecure.org . List archive: http://seclists.org
Received on Mar 23 2004