Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-1407

nm-settings-keyfile confusion

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • NetworkManager-1.45.3-1.el9
    • Medium
    • 3
    • rhel-net-mgmt
    • ssg_networking
    • 7
    • 1
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • Documentation and Logging, NMT - RHEL 8.10/9.4 DTM 00, NMT - RHEL 8.10/9.4 DTM 2
    • Hide

      Given a system administrator working with a system that uses NetworkManager and keyfile configuration,
      When the system administrator refers to the "nm-settings-keyfile" documentation, 
      Then the documentation should provide clear instructions on how to configure routing rules.

      Defintion of Done

      • The nm-settings-keyfile documentation contains instructions on how to configure routing rules
      Show
      Given a system administrator working with a system that uses NetworkManager and keyfile configuration, When the system administrator refers to the "nm-settings-keyfile" documentation,  Then the documentation should provide clear instructions on how to configure routing rules. Defintion of Done The nm-settings-keyfile documentation contains instructions on how to configure routing rules
    • Pass
    • None
    • If docs needed, set a value
    • None
    • 0

      Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/assembly_manually-creating-networkmanager-profiles-in-key-file-format_configuring-and-managing-networking

      Section Number and Name: all

      Describe the issue:

      • I'm using the "keyfile" description for NetworkManager (a network technology I'm new to) which is supposed to be the "new" way to configure networking in the next version of RHEL according to the above document. However, the way to write these files is not always clear with a given nmcli command. Some fields are unspecified, such as:

      "ipv4.route1", "ipv4.route2", ... being the equivalent to an array of routes specified via:

      nmcli connection modify ... +ipv4.routes foo

      The man page (nm-settings-keyfile) *kinda* touches on weirdness to route specification but it's not at all clear.

      "routing-rules" is another example.

      Also note, the man page (nm-settings-keyfile) confuses things further:

      > More information of the generic key file format can be found at GLib key file format[1] (Lines beginning with a '#' are comments, lists are separated by character ; etc.).

      which would lead one to think that a list field like "routes" could be specified like:

      routes=x.x.x.x/24,x.x.x.1;y.y.y.y/24,y.y.y.1

      but this is not accepted.

      I have found that the only way to discover this information is to continue using nmcli for configuring connections but modify /etc/NetworkManager/NetworkManager.conf to use keyfile format:

      > [main]
      > plugins=keyfile

      and then inspect how it encodes commands in the keyfile.

      Acceptance Criteria:
      Given a system administrator working with a system that uses NetworkManager and keyfile configuration,
      When the system administrator refers to the "nm-settings-keyfile" documentation, 
      Then the documentation should provide clear instructions on how to configure routing rules.

      Defintion of Done

      • The nm-settings-keyfile documentation contains instructions on how to configure routing rules

              ihuguet@redhat.com Inigo Huguet
              pdonnell@redhat.com Patrick Donnelly
              Network Management Team Network Management Team
              David Jaša David Jaša
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: