Open NanerLee opened 7 years ago
Hello. This is definitely a bug. I will look into it, but I don't promise any ETA. Thank you for reporting it.
@martinkontsek Thanks! But in fact, same TLVs don't cause fatal error. The limit of UPDATE EOT packet size is the most important thing when topology table is too large.
I also see the RFC7868, but I don't find the description about this case. So I try to change the packet size, and the large packet will be some fragmentations in IP layer.
having multiple TLVs in one (update) packet is not and issue. Fragmenting the packet (going past link MTU) is defiantly and issue.
-d
It be a first update packet that has some tlvs to nbr.
when eigrp runing on many nodes, it will cause that the length of data written is more than MTU, and program will abort itself