summaryrefslogtreecommitdiffstats
path: root/VNFs/UDP_Replay
diff options
context:
space:
mode:
authorXavier Simonart <xavier.simonart@intel.com>2017-11-09 15:57:11 +0100
committerXavier Simonart <xavier.simonart@intel.com>2017-11-15 19:05:17 +0100
commit4be177d0ef2813a20651d1a54991d25f3a66a090 (patch)
treea010ecadbb2654562b7c247e0f81a8c46b02a564 /VNFs/UDP_Replay
parentc5dfa2ba7c21dac5ff6895f6e0fa2dc1dcc50cc1 (diff)
Add support for nop mode with l3 submode
The l3 submode was not supported in nop mode, as the nop mode uses some specific nop thread (and not generic). When L3 is specified, the nop mode must use the generic thread. In addition the l3 submode is implemented differently than other submodes. It is not supported through task_init structures (i.e. each task does not have to explicitely tell that it supports l3 submode). But this prevented to run both a nop with no submode and a nop with a l3 submode. Note that nop with l3 is usually not very useful - it handles arp (requests and response) but as nop, it does not swap IP addresses. So with a real switch, the packets transmitted will be received back... and l3 mode is usually mainly usefull when using a switch. However, there is at least one nop mode where l3 submode makes sense: when the nop does not transmit. In such cases, for instace used in conjunction with a gen l3, the nop receives all packets and forward the arp requests and responses to the master for handling. Change-Id: I992121db285ba25a11cbb494092a6afc6fe55a58 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
Diffstat (limited to 'VNFs/UDP_Replay')
0 files changed, 0 insertions, 0 deletions