Comment # 3
on bug 12236
from Petr Sumbera
This can be easily reproduced with tshark (sparc):
--------------------------------------------------
$ tshark -r ~/mytest.dat | wc -l
37
$ tshark -r ~/mytest.dat -Y 'tcp.flags.reset eq 1' | wc -l
34
$ tshark -r ~/mytest.dat -Y 'tcp.flags.reset eq 0' | wc -l
34
While on intel everything works:
--------------------------------
$ tshark -r ~/mytest.dat -Y 'tcp.flags.reset eq 1' | wc -l
0
$ tshark -r ~/mytest.dat -Y 'tcp.flags.reset eq 0' | wc -l
34
And it's not problem of just 'reset' bit or 'tcp.flags':
--------------------------------------------------------------
(intel:)
$ tshark -r ~/mytest.dat -Y 'ip.flags.mf == 0' | wc -l
34
$ tshark -r ~/mytest.dat -Y 'ip.flags.mf == 1' | wc -l
0
(sparc:)
$ tshark -r ~/mytest.dat -Y 'ip.flags.mf == 0' | wc -l
34
$ tshark -r ~/mytest.dat -Y 'ip.flags.mf == 1' | wc -l
34
You are receiving this mail because:
- You are watching all bug changes.
