rs/buildwireshark.html
>>
>> <https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/buildwireshark.html>
>>
>>
>> HTH... Dave
>>
>>
>>
>>
>>
>> From: mailto:vpp-dev@lists.fd.io>> on behalf of
>>
1000”, cause a transaction, “pcap dispatch trace
>> off”; then look at the resulting trace w/ a vpp-dispatch-trace enabled
>> wireshark. See
>> https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/buildwireshark.html
>>
>>
>>
>> HTH... Dave
gettingstarted/developers/buildwireshark.html>
>
>
> HTH... Dave
>
>
>
>
>
> From: mailto:vpp-dev@lists.fd.io>> on behalf of Andreas
> Schultz <mailto:andreas.schu...@travelping.com>>
> Date: Monday, April 29, 2019 at 9:31 AM
> To: "vpp-
developers/buildwireshark.html
>
>
>
> HTH... Dave
>
>
>
>
>
> *From: * on behalf of Andreas Schultz <
> andreas.schu...@travelping.com>
> *Date: *Monday, April 29, 2019 at 9:31 AM
> *To: *"vpp-dev@lists.fd.io"
> *Subject: *[vpp-dev] how to tra
Hi Andreas,
The tracing should work but because we’re reusing the syn packet to build the
syn-ack, it might not show correctly. Could you breakpoint the tcp4-output and
try to see if the trace code is hit?
As for the checksum, tcp only tags the packet with a request to have it
offloaded. If
: on behalf of Andreas Schultz
Date: Monday, April 29, 2019 at 9:31 AM
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] how to trace tcp4-output?
Hi,
I'm trying to debug a problem and need to trace tcp4-output with vpp 19.04.
So far I have tried it with "trace add tcp4-out
Hi,
I'm trying to debug a problem and need to trace tcp4-output with vpp 19.04.
So far I have tried it with "trace add tcp4-output 100 verbose", but that
is not producing the expected result. The trace buffer is always empty.
I was expecting that "trace add af-packet-input 100" would also trace
