tests: net: config: Add tests for yaml based configuration

Add simple unit tests that verify that options specified
in yaml file can be used to configure network stack.

Signed-off-by: Jukka Rissanen <[email protected]>

Author: jukkar

tests/net/lib/config/CMakeLists.txt

@@ -0,0 +1,9 @@
+# SPDX-License-Identifier: Apache-2.0
+
+cmake_minimum_required(VERSION 3.20.0)
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(iface)
+
+target_include_directories(app PRIVATE ${ZEPHYR_BASE}/subsys/net/ip)
+FILE(GLOB app_sources src/*.c)
+target_sources(app PRIVATE ${app_sources})

tests/net/lib/config/network-config.yaml

@@ -0,0 +1,156 @@
+# This is a network configuration data that is used to validate that the
+# configuration can be applied automatically when the device boots.
+#
+# In this test, we have multiple devices and network interface. The test
+# enables the network config library, it reads the configuration when the
+# device boots, and then the test checks that the configuration is applied
+# correctly to the network stack.
+#
+# Some of the network interfaces are dummy ones and some Ethernet ones.
+# The Ethernet devices are needed to validate the VLAN configuration.
+# The virtual interface is used to verity that it can be bound to some
+# other network interface.
+#
+networking:
+  interfaces:
+    # First Ethernet interface in the system. We change its name in the
+    # testing process.
+    - &main-interface
+      name: eth0
+      set_name: test-eth0
+      set_default: true
+      ipv6:
+        status: true
+        ipv6_addresses:
+          - 2001:db8:110::1
+        ipv6_multicast_addresses:
+          - ff05::114
+          - ff15::115
+        prefixes:
+          - address: "2001:db8::"
+            len: 64
+            lifetime: 1024
+        hop_limit: 48
+        multicast_hop_limit: 2
+        dhcpv6:
+          status: true
+          do_request_address: true
+          do_request_prefix: false
+      ipv4:
+        status: true
+        ipv4_addresses:
+          - 192.0.2.10/24
+        ipv4_multicast_addresses:
+          - 234.0.0.10
+        gateway: 192.0.2.1
+        time_to_live: 128
+        multicast_time_to_live: 3
+        dhcpv4:
+          status: true
+        ipv4_autoconf:
+          status: true
+
+    # For this interface we do not know its name, but we know what device
+    # it is bound to.
+    - &device-interface
+      device_name: eth_2
+      set_name: test-eth1
+      flags:
+        - NET_IF_NO_AUTO_START
+        - NET_IF_PROMISC
+      ipv4:
+        status: true
+        ipv4_addresses:
+          - 192.0.2.22/24
+        gateway: 192.0.2.2
+        time_to_live: 10
+        multicast_time_to_live: 1
+        dhcpv4:
+          status: false
+        dhcpv4_server:
+          status: true
+          base_address: 192.0.2.32
+
+    # This virtual interface bound to the first one
+    - name: virt0
+      bind_to: *main-interface
+      flags:
+        - NET_IF_IPV6_NO_MLD
+        - NET_IF_NO_AUTO_START
+        - ^NET_IF_PROMISC
+      ipv6:
+        status: true
+        ipv6_addresses:
+          - 2001:db8:111::2
+      ipv4:
+        status: false
+
+    # This VLAN interface that attaches to second Ethernet interface
+    - &vlan-interface
+      set_name: vlan0
+      bind_to: *device-interface
+      vlan:
+        status: true
+        tag: 2432
+      ipv4:
+        status: true
+        dhcpv4:
+          status: true
+
+    # This 2nd VLAN interface is attached to one of the Ethernet interfaces
+    - set_name: vlan1
+      bind_to: *main-interface
+      vlan:
+        status: true
+        tag: 1234
+      ipv4:
+        status: true
+        dhcpv4:
+          status: true
+
+    # This virtual interface bound to the VLAN interface
+    - name: virt1
+      set_name: virt-over-vlan
+      bind_to: *vlan-interface
+      ipv6:
+        status: true
+        ipv6_addresses:
+          - 2001:db8:abcd::11
+
+    # This interface IPv4 configuration is set to disabled
+    # in which case its IPv4 configuration is skipped
+    - name: dummy0
+      ipv6:
+        status: true
+      ipv4:
+        status: false
+        ipv4_addresses:
+          - 192.2.0.2
+        gateway: 192.2.0.1
+        time_to_live: 10
+        multicast_time_to_live: 2
+
+    # This interface IPv4 and IPv6 configuration are both disabled.
+    # Basically the interface is non functional for IP connectivity.
+    - name: dummy1
+      ipv6:
+        status: false
+      ipv4:
+        status: false
+
+  ieee_802_15_4:
+    status: true
+    pan_id: 0xabcd
+    channel: 26
+    tx_power: 1
+    security_key: [0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9,
+                   0xca, 0xcb, 0xcc, 0xcd, 0xce, 0xcf]
+    security_key_mode: 0
+    security_level: 1
+    ack_required: true
+    bind_to: *device-interface
+
+  sntp:
+    server: sntp.foo.bar
+    timeout: 30
+    bind_to: *vlan-interface

tests/net/lib/config/prj.conf

@@ -0,0 +1,51 @@
+CONFIG_NETWORKING=y
+CONFIG_NET_TEST=y
+CONFIG_ZTEST=y
+CONFIG_NET_LOG=y
+CONFIG_LOG=y
+CONFIG_MAIN_STACK_SIZE=2048
+
+CONFIG_NET_IPV6=y
+CONFIG_NET_IPV4=y
+CONFIG_NET_IPV6_DAD=n
+CONFIG_NET_IPV6_MLD=n
+CONFIG_NET_IPV6_MAX_NEIGHBORS=8
+CONFIG_NET_IPV6_ND=n
+CONFIG_NET_MAX_NEXTHOPS=8
+CONFIG_NET_IPV4_AUTO=n
+CONFIG_NET_IPV4_ACD=n
+CONFIG_NET_DHCPV4=y
+CONFIG_NET_DHCPV4_SERVER=y
+CONFIG_NET_DHCPV4_SERVER_ADDR_COUNT=32
+CONFIG_NET_DHCPV6=y
+
+CONFIG_NET_UDP=y
+CONFIG_NET_TCP=y
+
+CONFIG_NET_MAX_CONTEXTS=4
+
+CONFIG_NET_L2_DUMMY=y
+CONFIG_NET_L2_ETHERNET=y
+CONFIG_NET_L2_ETHERNET_MGMT=y
+CONFIG_NET_L2_VIRTUAL=y
+CONFIG_NET_INTERFACE_NAME_LEN=15
+
+CONFIG_NET_VLAN=y
+CONFIG_NET_VLAN_COUNT=2
+
+CONFIG_ENTROPY_GENERATOR=y
+CONFIG_TEST_RANDOM_GENERATOR=y
+
+CONFIG_NET_PKT_TX_COUNT=10
+CONFIG_NET_PKT_RX_COUNT=10
+CONFIG_NET_BUF_RX_COUNT=10
+CONFIG_NET_BUF_TX_COUNT=10
+
+CONFIG_NET_IF_MAX_IPV6_COUNT=8
+CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=6
+CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=4
+CONFIG_NET_IF_UNICAST_IPV4_ADDR_COUNT=2
+CONFIG_NET_IF_MAX_IPV4_COUNT=8
+
+CONFIG_NET_CONFIG_SETTINGS=y
+CONFIG_NET_CONFIG_AUTO_INIT=y