• Containers for test usage
  • NetworkManager
    • NetworkManager on CentOS Stream 10
    • NetworkManager on CentOS Stream 9
  • 802.1X Authentication
  • IPSec
    • IPSec using PSK authentication
    • IPSec using RSA authentication
    • IPSec using PKI authentication
    • IPSec P2P connection
    • IPSec Site-to-Site connection
    • IPSec Transport connection (p2p only)
    • IPSec Host-to-Site connection
    • IPSec IPv4 in IPv6 and IPv6 in IPv4 connection

The containers are stored in (https://quay.io/repository/nmstate/test-env)

All files licensed under Apache 2.0.

Containers for test usage

NetworkManager

NetworkManager on CentOS Stream 10

sudo ./run.sh nm c10s

NetworkManager on CentOS Stream 9

sudo ./run.sh nm c9s

802.1X Authentication

sudo ./run.sh 802_1x
# Afterwards, you may use `802_1x_cli` interface for 802.1x authentication.

Please be aware the container is purely authenticator, it has NO firewall rule to drop unauthenticated packet. You may use check hostapd log to know whether client is authenticated. Example of log of authenticated client:

Feb 27 07:01:31 802-1x-srv.example.org hostapd[53]: 802_1x_srv: STA
00:23:45:67:ef:bc IEEE 802.1X: authenticated - EAP type: 0 (unknown)

IPSec

By default, this script will create both server and client containers.

Passing --server-only will only create server container and load IPSec keys to local ipsec database.

IPSec using PSK authentication

sudo ./run.sh ipsec psk

IPSec using RSA authentication

sudo ./run.sh ipsec rsa

IPSec using PKI authentication

sudo ./run.sh ipsec cert

IPSec P2P connection

sudo ./run.sh ipsec p2p

IPSec Site-to-Site connection

sudo ./run.sh ipsec site2site

IPSec Transport connection (p2p only)

sudo ./run.sh ipsec transport

IPSec Host-to-Site connection

sudo ./run.sh ipsec host2site

IPSec IPv4 in IPv6 and IPv6 in IPv4 connection

sudo ./run.sh ipsec mix46