Hi Stefan, Thank you for taking the time to inspect this issue that was neglected for a long time.
The wrong NAS-IP addresses I encountered were usually a semi random address from the same class B as the IP used by the host. That IP was not an existing in the system. The host is properly registered in DNS, both forward and reverse. The wrong NAS-IP is sometimes registered in DNS but allocated to other hosts. Since the issue was resolved upsteram - can Ubuntu update the package to resolve this issue? The issue was not closed upstream as a configuration error, please see: https://github.com/FreeRADIUS/pam_radius/issues/100#issuecomment-2329314957 "The solution here is to fix the OS so that it returns the correct IP address for the host. The PAM module is just doing OS API calls to get the IP, and definitely does not "invent" any IP, or get any IP "wrong". It asks the OS for an IP, and then uses whatever IP the OS has returned." I can try setting up a clean OS install for testing if this bug was resolved by some patch since June 2025 when I last encountered it. Would this be helpful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078938 Title: Incorrect NAS-IP-Address Attribute (4) Value in PAM RADIUS Module on Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-radius-auth/+bug/2078938/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
