syaakov
commented
2 years ago @doonhammer You need to activate GTPU with loopback mode as Hanoch suggested here: https://github.com/cisco-system-traffic-generator/trex-core/issues/837#issuecomment-1098763409
You can read more about loopback mode with GTPU here: https://trex-tgn.cisco.com/trex/doc/trex_astf.html#_tutorial_gtpu_loopback_mode
Thanks for getting the new GTP-U version out.
The question is, can I use GTP-U mode with tunables. I follow the steps below and while I see truncated inner flows on the DUT and a GTP-U session however the throughput is very low compared to GTPU --off
My DUT is a firewall acting as a "dump in the wire" so it makes not changes to either the outer GTP-U tunnel or the inner flows. In my DUT logs I see the correct flows and I am not seeing any errors so it appears as if everything is working correctly. I am using Mellanox 100Gbps NICS on Centos 8. Running without GTP-U everything works as expected.
I set the server up with $ sudo ./t-rex-64 -i --astf --software --tso-disable -c 16
The client I go through the following steps:
$ ./trex-console
trex> tunnel --type gtpu trex> tunnels_topo load -f astf/gtpu_topo.py trex> start -f astf/http_eflow.py -m 100 -d 240 -t size=2048,loop=100
I have edited http_eflow.py to remove the limit=1.