[Guy Harris <guy@xxxxxxxxxx>]

On Thu, Jun 20, 2002 at 04:46:08PM +0200, Marco van den Bovenkamp wrote:
> Try 'debug ip packet dump' (undocumented, sadly),

While doing a Google search for "debug ip packet dump" to try to find
something describing the format of that command's output, I came across:

	http://www.ethereal.com/lists/ethereal-dev/200010/msg03402.html

which warns about "debug ip packet dump":

	I would *strongly* recommend against using this command unless
	you really know what you're doing and/or don't mind a router
	reboot.

	It is very easy to lose control of the router, because it can
	saturate both the serial link and the CPU given sufficient load
	on the circuits, and you may need physical access to the router
	to recover from this condition.  If you're lucky, the task gets
	killed by the executive, if not, the router locks up.

	I've seen someone do this to a router in South Africa.  He
	didn't appreciate my suggestion he should bike over there and
	fix it.

	The SNMP capture has resource usage limitations built in; I'd
	suggest using that if this functionality is required.