On Thu, 5 Jun 2003, Todd A. Jacobs wrote:

> Is there a place to define a source IP in nessus? I need something similar 
> to nmap's -S flag, or nmap simply binds to the loopback interface on my 
> box when spawned from nessus.

A little more information about this box: it's a Virtuozzo virtual machine 
with the following:

    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:1147518 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1147518 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:111856804 (106.6 Mb)  TX bytes:111856804 (106.6 Mb)
     
    venet0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
              inet addr:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.0
              UP BROADCAST RUNNING NOARP MASTER  MTU:1500  Metric:1
              RX packets:1408727 errors:0 dropped:0 overruns:0 frame:0
              TX packets:3160659 errors:0 dropped:1724851 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:238860188 (227.7 Mb)  TX bytes:268070342 (255.6 Mb)
     
    venet0:0  Link encap:Ethernet  HWaddr 00:00:00:00:00:00
              inet addr:10.10.2.5  Bcast:0.0.0.0  Mask:255.255.255.255
              UP BROADCAST RUNNING NOARP MASTER  MTU:1500  Metric:1

For whatever reason, nessus is sending a lot of traffic with a source port 
of 127.0.0.1, which obviously is just going to be discarded at the other 
end. I've tried running nessusd both with and without the -a flag, and it 
doesn't seem to make a difference.

How can I force it to use venet0:0 as the source interface?

-- 
The DMCA is anti-consumer. The RIAA has no right to rewrite copyright
laws to suit themselves.

Reply via email to