Hi Richard, Yes, this does happen only on output packet. After put "extensive" in the monitoring command, I haven't seen missing bytes anymore.
Thanks for comment. Regards, Nugroho On Mon, Jun 8, 2009 at 12:53 PM, Richard A Steenbergen <[email protected]>wrote: > > > Add "extensive" to your monitor traffic, see if you can get a complete > copy of the packet it doesn't like. IIRC this message (the one with "%d > bytes missing" specifically) only happens if the length in the IP header > doesn't agree with the length of the original packet as it was presented > to tcpdump (so regardless of snaplen). Also, does this happen only on > output packets? > > -- > Richard A Steenbergen <[email protected]> http://www.e-gerbil.net/ras > GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
