| Bug ID |
13229
|
| Summary |
Feature request: Forced TCP Window Scaling factor on per-socket basis
|
| Product |
Wireshark
|
| Version |
2.2.2
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.2.2 (v2.2.2-0-g775fb08)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.6.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
Russian_Russia.1251, with WinPcap version 4.1.3 (packet.dll version 0.10r16),
based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15,
with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz (with SSE4.2), with 16182MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
If WS factor is unknown (no TCP handshake has been captured), I can tell
Wireshark to use any WS by command "TCP -> Protocol preferences -> Scaling
factor to use when is not available from capture"
But TCP endpoints usually have different WS factors, whereas above comand
affects all the trace.
Is it possible to implement definable WS factor, that will bind to only one TCP
socket (ip:port) that I specify?
You are receiving this mail because:
- You are watching all bug changes.