Re: [PATCH]upnp-info.nse and upnp.lua

[kaito <kaito834 () gmail com>]

> I am not so sure about upnp-info.nse.patch. The patch changes the script
> to send a multicast request instead of a unicast request, then discard
> the results that do not match the desired address. Could you instead try
> the broadcast-upnp-info script, which does this already?
> http://nmap.org/nsedoc/scripts/broadcast-upnp-info

Yeah, I have already done broadcast-upnp-info script, and understood
patched upnp-info script and broadcast-upnp-info was same if not
discard the result. Maybe, upnp-info.nse.patch is my taste:S

When broadcast-upnp-info script done to 192.168.0.106, then M-SEARCH
request sent to same lan. So, the result is the following; I could get
the upnp-info of 192.168.0.1. I wanted only the result of
192.168.0.106:( So, I wrote the patch.

> nmap -sn -n --script=broadcast-upnp-info 192.168.0.106

Starting Nmap 6.25 ( http://nmap.org ) at 2013-02-26 00:44 東京 (標準時)
Pre-scan script results:
| broadcast-upnp-info:
|   192.168.0.106
|       Server: ...
(snip)
|   192.168.0.1
|       Server: ...
(snip)

I think it is better result that broadcast-upnp-info can get upnp-info
of all upnp device on same lan, and upnp-info can get an upnp-info of
target ip address.


-- 
kaito<kaito834 () gmail com>
Blog: http://d.hatena.ne.jp/kaito834/
Twitter: http://twitter.com/kaito834/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/