Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"X.X.X.X/0 looks like an IPv6 target specification" error with proxychains-ng #52

Closed
dmiller-nmap opened this issue Jan 21, 2015 · 1 comment
Labels
expected-behavior Behavior described is currently expected/documented, but that doesn't preclude improvements Nmap

Comments

@dmiller-nmap
Copy link

This is a known old bug with Proxychains-NG, which I am entering into our issues tracker to make it more searchable. Here is one of the original reports: http://seclists.org/nmap-dev/2014/q4/54

Example output:

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
@dmiller-nmap dmiller-nmap added expected-behavior Behavior described is currently expected/documented, but that doesn't preclude improvements Nmap labels Jan 21, 2015
@dmiller-nmap
Copy link
Author

Proxychains-NG before version 4.8 does not respect the AI_NUMERICHOST flag to
getaddrinfo. Proxychains-NG changelog message for version 4.8:

- fix for odd cornercase where getaddrinfo was used with AI_NUMERICHOST to test for a numeric ip instead of resolving it (fixes nmap).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
expected-behavior Behavior described is currently expected/documented, but that doesn't preclude improvements Nmap
Projects
None yet
Development

No branches or pull requests

1 participant