Nmap broadcast-ripng-discover NSE Script


This page contains detailed information about how to use the broadcast-ripng-discover NSE script. For list of all NSE scripts, visit the Nmap NSE Library.

Select:
Overview
Error Messages

Script Overview

Script source code: https://github.com/nmap/nmap/tree/master/scripts/broadcast-ripng-discover.nse
Script categories: broadcast, safe
Target service / protocol: -
Target network port(s): -
List of CVEs: -

Script Description

The broadcast-ripng-discover.nse script discovers hosts and routing information from devices running RIPng on the LAN by sending a broadcast RIPng Request command and collecting any responses.

Broadcast-ripng-discover NSE Script Arguments

This is a full list of arguments supported by the broadcast-ripng-discover.nse script:

broadcast-ripng-discover.timeout

Sets the connection timeout (default: 5s)

- - -
To use this script argument, add it to Nmap command line like in this example:

nmap --script=broadcast-ripng-discover --script-args broadcast-ripng-discover.timeout=value <target>

Broadcast-ripng-discover NSE Script Example Usage

Here's an example of how to use the broadcast-ripng-discover.nse script:

nmap --script broadcast-ripng-discover

Broadcast-ripng-discover NSE Script Example Output

Here's a sample output from the broadcast-ripng-discover.nse script:

| broadcast-ripng-discover:
|   fe80::a00:27ff:fe9a:880c
|     route                       metric  next hop
|     fe80:470:0:0:0:0:0:0/64     1
|     fe80:471:0:0:0:0:0:0/64     1
|_    fe80:472:0:0:0:0:0:0/64     1

Broadcast-ripng-discover NSE Script Example XML Output

There is no sample XML output for this module. However, by providing the -oX <file> option, Nmap will produce a XML output and save it in the file.xml file.

Author

  • Patrik Karlsson

References

See Also

Related NSE scripts to the broadcast-ripng-discover.nse script:

Visit Nmap NSE Library for more scripts.

The broadcast-ripng-discover.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.

Invalid IPv6 address encountered

Here is a relevant code snippet related to the "Invalid IPv6 address encountered" error message:

76:	
77:	    -- Converts a RTE instance to string
78:	    -- @return string of bytes to send to the server
79:	    __tostring = function(self)
80:	      local ipstr = ipOps.ip_to_str(self.prefix)
81:	      assert(16 == #ipstr, "Invalid IPv6 address encountered")
82:	      return ipstr .. string.pack(">I2 BB", self.tag, self.prefix_len, self.metric)
83:	    end,
84:	
85:	
86:	  },

Couldn't determine what interface to use, try supplying it with -e

Here is a relevant code snippet related to the "Couldn't determine what interface to use, try supplying it with -e" error message:

181:	  local status = sock:sendto(host, port, tostring(req))
182:	
183:	  -- do we need to add the interface name to the address?
184:	  if ( not(status) ) then
185:	    if ( not(iface) ) then
186:	      return fail("Couldn't determine what interface to use, try supplying it with -e")
187:	    end
188:	    status = sock:sendto(host .. "%" .. iface, port, tostring(req))
189:	  end
190:	
191:	  if ( not(status) ) then

Failed to send request to server

Here is a relevant code snippet related to the "Failed to send request to server" error message:

187:	    end
188:	    status = sock:sendto(host .. "%" .. iface, port, tostring(req))
189:	  end
190:	
191:	  if ( not(status) ) then
192:	    return fail("Failed to send request to server")
193:	  end
194:	
195:	  local responses = {}
196:	  while(true) do
197:	    local status, data = sock:receive()

Version

This page has been created based on Nmap version 7.92.

Go back to menu.