Bug 125491

Summary: Samba packets with TTL 0
Product: Red Hat Enterprise Linux 3 Reporter: NN Poster <nnposter>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: medium    
Version: 3.0CC: abartlet, fenlason
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-12 17:49:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description NN Poster 2004-06-08 01:26:42 UTC
Description of problem:
Samba packaged with RHEL 3 emits name service broadcast packets 
(137/udp) with TTL set to 0, which is illegal according to RFC 791.

(The symptom appears to be specific either to the RHEL build or to a 
particular version of Samba because all other Samba instances that I 
have access to use TTL 1.)

Version-Release number of selected component (if applicable):
samba-3.0.2-6.3E

How reproducible:
always

Steps to Reproduce:
1. /etc/init.d/smb start
2. tethereal -i eth0 -w capture udp port 137 and ip src host <my-ip>
3. tethereal -r capture ip.ttl==0
  
Actual results:
lots of packets

Expected results:
no packets

Additional info:

Comment 1 Andrew Bartlett 2007-01-02 01:26:39 UTC
I don't see how Samba can even do this.  We just call sendto().  I suspect a
kernel issue with UDP broadcasts.

Comment 2 Prarit Bhargava 2007-09-12 17:49:35 UTC
NOTABUG based on abartlet's comment.

P.