diff options
author | 2020-04-20 23:25:22 +0200 | |
---|---|---|
committer | 2020-05-29 23:28:44 +0200 | |
commit | fa869940dd9bb459ac599fe80c26c9d3e720fd31 (patch) | |
tree | 67aefe7f36fad283ab690d5d0feae1a547a59487 /VNFs/DPPD-PROX/rx_pkt.c | |
parent | 6f898f1c73d630bf6e5e75ba1b30d261c8301d2a (diff) |
Add support for vdev tap devices
This commit adds support for the creation of tap devices.
To create a tap device, and associate it with a DPDK port,
add within the port section:
vdev=<tap_name>
local ipv4=<ip_assigned_to_port>
<tap_name> will appear as a kernel network device, with an IP <ip_assigned_to_port>
ARP packets received from the network on the DPDK interface will be forwarded to the kernel.
1st packet which needs to be generated to a new IP will cause an IP packet
to be sent to the kernel (using socket sendto) forcing the kernel to send an ARP_REQUEST.
In this commit, there is no notification from the kernel about ARP table changes.
This is subject to further commits.
Two config files, gen_tap.cfg and swap_tap.cfg have been created. They work one against each other.
*** Note however that they do not work if running within the same host
(with the port being connected back to back) ***
This is due to the fact that the kernel would bypass the ports and use local interface...
Change-Id: Iadeec0d99e3c693472ea44bdb9163a3bf97df2fa
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
Diffstat (limited to 'VNFs/DPPD-PROX/rx_pkt.c')
0 files changed, 0 insertions, 0 deletions