Daniel Jakots wrote: > Our scapy is old. Here's a diff to update it to latest stable. > Upstream moved to github. > > While talking with them, they advised me to get ethertypes somewhere > else than the website [1]. As it's the same name but with different > checksum, you'll have to use REFETCH=true. The difference with the > previous file are "+RARP 8035 # Reverse ARP [RFC903]", a couple of > space/tabs fixes and another link in the comment. > > If you do make test, it will hang and if you ^C it will simply stop. If > you go in scapy-2.3.2 and do `python2.7 scapy/tools/UTscapy.py -t > test/regression.uts -f html -l -o /tmp/scapy_regression_test.html` it > will hang but just ^C a couple of times and then it finishes. I've the > same behaviour with the current scapy we have in port (2.1.0). > > On 2.1.0/amd64: > PASSED=698 FAILED=58 > on 2.3.2/amd64: > PASSED=739 FAILED=28 > on 2.3.2/i386: > PASSED=739 FAILED=28 > on 2.3.2/i386 with root: > PASSED=748 FAILED=19 > > [1]: https://twitter.com/pi3rre/status/689716600056987648
Does it hang in RARP-reading code? I came across a potential bug in our RARP yesterday. Currently working on it with a few other people.
