Description of problem: sending net directed broadcasts results in a ttl of zero in the IP header (conflicting with RFC1122) Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.tcpdump a icmp request to a broadcast ip address 2. 3. Actual results: ip header has ttl of 0 Expected results: ip header should have ttl specified by application specific IP_TTL value from setsockopt, or from /proc/sys/net/ipv4/ip_default_ttl Additional info:
Created attachment 100518 [details] patch to default the ttl of an ip header to /proc/sys/net/ipv4/ip_default_ttl This patch picks up ip_default_ttl on output for frames which don't have an override ttl set via setsockopt. It's up on kernel list now, but I wanted to make sure we have a blocker bug to get it into RHEL3 U3
*** Bug 110387 has been marked as a duplicate of this bug. ***
A fix for this problem has been committed to the RHEL3 U3 patch pool this evening (in kernel version 2.4.21-15.6.EL).
Moving from u4 to u3 blocker for tracking.
Neil or others . . . is this looking good with the latest U3-candidate kernel?
the test I just ran from your machine looks to be working fine. Thanks!
Closing out based on feedback from original reporter.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-433.html