Description of problem:
Trying to compare two pcap files and I get the following error:
Traceback (most recent call last):
File "/usr/bin/pcapdiff", line 5, in <module>
File "/usr/share/pcapdiff/pcapdiff.py", line 263, in <module>
next['remote'] = get_packet(pcap_remote)
File "/usr/share/pcapdiff/pcapdiff.py", line 152, in get_packet
spacket = parse_and_save(packet)
File "/usr/share/pcapdiff/pcapdiff_helper.py", line 89, in parse_and_save
spacket['ip_total_length'] = 256*ord(ip_packet)+ord(ip_packet)
IndexError: string index out of range
Version-Release number of selected component (if applicable):
'uname -a' is:
Linux jhorne 188.8.131.52-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Occurs every time with the 2 pcap files I have.
Steps to Reproduce:
See error above.
No errors should be output.
Would you mind attaching the two files?
I can, but they are 12MB and 54MB in size respectively. Do you really want me to attach them?
Do you have any webspace you can put them on briefly? Or do the files possibly contain anything sensitive? If not, see if BZ will let you attach them. Not sure what the limit is.
Created attachment 431820 [details]
First compressed pcap file.
Created attachment 431823 [details]
Second compressed pcap file.
Okay, both files should now be attached.
Sorry for the delay, which is local and which is remote, and what were the IPs for each?
First attachment (tcpdump file) is 'local'. Its IP address is 184.108.40.206. The remote IP address is 220.127.116.11.
Interesting. From everything I can figure, I wonder if there isn't a problem with one of the files. The error makes it look like there's a chunk missing from a packet and it's not handling it gracefully. Can you produce another set of dumps that crash pcapdiff?
No, not really. This was 6 months ago when we were trying to resolve a particular problem. Things have now moved on: the problem was resolved (I gather), and one of the servers involved now performs a different function. So not really possible to get any other dumps from them.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.