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

sysctl ra_honor_pio_life seems not working

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

    • No
    • Low
    • rhel-net-mgmt
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given a system administrator managing a RHEL host,

      When ra_honor_pio_life=1 is configured on an interface,

      Then NetworkManager must offer a connection-level override e.g ipv6.accept-ra-force=yes that sets accept_ra=1 safely under NM control.

      –
      Given a system administrator configuring a RHEL host with ipv6.accept-ra-force=yes set on a connection,

      When the interface receives IPv6 Router Advertisements with updated PIO and ra_honor_pio_life=1 is configured via sysctl,

      Then the kernel RA logic must remain active and the lifetime of the existing IPv6 address must be updated in-place to reflect the new RA values.

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given a system administrator managing a RHEL host, When ra_honor_pio_life=1 is configured on an interface, Then NetworkManager must offer a connection-level override e.g ipv6.accept-ra-force=yes that sets accept_ra=1 safely under NM control. – Given a system administrator configuring a RHEL host with ipv6.accept-ra-force=yes set on a connection, When the interface receives IPv6 Router Advertisements with updated PIO and ra_honor_pio_life=1 is configured via sysctl, Then the kernel RA logic must remain active and the lifetime of the existing IPv6 address must be updated in-place to reflect the new RA values. ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • All
    • None

      What were you trying to do that didn't work?

      When we set ra_honor_pio_life=1, valid life time received from RA is not set on the address.

      What is the impact of this issue to you?

      RA's valid lifetime value is not honored

      Please provide the package NVR for which the bug is seen:

      1. uname -r
        6.11.0-0.rc5.22.el10.x86_64

        How reproducible is this bug?:

      With validlife 7300 and preflife 3600 configured at radvd.conf, value applies rightly

      1. ip a s  enp7s0

      3: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

      link/ether 52:54:00:2a:5d:80 brd ff:ff:ff:ff:ff:ff

      inet 192.168.100.122/24 brd 192.168.100.255 scope global noprefixroute enp7s0

          valid_lft forever preferred_lft forever

      inet6 fd00:dead:beef:55::14f/128 scope global dynamic noprefixroute

          valid_lft 86236sec preferred_lft 86236sec

        • inet6 2001:cb90:1:0:3e92:b97a:c7c9:be5/64 scope global dynamic noprefixroute

         *    ** *valid_lft 7292sec preferred_lft 3592sec

      inet6 fe80::18f5:81dc:28cb:e81c/64 scope link noprefixroute

          valid_lft forever preferred_lft forever

       

      Then I set  validlife 5200 and preflife 3600 in radvd.conf and set net.ipv6.conf.enp7s0.ra_honor_pio_life to 1, I expected interface will inherit new valid lifetime of 5200 but it is not taken:

      1. sysctl -w net.ipv6.conf.enp7s0.ra_honor_pio_life=1

      net.ipv6.conf.enp7s0.ra_honor_pio_life = 1

      But we still valid lifetime as:

      3: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

      link/ether 52:54:00:2a:5d:80 brd ff:ff:ff:ff:ff:ff

      inet 192.168.100.122/24 brd 192.168.100.255 scope global noprefixroute enp7s0

          valid_lft forever preferred_lft forever

      inet6 fd00:dead:beef:55::14f/128 scope global dynamic noprefixroute

          valid_lft 85575sec preferred_lft 85575sec

      inet6 2001:cb90:1:0:3e92:b97a:c7c9:be5/64 scope global dynamic noprefixroute

          valid_lft 7049sec preferred_lft 3595sec

      inet6 fe80::18f5:81dc:28cb:e81c/64 scope link noprefixroute

          valid_lft forever preferred_lft forever

       

      Expected results

       

      I expected valid lifetime of 5200 should have been set on interface.  if my expectation or test results are not correct , can you correct me with my understanding?

      Actual results

        1. Screenshot from 2024-09-18 16-41-45.png
          Screenshot from 2024-09-18 16-41-45.png
          44 kB

              nm-team Network Management Team
              prpatel@redhat.com Prijesh Patel
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: