Re: [tcpdump-workers] Link-Layer Header Type request for USBPcap

2013-03-27 Thread Guy Harris
OK, 249 assigned for LINKTYPE_USBPCAP/DLT_USBPCAP.

You might want to update your description to clarify the points I mentioned - 
not everybody writing or maintaining code to process this will necessarily be 
familiar with #pragma pack(), Windows NT IRPs, etc.

___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] tcpdump 4.4 release candidate 1

2013-03-27 Thread Wesley Shields
On Mon, Mar 25, 2013 at 02:42:07PM -0400, Wesley Shields wrote:
 On Sun, Mar 24, 2013 at 05:52:51PM -0400, Michael Richardson wrote:
  
   Romain == Romain Francoise rom...@orebokech.com writes:
   please expect a new release candidate on 2013-03-09, assuming I
   can get enough Internet in St.Johns.
  
  Romain Not sure if this was St John's in Antigua or St John's in
  Romain Canada, hopefully the former this time of year (but most
  Romain likely the latter). :-)
  
  It was a 7000km of air travel for a 2300km trip thanks to snow at LGA.
  Very tiring.
  
  Romain In any case the rc2 tarballs are nowhere to be found. Can we
  Romain get an update, please?
  
  http://www.ca.tcpdump.org/beta/
 
 Picking a random spot in this thread to chime in but I've heard reports
 via co-workers that hitting ^C while handling multiple input files via
 'find | tcpdump -V -' doesn't work as expected. I'm trying to find time
 to look into this before the 4.4.0 release.

Hopefully it's not too late to get https://github.com/mcr/tcpdump/pull/60
merged in to 4.4.0.

Prior to the fix mentioned above if you hit ^C while doing

find /pcaps -type f | tcpdump -V - -w foo.pcap

it would stop processing the current file and move on to the next one in
the list. With this fix it stops processing the entire list and exits
normally.

-- WXS
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers