Wireshark-bugs: [Wireshark-bugs] [Bug 2731] tshark/wireshark don't allow snaplen < 68
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 1 Aug 2008 18:06:22 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2731


Chris Maynard <christopher.maynard@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #2095|                            |review_for_checkin?
               Flag|                            |




--- Comment #1 from Chris Maynard <christopher.maynard@xxxxxxxxx>  2008-08-01 18:06:21 PDT ---
Created an attachment (id=2095)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2095)
Patch to remove snaplen restriction of 68.

I tested tcpdump 3.7.2 linked to libpcap 0.7.2 using a snaplen of 1 and it
worked just fine.  In fact, even a snaplen of 0 works.  According to the
tcpdump man page, "Setting snaplen to 0 means use the required length to catch
whole packets."

So, since tcpdump places no restrictions on the snaplen, I didn't see any
reason why tshark/Wireshark should.  Attached is a small patch that allows the
full range of snaplens from 0-65535.  I tested this patch on Windows using both
Wireshark and tshark and snaplens set to 1 and 0.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.