1. 14 Oct, 2014 1 commit
  2. 12 Oct, 2014 1 commit
  3. 30 Jun, 2014 2 commits
  4. 04 Mar, 2014 1 commit
  5. 15 Dec, 2013 1 commit
  6. 27 Jun, 2013 1 commit
  7. 22 May, 2013 2 commits
    • Guy Harris's avatar
      AAAAAArgh. The capture_input_new_XXX routines are called from · 9ac21fd6
      Guy Harris authored
      capture_sync.c, not from capture.c, so they should be declared in
      capture_sync.h, so callers that use the capture_sync.c stuff but not the
      capture.c stuff - such as TShark - get the declarations and get their
      implementations compared with the signatures that they should have.
      
      Doing so points out that some of them in TShark *don't*, so fix that.
      
      svn path=/trunk/; revision=49517
      9ac21fd6
    • Guy Harris's avatar
      Pull the capture-session state information out of capture_opts and put · 8596d17d
      Guy Harris authored
      it into a separate capture_session structure.  capture_opts should
      contain only user-specified option information (and stuff directly
      derived from it, such as the "capturing from a pipe" flag).
      
      svn path=/trunk/; revision=49493
      8596d17d
  8. 26 Apr, 2013 1 commit
  9. 28 Jun, 2012 1 commit
  10. 13 Mar, 2012 1 commit
    • Guy Harris's avatar
      Add an explicit capture_cb_capture_failed indication for the case where · cd1debf1
      Guy Harris authored
      we weren't even able to start a capture, rather than delivering a fake
      "capture start" indication and relying on a later "capture file closed"
      indication - for a capture that was never opened in the first place - to
      handle GUI cleanups.
      
      Don't deliver any GUI indications in cf_close() if we didn't have a
      capture file open in the first place.
      
      Clear the status bar and welcome header if that indication is delivered.
      
      If we start a capture from the command line with the -k flag, don't show
      the captured packet information unless the capture actually starts.
      
      svn path=/trunk/; revision=41521
      cd1debf1
  11. 25 Jan, 2012 1 commit
    • Michael Tüxen's avatar
      Third try. This time pipes and stdin are supported and the · 14b1a44c
      Michael Tüxen authored
      test scripts are passed.
      
      Use a global list containing all interfaces and only change
      properties of the entries when changes are made in the GUI.
      Do not misuse the list of interfaces specified on the command
      line anymore.
      
      This patch does not provide any new functionality, it just
      provides the base for future extensions like removing
      remote interface, mulitple airpcap devices and multiple
      pipes.
      
      This patch was provided by Irene Ruengeler.
      
      svn path=/trunk/; revision=40715
      14b1a44c
  12. 24 Jan, 2012 2 commits
  13. 29 Dec, 2011 1 commit
  14. 20 Oct, 2011 2 commits
  15. 27 Jun, 2011 1 commit
  16. 26 Aug, 2010 1 commit
  17. 26 May, 2010 1 commit
  18. 14 May, 2010 1 commit
  19. 04 Mar, 2010 1 commit
  20. 19 Aug, 2008 1 commit
  21. 24 Jun, 2008 1 commit
    • Guy Harris's avatar
      Have separate callback mechanisms in file.c and capture.c; pass the · c4932893
      Guy Harris authored
      capture callbacks the capture_options * as its second argument in all
      cases.  This makes it a bit clearer what arguments callbacks take, and
      means we can get rid of all global_capture_opts references in
      gtk/main_statusbar.c.
      
      Put the interface between gtk/main.c and gtk/main_statusbar.c into a
      private header.
      
      svn path=/trunk/; revision=25576
      c4932893
  22. 21 Feb, 2008 1 commit
  23. 02 Aug, 2007 1 commit
  24. 20 Jul, 2007 1 commit
  25. 11 Jun, 2007 1 commit
    • Gerald Combs's avatar
      One more step in privilege separation. · e9f1a0b6
      Gerald Combs authored
      Add a capture_interface_list(), which works similar to
      get_interface_list() except that it forks dumpcap instead of calling
      the pcap routines directly.  Use it in the GUI.
      
      Add a "-I" flag to dumpcap, which prints out verbose interface
      information.
      
      Tested under Windows and Linux.
      
      svn path=/trunk/; revision=22071
      e9f1a0b6
  26. 21 May, 2006 1 commit
  27. 13 Mar, 2006 1 commit
    • Ulf Lamping's avatar
      fix bug #803: sync pipe on Win32 wasn't set to binary mode, so error message... · 069b26b2
      Ulf Lamping authored
      fix bug #803: sync pipe on Win32 wasn't set to binary mode, so error message transport failed between Ethereal and dumpcap.
      
      I've also changed the way the secondary error message is transported from former "header message 0 secondary 0" to "header header message 0 header secondary 0" as that might be a bit more clearer, and I'll need it for further development anyway.
      
      I was using this while debugging and not recognizing the real problem - for about four hours :-(. I'll need this feature when doing the interface (and link layer type) browsing later (transferring this data from dumpcap to Ethereal) to get a full blown privilege seperation.
      
      svn path=/trunk/; revision=17608
      069b26b2
  28. 05 Mar, 2006 1 commit
    • Guy Harris's avatar
      Pass two strings in capture child messages, so the child can send · cbe69401
      Guy Harris authored
      primary and secondary error messages and let the parent worry about how
      to display them.  This means dumpcap doesn't need stub routines for
      generating the formatting tags for the primary and secondary messages.
      
      Have a separate message for capture filter errors, so that the parent
      can check whether the capture filter looks like a display filter and
      report the appropriate message.  This means that dumpcap doesn't need a
      stub routine for compiling display filters (a stub routine also means
      that Ethereal won't do the check for capture filters that look like
      display filters!).
      
      svn path=/trunk/; revision=17465
      cbe69401
  29. 03 Dec, 2005 2 commits
  30. 17 Nov, 2005 1 commit
    • Guy Harris's avatar
      Handle "-G" only in Tethereal - it doesn't work in Ethereal, and isn't · 2f7fd680
      Guy Harris authored
      necessary there.
      
      Add a "cmdarg_err()" routine to report command-line option errors; it
      creates a console if necessary, and prints the command name and the
      trailing newline.  Also add "cmdarg_err_cont()", which also creates a
      console if necessary, and prints a trailing newline but no command name;
      it's used to continue the message.  Use those, rather than
      "g_warning()", for errors.
      
      That means that we no longer need to pass the command name to various
      command-line argument parsing routines.
      
      svn path=/trunk/; revision=16526
      2f7fd680
  31. 26 May, 2005 1 commit
    • Ulf Lamping's avatar
      use the log features of the GLib to have verbose output of the capturing... · 5d404864
      Ulf Lamping authored
      use the log features of the GLib to have verbose output of the capturing engine, e.g. GLib provides different domains for different submodules. Output more verbose than warning level will be disabled by default (just like before).
      
      use the console_log_handler in main.c for win32 AND unix now
      
      Currently use the log for the capturing engine (only), as I desperately needed a log output for debugging.
      
      
      svn path=/trunk/; revision=14438
      5d404864
  32. 27 Apr, 2005 1 commit
  33. 16 Apr, 2005 1 commit
  34. 12 Apr, 2005 1 commit
    • Ulf Lamping's avatar
      capture engine: · 7e9cedfe
      Ulf Lamping authored
      add a new feature to clear the currently captured packets and restart the capture with the previous parameters
      
      various code cleanup and minor bugfixes
      
      Win32: use millisecond resolution in capture_loop, to smooth screen update a bit (500ms instead of 1000ms)
      
      svn path=/trunk/; revision=14059
      7e9cedfe
  35. 10 Apr, 2005 1 commit
    • Ulf Lamping's avatar
      Win32 only bugfix: as using TerminateProcess is the brute force way and... · 7b7f7e7f
      Ulf Lamping authored
      Win32 only bugfix: as using TerminateProcess is the brute force way and sometimes clipped packets in the middle, now using a pipe called signal_pipe from the parent to the child for this.
      On unix we're using kill() for this, which simply signals the child, but this isn't available on win32.
      
      svn path=/trunk/; revision=14040
      7b7f7e7f