[SATAN IMAGE]SATAN Troubleshooting


Symptoms and questions (you might look at the FAQ for more questions/answers.)

SATAN crashed, hung, or did very odd things to a system that it was run against.

We've received reports of various OS's that seem to have significant trouble with SATAN scans, particularily the UDP and TCP scans that span lots of ports. Among the afflicted:

I ran SATAN to analyze my results and the machine slows grinds down to a standstill (and possibly crashes), but I don't get any answers.

It could be, with a large amount of data, that SATAN is using too much memory to fit in your machine. An enormous amount of memory is consumed by the program (see

Given that Satan starts its own http server on the local host, why doesn't it use 'localhost' instead of the FQDN of the local host when trying to contact it?

This breaks some HTML browsers. Try running with $dont_use_dns (found in config/satan.cf) when your naming service is crippled.

Whenever I click on a hyper link it doesn't work.

Be careful if you use proxy services (typically if you're behind a firewall you do) to access the WWW - you should unset your file environment variables (such as $http_proxy $file_proxy, $socks_ns, etc.) and/or change your browser's configuration to not use your SOCKS host or HTTP Proxy host (in your HTML browser's option section.)

I'm trying to get SATAN running on my Linux box.

Linux is far from a standard Un*x, and SATAN has a tendency to push the OS and perl to the limits. We've tried to do as much as possible to make it work, but there are probably various problems we haven't found because we don't have a Linux box to play with. (Cross?) posting to comp.security.unix and comp.os.linux.* could probably give you more help than we could.
Back to the Documentation TOC