Wireshark-bugs: [Wireshark-bugs] [Bug 5036] TShark capture file to text conversion gets malforme
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5036
--- Comment #7 from krains <ken.rains@xxxxxxxxxxx> 2010-07-23 13:59:06 PDT ---
we have been able to run tshark using one profile (actually several profiles to
test) which gives an output file with the same results (few malformed packets).
the commands we used are:
DOS> path=\program files\wireshark;%path%
# this puts tshark in the path so it can run
DOS> tshark -r openicshop1st20000.pcap -C test1 > openicshop
# this runs tshark with profile test1 sending the output to a file called
openicshop
I have my wireshark default profile which does not cause malformed packets in
the output file.
I have a test1 profile which does not cause malformed packets.
I have a wireless profile which does cause malformed packets in the output
file.
My co-worker has his default profile which causes malformed packets.
My co-worker has a test1 profile which doers not cause malformed packets.
It looks like there is something in our configurations which cause the issue.
The Perl script we use runs tshark using the default profile.
So, we need both default profiles to run without causing malformed packets in
the output file.
What are some things we could check which may account for the different outputs
when using different profiles.
What do you suggest we do to eliminate the differences?
What do you suggest we do to enable no (extra) malformed packets to be in the
tshark output file?
thank you for any help you can provide.
ken rains
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
