Bug 124625
Summary: | IPv6 support missing | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan <ml> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | harkness, mattdm, thomasz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-27 17:28:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dan
2004-05-28 00:47:10 UTC
*** Bug 126519 has been marked as a duplicate of this bug. *** Even better, this should be able to contact the server using IPv4. I have a mail server that is accessible over both IPv6 and IPv4. Evolution had always worked fine before. A recent update in Fedora Devel (likely in glibc packages) has caused the IPv6 address to be returned before the IPv4 address in lookups. (I can see this as telnet connections attempt the IPv6 address first, fails, then tries the IPv4 address, when it had always tried the IPv4 address first before last week.) I believe what is happening is that Evolution is getting the IPv6 address, failing to connect, and not trying the second address. This not only causes problems with IPv6, but for _any_ setup where fail over is necessary. Services often have several addresses listed in case the first ones fail. As this bug stands, it is impossible to use Evolution on an IPv6-enabled host. This should be (IMO) a major bug, as it is a major component of most Fedora desktops and needs to work independent of IPv6 network availability. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. Closing per lack of response. Also note that FC1 and FC2 are no longer supported even by Fedora Legacy. If this still occurs on FC3 or FC4, please assign to that version and Fedora Legacy. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. |