From 8a6e1b190c63cc596aed33f84b5989b64d276423 Mon Sep 17 00:00:00 2001 From: jdenisco Date: Mon, 13 May 2019 12:40:21 -0400 Subject: docs: Update sphinx, requirements, support markdown tables Change-Id: Ie7c546f5720b10fe5423397204e1ab5c22d7a2ba Signed-off-by: jdenisco --- docs/usecases/contiv/VPPTRACE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/usecases/contiv/VPPTRACE.md') diff --git a/docs/usecases/contiv/VPPTRACE.md b/docs/usecases/contiv/VPPTRACE.md index 2b397427cb3..c9d2088266b 100644 --- a/docs/usecases/contiv/VPPTRACE.md +++ b/docs/usecases/contiv/VPPTRACE.md @@ -1,7 +1,7 @@ ## Using vpptrace.sh for VPP Packet Tracing VPP allows tracing of incoming packets using CLI commands `trace add` and `show trace` -as explained [here](VPP_PACKET_TRACING_K8S.html), but it is a rather cumbersome process. +as explained \[here\](VPP_PACKET_TRACING_K8S.html), but it is a rather cumbersome process. The buffer for captured packets is limited in size, and once it gets full the tracing stops. The user has to manually clear the buffer content, and then repeat the trace command to resume the packet capture, losing information about all packets received in the meantime. -- cgit 1.2.3-korg