The short version of this is that from client A to server B, some connections are getting all the way there, and others are being dropped in transit. I know they're being dropped in transit because, when I do a tcpdump at the server, I see hits for the ports that work, but nothing for the ones that don't.
I tried the nmap
command:
nmap -p <port> --traceroute <dst_ip>
which works perfectly when the connection is successful, but if the connection fails for whatever reason, it marks the port as filtered and then switches to icmp for the traceroute.
Is there something I can do to force the traceroute to stay in the port supplied even if the connection is unsuccessful? I need to be able to see how far the specific port(s) get before being dropped.
I can't find any parameter to control this behavior in the document of nmap.
If you want to find which hop drops the specific packet, you may try to use traceroute. The parameter -P
is for protocol and -p
is for port.
Hope this helps.
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments