Nmap Development mailing list archives
Re: Possible regression: weird IPv6 error when trying to portscan behind proxychains
From: Jacek Wielemborek <d33tah () gmail com>
Date: Sat, 29 Mar 2014 18:42:47 +0100
22/09/2013 16:25:19 Jacek Wielemborek <wielemborekj1 () gmail com>:
2013/9/22 Jacek Wielemborek <wielemborekj1 () gmail com>:Hi, I'm copying the message below as written from an IRC guy mx8manger, who contacted #nmap yesterday. (CUT)Since his message is a bit cryptic, I'll explain it here below. Basically, what he tried was to nmap -sT scanme.nmap.org behind his proxychains. The error message, not included in his original e-mail, but posted on the IRC, is following: root@linux-pc:~# proxychains nmap -sV scame.nmap.org ProxyChains-3.1 (http://proxychains.sf.net) Starting Nmap 6.41SVN ( http://nmap.org ) at 2013-09-22 00:31 AST |DNS-request| scame.nmap.org |S-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<><>-OK |DNS-response| scame.nmap.org is 173.255.243.189 173.255.243.189/0 looks like an IPv6 target specification -- you have to use the -6 option. WARNING: No targets were specified, so 0 hosts scanned. Nmap done: 0 IP addresses (0 hosts up) scanned in 1.56 seconds (original source: http://paste.ubuntu.com/6138529/) (he said that -sT reacts the same way). I marked it as a "possible regression" because the guy said that this setup used to work with one of the older versions of Nmap. We probably don't have the e-mail address for the fellow. I attach the IRC log. Yours, Jacek Wielemborek
Just wanted to let you know that this bug still affects current SVN.
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: Possible regression: weird IPv6 error when trying to portscan behind proxychains Jacek Wielemborek (Mar 29)