Using the following command:
nmap --proxy socks4://*.*.*.*:25074 -sV -O --reason scanme.nmap.org
I'm not sure if nmap is really using the proxy specified
Had an idea of scanning "localhost" or "127.0.0.1" while using netcat listening on specific port predefined in nmap arguments (other than the exact example above) but netcat doesn't reveal source address of scanning, it just echo the GET request (for port version detection i suppose)
and no matter what i put as invalid socks server ip address along with nmap it STILL do the scan
and doesn't give any error messages
the only error message i'm getting happens if i changed socks type from socks4 to socks5 which is:
Invalid protocol in proxy specification string: socks5://*.*.*.*:25074 QUITTING!
also tried tcpdump but i didn't find the packet request
so i'm not sure if it really use the socks proxy defined or not
How to make sure nmap is actually using a proxy?
Is there other ways of making sure other than setting up a remote machine myself and scanning it (i suppose it shouldn't be on same LAN which is hard to accomplish at the moment)
the same issue happens when using proxychain or scanning through vpn
Using Nmap version 7.12 on Linux