| Bug ID |
8228
|
| Summary |
Improved capture filters - different default values under SLES11 and Windows
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86-64
|
| OS |
SuSE
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 9822 [details]
Zipped file containing screen snapshots 1 to 5 referred to in the Description
Build Information:
SVN revision 46987
--
With many recent improvements in the handling of capture filters and their
definitions, we have observed a slight discrepancy in their handling between
Windows and SLES11 based compilations of one and the same SVN.
Basically, under Windows the software works as intended. In the Capture Filter
window, the user can define a temp capture filter to be used on one or more eth
interfaces (see jpeg 01 in the attachment).
After completing data capture, this filter is retained (see jpeg 02 in the
attachment).
Quite by contrast, SLES11 build of the same SVN exhibits a different behaviour.
Upon start up, a default value is inserted in the Capture Filter window (see
jpeg 03 in the attachment). Something like:
not (tcp port 41368 and ip host IP1 and tcp port 22 and ip host IP2)
where IP1 and IP2 are two real IP addresses from the network Wireshark is
connected to.
Then the user can define his preferred temp capture filter as required (see
jpeg 04 in the attachment) and commence his data capture.
Upon completing the capture, and this is where the bug is, we have instead of
say 'tcp' string being retained the above default string being pulled from
somewhere (we have not been able to find it in the source code). (see jpeg 05
in the attachment)
So this is a task for all those Linux gurus out there: could you please make it
behave the same way it behaves under Windows.
You are receiving this mail because:
- You are watching all bug changes.