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.

+++ This bug was initially created as a clone of Bug #1247315 +++

When listing listening sockets using 'ss -nlpe', there is no indication about whether an AF_INET6 socket is dual-stack capable, i.e. allows access from IPv4 as well. The following upstream patch solves this issue:

commit f32dc7467fee0b9e55c3fc6e2895d62e881dec55
Author: Phil Sutter <phil>
Date:   Wed Jun 24 13:07:20 2015 +0200

    ss: print value of IPV6_V6ONLY socket option if set
    
    If available and set, print 'v6only:1' for AF_INET6 sockets upon request
    of extended information. For IPv6 sockets bound to in6addr_any, this is
    the only way to determine if they will also accept IPv4 requests or not.
    
    Signed-off-by: Phil Sutter <phil>

*** Bug 1244824 has been marked as a duplicate of this bug. ***

Been told rhel-6.7 won't work, so targeting this at rhel-6.8.

Phil, as per your comments in the 6.8 spreadsheet
Too risky for 6.x 
Closing

If you disagree, please feel free to re-open