You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error occurs in Message.py in parsing method. Therefore the error message is not related to the UPDATE filter but to a possible bug in the parsing method.
Error occurs while trying to parse large TCP packets that are containing several BGP messages. Performing a TCP reassembly that is able to rebuild the segmented payloads into a single one is the solution for this kind of problem.
First off, I consider this library to be a holy grail and I applaud the folks that work on this project.
Is there anyone that can tell me the impact that this limitation has? Do large packets come through frequently enough for this issue to warrant re-adding the "high priority" label? Would love to help work out the issues with it. Any help and/or attention on this is appreciated. Thanks!
(new)cdietzel@flowbox:/jbod3/users/cdietzel/blackholing/32_accept$ zcat /some.pcap.gz | pbgpp.py - --filter-message-type UPDATE --filter-next-hop 80.81.193.66
[Message.py:92 - __parse() ] unpack requires a string argument of length 10
[Message.py:92 - __parse() ] unpack requires a string argument of length 10
[Message.py:92 - __parse() ] unpack requires a string argument of length 10
The text was updated successfully, but these errors were encountered: