Re: misc/40057: tcpdump -w should document what packets are saved

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

The following reply was made to PR misc/40057; it has been noted by GNATS.

From: jnemeth%victoria.tc.ca@localhost (John Nemeth)
To: gnats-bugs%NetBSD.org@localhost, misc-bug-people%NetBSD.org@localhost, 
gnats-admin%NetBSD.org@localhost
Cc: 
Subject: Re: misc/40057: tcpdump -w should document what packets are saved
Date: Fri, 28 Nov 2008 21:39:12 -0800

 On Mar 16,  5:27am, Aleksej Saushev wrote:
 }
 } >Number:         40057
 } >Synopsis:       tcpdump(1) should document what packets are saved when 
using -w
 } >Originator:     Aleksej Saushev <asau%inbox.ru@localhost>
 } >Release:        NetBSD 5.99.01
 } >Organization:
 } >Environment:
 } System: NetBSD asau.local 5.99.01 NetBSD 5.99.01 (KERN) #0: Wed Nov 5 
20:10:09 MSK 2008 asau%asau.local@localhost:/usr/obj/sys/arch/i386/compile/KERN 
i386
 } Architecture: i386
 } Machine: i386
 } >Description:
 }      tcpdump(1) reads:
 } 
 }      -w    Write the raw packets to file rather than parsing  and  printing
 }               them  out.
 } 
 }      Experience shows that those packets are ethernet frames for ethernet
 }      interfaces. It would be nice to clarify that in the manual page.
 
      What does it store if you use -y to specify a linktype (i.e.
 IEEE80211)?
 
 } >How-To-Repeat:
 }      Read the man page. Wonder, what those packets are.
 } 
 }-- End of excerpt from Aleksej Saushev