Bug #3943
closed
dump: uncaught exception "unrecognized field 4 cannot be ignored"
Added by Junxiao Shi over 7 years ago.
Updated almost 6 years ago.
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
A similar case: hobo1486075800.pcap causes ndndump to terminate with ERROR: TLV length exceeds buffer length.
- Assignee set to Alex Afanasyev
Just curious. Are these simply invalid packets?
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.
- Assignee changed from Alex Afanasyev to Davide Pesavento
- Start date deleted (
02/02/2017)
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...
- Status changed from New to Code review
- % Done changed from 0 to 100
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.
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by