Re: Wild TTL value

[Gisle Vanem <gvanem () broadpark no>]

"David Fifield" <david () bamsoftware com> wrote:

> Okay. If not from you though, I need before-and-after default TTLs from
> somebody, for a connect scan on Linux and Windows. Or I'm going to
> forget the patch.

Okay. It's probably okay to forget about the error from:

  * libnetutil/netutil.cc(871) (set_ttl+34):   setsockopt (1780, IPPROTO_IP,
                   IP_TTL, ULONG_MAX, 4) --> WSAEINVAL: Invalid arguments (10022).

In the comments for IP_TTL here:
 http://msdn.microsoft.com/en-us/library/windows/desktop/ms738586(v=vs.85).aspx

it says:

 Changes the default value set by the TCP/IP service provider in the TTL field 
 of the IP header in outgoing datagrams. IP_TTL support is not required; ..

I assume the Service Provider (WSP) will not fall over if given a ULONG_MAX.
My intention behind the patch was just to make things a bit cleaner. 

--gv
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/