aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/net/lib/py/ynl.py
diff options
context:
space:
mode:
authorAntonio Quartulli <[email protected]>2025-04-15 11:17:32 +0000
committerPaolo Abeni <[email protected]>2025-04-17 10:30:03 +0000
commita3aaef8cd1730381392dcc4868b437da7d9ad5ac (patch)
tree8f8d257d70726c8115cc1546757d3b07211c3900 /tools/testing/selftests/net/lib/py/ynl.py
parentovpn: implement multi-peer support (diff)
downloadkernel-a3aaef8cd1730381392dcc4868b437da7d9ad5ac.tar.gz
kernel-a3aaef8cd1730381392dcc4868b437da7d9ad5ac.zip
ovpn: implement peer lookup logic
In a multi-peer scenario there are a number of situations when a specific peer needs to be looked up. We may want to lookup a peer by: 1. its ID 2. its VPN destination IP 3. its transport IP/port couple For each of the above, there is a specific routing table referencing all peers for fast look up. Case 2. is a bit special in the sense that an outgoing packet may not be sent to the peer VPN IP directly, but rather to a network behind it. For this reason we first perform a nexthop lookup in the system routing table and then we use the retrieved nexthop as peer search key. Signed-off-by: Antonio Quartulli <[email protected]> Link: https://patch.msgid.link/[email protected] Reviewed-by: Sabrina Dubroca <[email protected]> Tested-by: Oleksandr Natalenko <[email protected]> Signed-off-by: Paolo Abeni <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/ynl.py')
0 files changed, 0 insertions, 0 deletions