RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When IPv6 is used connection between remote logging server and its clients, audit events have incorrect addr field (addr=0.0.0.0) instead of clients' addresses. 

Version-Release number of selected component (if applicable):

kernel-3.10.0-823.el7
audit-2.8.1-3.el7

How reproducible:

100%

Steps to Reproduce:

1. Configure remote server logging between server and client connected with IPv6 network [1].
2. Start auditd on both machines.
3. See DAEMON_ACCEPT event and its addr field.

[1] https://access.redhat.com/solutions/28676

Actual results:

node=CLIENT type=DAEMON_ACCEPT msg=audit(...): addr=0.0.0.0 port=60 res=success

Expected results:

node=CLIENT type=DAEMON_ACCEPT msg=audit(...): addr=<IP address of CLIENT> port=60 res=success

Additional info:

 * This is not really a regression since remote logging was not supported in 
   audit before.

 * Remote logging works, only addr field is incorrect.

 * When IPv6 is disabled:

   sysctl -w net.ipv6.conf.all.disable_ipv6=1
   sysctl -w net.ipv6.conf.default.disable_ipv6=1

   and IPv4 is enforced, addr field is set correctly.

Fixed in upstream commit 5344f96f.

IPv6 is used connection between remote logging server and its clients remains an issue even with IPv6 disabled.  

Kernel = 3.10.0-862.3.2.el7.x86_64
Audit = 2.8.1-3.el7.x86_64

Results: 
(Audit log) type=DAEMON_ACCEPT msg=audit (...) op=dup addr=0.0.0.0 port=60 res=no
(Syslog) audit_backlog=321 > audit_backlog_limit=320

Notes: 
Auditing will work for a brief period of time until the audit queue quickly fills up causing an audit backlog preventing any logs from being received.  Disabling the audit server's IPv6 in DNS provides a work-around allowing hosts to continue logging without the "addr=0.0.0.0" messages.

audit-2.8.4-1.el7 has been built to address this issue.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3237