diff --git a/.README.html b/.README.html index 0dc6008a..f4b771fb 100644 --- a/.README.html +++ b/.README.html @@ -187,6 +187,8 @@

Contents

  • autoconnect
    • +
  • autoconnect_retries
  • mac
  • cloned_mac
    • @@ -259,6 +261,20 @@

    Introduction

    settings are introduced.

    The network role supports two modules: network_connections and network_state.

    +

    Since the backend of network_state is Nmstate, the +network_state modules represents the future direction for +the network role, aiming to provide a more streamlined and reliable way +of managing network. As a result, the focus is on promoting the use of +network_state over the network_connections +variable to ensure better consistency and functionality moving forward. +Additionally, most of the features currently supported in NetworkManager +are also available with network_state. For more information +and examples on how to configure the network using Nmstate schema in +network_state variable, please refer to the official +documentation at nmstate.io. For +detailed syntax and explanations of each parameter, visit nmstate's API +documentation.

    For each host a list of networking profiles can be configured via the network_connections variable.

    +

    autoconnect_retries

    +

    The number of times a connection should be tried when autoactivating +before giving up. Zero means forever, -1 means the global default in +NetworkManager (4 times if not overridden). Setting this to 1 means to +try activation only once before blocking autoconnect. Note that after a +timeout, NetworkManager will try to autoconnect again.

    +

    mac

    The mac address is optional and restricts the profile to be usable only on devices with the given MAC address. mac @@ -803,6 +829,15 @@

    ip

  • gateway4 and gateway6

    The default gateway for IPv4 (gateway4) or IPv6 (gateway6) packets.

    • +

  • wait_ip

    +

    The property controls whether the system should wait for a specific +IP stack to be configured before considering the connection activated. +It can be set to "any", "ipv4","ipv6," or "ipv4+ipv6". When set to +"any," the system considers the connection activated when any IP stack +is configured. "ipv4" ensures the system waits for IPv4 configuration, +while "ipv6" ensures the system waits for IPv6 configuration. The +"ipv4+ipv6" option requires both IPv4 and IPv6 to be configured before +the connection is considered activated.

  • ipv4_ignore_auto_dns and ipv6_ignore_auto_dns

    If enabled, the automatically configured name servers and search @@ -1440,38 +1475,79 @@

    Examples prefix-length: 64 autoconf: false dhcp: false -

    Configuring the route:

    +

    Configuring the Linux bridge with custom multicast, stp options, +along with a port with specific stp settings:

    network_state:
   interfaces:
-    - name: eth1
-      type: ethernet
+    - name: br0
+      type: linux-bridge
       state: up
-      ipv4:
-        enabled: true
-        address:
-          - ip: 192.0.2.251
-            prefix-length: 24
-        dhcp: false
-
-  routes:
-    config:
-      - destination: 198.51.100.0/24
-        metric: 150
-        next-hop-address: 192.0.2.251
-        next-hop-interface: eth1
-        table-id: 254
    -

    Configuring the DNS search and server:

    + bridge: + options: + gc-timer: 29657 + group-addr: 01:80:C2:00:00:00 + group-forward-mask: 0 + group-fwd-mask: 0 + hash-max: 4096 + hello-timer: 0 + mac-ageing-time: 300 + multicast-last-member-count: 2 + multicast-last-member-interval: 100 + multicast-membership-interval: 26000 + multicast-querier: false + multicast-querier-interval: 25500 + multicast-query-interval: 12500 + multicast-query-response-interval: 1000 + multicast-query-use-ifaddr: false + multicast-router: auto + multicast-snooping: true + multicast-startup-query-count: 2 + multicast-startup-query-interval: 3125 + stp: + enabled: false + forward-delay: 15 + hello-time: 2 + max-age: 20 + priority: 32768 + vlan-protocol: 802.1q + port: + - name: eth1 + stp-hairpin-mode: false + stp-path-cost: 100 + stp-priority: 32 +

    Configuring the route:

    network_state:
-  dns-resolver:
-    config:
-      search:
-        - example.com
-        - example.org
-      server:
-        - 2001:4860:4860::8888
-        - 8.8.8.8
    + interfaces: + - name: eth1 + type: ethernet + state: up + ipv4: + enabled: true + address: + - ip: 192.0.2.251 + prefix-length: 24 + dhcp: false + + routes: + config: + - destination: 198.51.100.0/24 + metric: 150 + next-hop-address: 192.0.2.251 + next-hop-interface: eth1 + table-id: 254 +

    Configuring the DNS search and server:

    +
    network_state:
+  dns-resolver:
+    config:
+      search:
+        - example.com
+        - example.org
+      server:
+        - 2001:4860:4860::8888
+        - 8.8.8.8

    Invalid and Wrong Configuration

    The network role rejects invalid configurations. It is diff --git a/CHANGELOG.md b/CHANGELOG.md index 13b93aab..d9cd21fe 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,23 @@ Changelog ========= +[1.17.0] - 2024-10-30 +-------------------- + +### New Features + +- feat: Support autoconnect_retries (#737) +- feat: Support `wait_ip` property (#741) + +### Other Changes + +- docs: Explain where network state examples originate (#734) +- ci: Add tags to TF workflow, allow more [citest bad] formats (#738) +- ci: ansible-test action now requires ansible-core version (#739) +- ci: add YAML header to github action workflow files (#740) +- docs: Promote `network_state` variable as the future for network management (#742) +- refactor: Use vars/RedHat_N.yml symlink for CentOS, Rocky, Alma wherever possible (#744) + [1.16.5] - 2024-08-29 --------------------