Red Hat Bugzilla – Bug 74336
Logging doesn't display IPv6 addresses
Last modified: 2008-02-13 20:24:06 EST
Description of problem:
Connecting to IMAP or POP over IPv6 works, but logging don't display IPv6 addresses
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1) enable IPv6 on system
2) enable IMAP or POP service on xinetd.d
3) restart xinetd
Sep 20 20:36:53 gate imapd: Authenticated user=peter host=NON-IPv4
Sep 20 20:32:10 gate ipop3d: Auth user=peter host=NON-IPv4 nmsgs=1/1
Expected Results: Logging of IPv6 addresses
Mho: bug can be closed with cantfix (outdated version of OS)
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.
If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been
If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.
Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.
I hoped, this bug was fixed since 2002, but testing this now in FC5 I found the
issue still exists - will change release:
Aug 5 10:52:31 gatemuc imapd: Login user=peter host=[NON-IPv4]
Aug 5 10:52:38 gatemuc imapd: Logout user=peter host=[NON-IPv4]
Used xinetd config:
socket_type = stream
wait = no
user = root
server = /usr/sbin/imapd
log_on_success += HOST DURATION
log_on_failure += HOST
disable = no
flags = IPv6
Tested version: uw-imap-2004g-4.fc5.2
Testing uw-imap-2006g-2.fc6 I found, that this issue is finally solved now:
Apr 11 14:20:15 s xinetd: START: pop3 pid=5331 from=::ffff:127.0.0.1
Apr 11 14:20:25 s xinetd: EXIT: pop3 status=0 pid=5331 duration=10(sec)
Apr 11 14:20:29 s xinetd: START: pop3 pid=5333 from=::1
Apr 11 14:20:38 s xinetd: EXIT: pop3 status=0 pid=5333 duration=9(sec)
So this bug can be closed now.
Closing the bug as requested by the bug reporter.