On Fri, 20 Aug 2004, Corio, Jim wrote: > I have an environment where I need to run Nessus as a dual homed > solution. Does anyone have any experience with this and can offer any > guidance as to what is required to do so and what pitfalls may be > encountered?
I may be missing some specific details of what you are trying to accomplish... but, from a basic perspective, it would be very simple. Nessus will just use the local routing rable for determining which interface to send out packets. For example, if you have 192.168.0/24 routed to eth0 and 172.16.0/24 routed to eth1, then the server's local routing table would handle directing packets to either of those subnets. If you scan, for example, 172.16.0.55, the local routing table would ensure the packets get directed to eth1. No special configurations in Nessus required at all. ~Jay -- .. .. Jay Jacobson .. Edgeos, Inc. - 480.961.5996 - http://www.edgeos.com .. .. Network Security Auditing and .. Vulnerability Assessment Managed Services .. _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
