On (2013-11-26 12:16 +0100), Antonio Prado wrote: > > if I set the maxas-limit, whenever the router receives a longer path, it > complains: > > 020250: Nov 26 12:09:52: %BGP-6-MSGDUMP_LIMIT: unsupported or > mal-formatted message received from xx.xx.xxx.243:
I'm guessing this might happen because max-prefix bites while packet is being received. So remaining packet is incomplete and thus invalid. I'm not 100% sure about this, but if you put that hexdump through 'text2pcap', I'm betting it won't be recognized as BGP until you fix the 'size' bytes. Interestingly, I don't believe this behaviour could be seen in IOS-XR or JunOS or such, since it's quite untypical for userland process to start processing packet before it's received. But IOS specifically has dedicated TCP/IP implementation for BGP and another implementation for rest of the system. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
