Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-users: Re: [Wireshark-users] Editcap 100 argument limitation?

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Tue, 19 Jun 2007 14:18:36 -0700

On Tue, Jun 19, 2007 at 04:48:15PM -0400, Rob Campbell wrote:

> I did some experimenting and the problem seems to lie in that editcap 
> seems to only read the first 100 arguments (be it individual packet 
> numbers or sets of packet numbers).
>
> Is this limit intentional or can it be removed?  Is this a unix/linux 
> limitation?

This is an arbitrary limit compiled into the editcap program:

Line 109 of editcap.c:

  static struct select_item selectfrm[100];

How many arguments do you need to pass to editcap?  We could look into 
changing this limit or removing it entirely to make it dynamically 
allocate space for as many arguments as fit on the command-line.


Steve


  • Follow-Ups:
    • Re: [Wireshark-users] Editcap 100 argument limitation?
      • From: Jeff Morriss
  • References:
    • [Wireshark-users] Editcap 100 argument limitation?
      • From: Rob Campbell
  • Prev by Date: [Wireshark-users] Cannot reassemble (and save as a file) packets
  • Next by Date: Re: [Wireshark-users] Editcap 100 argument limitation?
  • Previous by thread: [Wireshark-users] Editcap 100 argument limitation?
  • Next by thread: Re: [Wireshark-users] Editcap 100 argument limitation?
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation