FWD: Possible regression: weird IPv6 error when trying to portscan behind proxychains

[Jacek Wielemborek <wielemborekj1 () gmail com>]

Hi,

I'm copying the message below as written from an IRC guy mx8manger,
who contacted #nmap yesterday.

Greeting Nmap team developer,
i have ubuntu 13 and nmap 6.3 was running normally then i went and
downloaded your latest svn which turned to be At revision 32375.
uname -a
Linux lolz-pc 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:36:13 UTC
2013 i686 i686 i686 GNU/Linux


-------------------------------------------------------------------------------------------------------------------------------------------------------
Nmap version 6.41SVN ( http://nmap.org )
Platform: i686-pc-linux-gnu
Compiled with: nmap-liblua-5.2.2 openssl-1.0.1c nmap-libpcre-7.6
nmap-libpcap-1.2.1 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select
___________________________________________________________________________________________________________________
i had no errors after compiling the nmap neither when installing it
but it didnt work with proxychains at all !
included with email a few log  with the debug level
the commands i used were
proxychains -sT -d9 scame.nmap.org
i tried scanning with -Pn and -sV and it didnt work at all
but when am not using proxychains everything goes fine whyy ?
proxychains is working fine
-----------------------------------------------------------------------------------------------------------------------------------------------------------
proxychains ping google.com
ProxyChains-3.1 (http://proxychains.sf.net)
PING google.com (173.194.35.163) 56(84) bytes of data.
64 bytes from 173.194.35.163: icmp_req=1 ttl=46 time=169 ms
64 bytes from 173.194.35.163: icmp_req=2 ttl=47 time=158 ms
-----------------------------------------------------------------------------------------------------------------------------------------------------------
i thought maybe i had something wrong in the compilation so i copied
the compilation logs as well
and also d33tah pointed to an interesting error
when i tried scanning ip directly it started from 0.0.0.1 ??
here:-
_____________________________________________________________________________________________________________________

nmap -sT 137.255.243.189/0

setup_target: failed to determine route to 0.0.12.83
setup_target: failed to determine route to 0.0.12.84
setup_target: failed to determine route to 0.0.12.85
setup_target: failed to determine route to 0.0.12.86
setup_target: failed to determine route to 0.0.12.87
setup_target: failed to determine route to 0.0.12.88
setup_target: failed to determine route to 0.0.12.89
setup_target: failed to determine route to 0.0.12.90
setup_target: failed to determine route to 0.0.12.91
setup_target: failed to determine route to 0.0.12.92
setup_target: failed to determine route to 0.0.12.93
setup_target: failed to determine route to 0.0.12.94
setup_target: failed to determine route to 0.0.12.95
setup_target: failed to determine route to 0.0.12.96
setup_target: failed to determine route to 0.0.12.97
setup_target: failed to determine route to 0.0.12.98
setup_target: failed to determine route to 0.0.12.99
setup_target: failed to determine route to 0.0.12.100
setup_target: failed to determine route to 0.0.12.101
the rest is found in nmap_interesting_error_log.log
______________________________________________________________________________________________________________________


thanks alot nmap i will be thankfull if you replied me with the problem solution
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/