|
List Info
Thread: Nessus is Not Scanning
|
|
| Nessus is Not Scanning |

|
2006-09-14 13:10:23 |
|
Hi all,
I've installed Nessus 3.0.3 build W327 beta version to my windows pc
but it is not performing scanning. Is it restricted to only localhost?
Is there anyone who can help me to find what the problem is?
Here are some information about it:
- Nessus scanner service is running
- I can scan my own computer (scans localhost) but,
- I cannot scan another IP
- When I run ethereal to look what's going on, I cannot see any traffic also.
Thanks
|
| DHCPv6 Relay Agent Link Selection(RALS)
Opt ion |

|
2006-09-14 12:59:11 |
|
| I agree with Andre. I can't see the need for this
option.
The link-address field in the relay-forw message is
addressing information for the server to use in determine where the client is
(for address assignment/prefix-delegation purposes). There is ***NO***
requirement that this address be an address that the relay-agent has
configured.
The address of relay agent is in either the peer-address
field (if this isn't the first hop relay) or in the SOURCE address of the
relay-forw packet. Thus, unlike in DHCPv4 where the giaddr field is overloaded
to mean two things, that is NOT the case for DHCPv6.
Unless you can come up with a reason why the link-address
field isn't sufficient, I can't see supporting this work.
- Bernie
Hello,Kostur
Thank you!
Yes, it is a counterpart of DHCPv4
link-selection sub-option, so we used a similiar option name. And we
missed it in the draft, sorry.
I obtain the requirement from NetLMM
Base protocol, the draft is still in progress.
+--------------------------------+
| LMM
Domain
|
|
|
|
+----+
+----+
|
| |LMA
| |
LMA|
|
|
+----+
+----+
|
|
\
/
|
| **********************
|
|
*
*
|
| * IP
network *
|
|
*
*
|
| **********************
|
| &n | |