The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/3250
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/2795
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build
Michael Tüxen Michael.Tuexen@... writes:
You actually need:
-n to use pcapng
and
-t to use threads.
It is simple to add -n and -t if you are specifying more than one interface
(actually this is what tshark and wireshark do). I wanted to be explicit
since I consider it currently an
Hmm, wouldn't using any was a means of nullifying other interfaces break
concurrent capturing on both the any interface and Bluetooth or USB
interfaces?
Still, I agree with Chris's suggestions, with regards to weak emulation of
an any interface under Windows; and speculative capturing (i.e.
Chris Maynard 5/20/2011 10:25 AM
To me, if it doesn't work without -n and -t, then it makes it that much more
user-friendly to automatically use pcapng and threads whenever multiple
interfaces are specified.
+1 to automagically do -n -t when more than one
interface is specified.
Here's some
On May 20, 2011, at 9:49 AM, Jim Young wrote:
When I used the command:
./dumpcap -I -i en1 -i fw0 -t -n -w iftest.pcapng
I got the message:
The capture session could not be initiated (That device doesn't support
monitor mode).
Presumably the -s option is per-interface, as the
Hello Michael,
On Thu, May 19, 2011 at 10:50:25PM +0200, Michael T?xen wrote:
it was a bug. I did not move the code for given up the permissions
to a place where all interfaces were opened. I checked in a fix
in r37311. Please retest and let me know if this fixes your issue.
Fixed of course
On Fri, May 20, 2011 at 02:25:38PM +, Chris Maynard wrote:
To me, if it doesn't work without -n and -t, then it makes it that much more
user-friendly to automatically use pcapng and threads whenever multiple
interfaces are specified.
Do we really need pcapng if multiple interfaces of the
On Fri, May 20, 2011 at 02:25:38PM +, Chris Maynard wrote:
And while I'm at it ... another feature that I think would be nice to have
would
be to be able to specify capturing on an interface that doesn't yet exist,
such
as ppp0. For my USB/PPP capturing, currently to get a capture of
