On (02/26/09 14:13), Peter Memishian wrote: > > Sure, it's a workaround (it actually only clobbers it for apps that > haven't explicitly requested a TTL).
but that would cause most well-behaved apps to be affected by the workaround for the problem app Looking at the code, it seems like ips_ip_def_ttl is used for all the icmp errors. This then begs the question, "so what is icmp_def_ttl?"- that's the ttl that can be set by both IP_TTL and by ndd for raw sockets Then there's tcp_ttl: that seems to be used for creating the header template for all tcp packets on a conn. All the ulp ttls seem to follow a similar pattern. And all of them can be over-ridden by the IP_TTL sockopt. If all we want is a sledge-hammer to force ttls, can we not achieve this by at most one ndd tunable that sets the ip ttl (instead of having so many ulp ttls!)? --Sowmini
