From 08eb2bb205f998a75dacd1f3b999ec1a10160b35 Mon Sep 17 00:00:00 2001 From: Dave Barach Date: Wed, 15 Apr 2020 09:34:43 -0400 Subject: pg: set vnet buffer flags in pg streams See .../extras/pg/checksum_offload.pg for a nontrivial example, which deliberately sets bogus ip and udp checksums in the generated packets, then fixes the mess with (software emulated) hardware checksum offload. Validated via "pcap dispatch trace on max 1000 buffer-trace pg-input 100". Packets stuffed into loop1-output have the configured bogus ip and udp checksums. vnet_calc_checksums_inline(...) fixes the checksums, which are correct when packets visit loop1-tx. The packet generator is a dumb robot in this regard. If you ask for a ridiculous flag combination - example: ip4 and ip6 - your mileage may vary. Type: feature Signed-off-by: Dave Barach Change-Id: I6d9e790f373bcd9e445a89113ca8e4c8f9aa9419 --- extras/pg/ip6_simple.pg | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 extras/pg/ip6_simple.pg (limited to 'extras/pg/ip6_simple.pg') diff --git a/extras/pg/ip6_simple.pg b/extras/pg/ip6_simple.pg new file mode 100644 index 00000000000..023bde6837f --- /dev/null +++ b/extras/pg/ip6_simple.pg @@ -0,0 +1,12 @@ + +packet-generator new { + name x + limit 5 + size 128-128 + interface local0 + node ip6-lookup + data { + ICMP: db00::1 -> db00::2 + incrementing 30 + } +} -- cgit 1.2.3-korg