Wireshark-bugs: [Wireshark-bugs] [Bug 10477] New: Wireshark command line option -B (buffer size)
| Bug ID |
10477
|
| Summary |
Wireshark command line option -B (buffer size) ignored
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
dde@innovaphone.com
|
Build Information:
Version 1.12.2rc0-1-gb2688c3 (v1.12.2rc0-1-gb2688c3 from master-1.12)
Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
AMD Phenom(tm) II X4 905e Processor, with 7934MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
During the development of our products we often use remote pcap interfaces.
On start of the capture we always get the error "Couldn't set the capture
buffer size!". The capture starts nonetheless but this message is annoying.
So we used the command line option "-B 1" to set a default buffer size of 1
MiB. This worked fine but with 1.12.x this option seems to be ignored and we
get the message again.
Is there any chance you'll get this working again?
Our own RPCAP implementation sends in the start capture reply message a certain
buffer size value but it seems to be ignored too, as I can set whatever value I
want.
The rpcapd daemon on linux suffers the same issue.
Greetings,
Daniel
You are receiving this mail because:
- You are watching all bug changes.
