Bug #3943
closed
dump: uncaught exception "unrecognized field 4 cannot be ignored"
100%
Description
Steps to reproduce:
ndndump -r hobo1486071022.pcap
Actual: program terminates with ERROR: unrecognized field 4 cannot be ignored
Expected: invalid packets, if any, do not cause program termination
Files
Updated by Junxiao Shi about 7 years ago
- File hobo1486075800.pcap hobo1486075800.pcap added
A similar case: hobo1486075800.pcap causes ndndump to terminate with ERROR: TLV length exceeds buffer length.
Updated by Alex Afanasyev about 7 years ago
- Assignee set to Alex Afanasyev
Just curious. Are these simply invalid packets?
Updated by Junxiao Shi about 7 years ago
Just curious. Are these simply invalid packets?
Probably not. Both pcap traces are captured on NDN testbed Arizona router using port 6363 filter. I just stripped the trace down to one second that contains the troublemaker.
Updated by Davide Pesavento over 5 years ago
- Assignee changed from Alex Afanasyev to Davide Pesavento
- Start date deleted (
02/02/2017)
Updated by Davide Pesavento over 5 years ago
ERROR: unrecognized field 4 cannot be ignored
This is caused by a missing try-catch around lp::Packet constructor. I don't know how you managed to capture a packet with an LP field of type 4 since we don't officially define any such field...
Updated by Davide Pesavento over 5 years ago
- Status changed from New to Code review
- % Done changed from 0 to 100
Updated by Junxiao Shi over 5 years ago
I don't know how you managed to capture a packet with an LP field of type 4 since we don't officially define any such field...
I kept tcpdump running for several days, fed the traffic to ndndump, and narrowed down to a shorter file that causes a crash.
The troublemakers might come from a non standard compliant node. I didn’t know how to handwrite a pcap back then.
Updated by Davide Pesavento over 5 years ago
- Status changed from Code review to Closed