Re: [RFCv3 09/15] selftests: tcp_authopt: Test key address binding

[David Ahern]

On 8/24/21 2:34 PM, Leonard Crestez wrote:
> By default TCP-AO keys apply to all possible peers but it's possible to
> have different keys for different remote hosts.
> 
> This patch adds initial tests for the behavior behind the
> TCP_AUTHOPT_KEY_BIND_ADDR flag. Server rejection is tested via client
> timeout so this can be slightly slow.
> 
> Signed-off-by: Leonard Crestez <cdleonard@xxxxxxxxx>
> ---
>  .../tcp_authopt_test/netns_fixture.py         |  63 +++++++
>  .../tcp_authopt/tcp_authopt_test/server.py    |  82 ++++++++++
>  .../tcp_authopt/tcp_authopt_test/test_bind.py | 143 ++++++++++++++++
>  .../tcp_authopt/tcp_authopt_test/utils.py     | 154 ++++++++++++++++++
>  4 files changed, 442 insertions(+)
>  create mode 100644 tools/testing/selftests/tcp_authopt/tcp_authopt_test/netns_fixture.py
>  create mode 100644 tools/testing/selftests/tcp_authopt/tcp_authopt_test/server.py
>  create mode 100644 tools/testing/selftests/tcp_authopt/tcp_authopt_test/test_bind.py
>  create mode 100644 tools/testing/selftests/tcp_authopt/tcp_authopt_test/utils.py
> 

This should be under selftests/net as a single "tcp_authopt" directory
from what I can tell.