linuxdcpp-team team mailing list archive

[maksis <maksis@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

Consider the following case:

1. The client tries to connect to an address that has both A and AAAA entries
2. ::getaddrinfo returns the AAAA entry first
3. The client tries to connect via IPv6 but there's no IPv6 connectivity available (or it doesn't work for other reasons)
4. Socket::connect throws immediately instead of continuing with the A entry

I haven't seen this happening on Windows because it doesn't seem to
return the AAAA entry if there is no (public) IPv6 connectivity
available. However, Linux systems seem to generally return the AAAA
first by default, regardless of the available connectivity. The attached
patch should fix this issue.

** Affects: dcplusplus
     Importance: Undecided
         Status: New

** Attachment added: "Socket.cpp.patch"
   https://bugs.launchpad.net/bugs/1245179/+attachment/3892943/+files/Socket.cpp.patch

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1245179

Title:
  Resolving addresses with A and AAAA entries may fail in some cases

Status in DC++:
  New

Bug description:
  Consider the following case:

  1. The client tries to connect to an address that has both A and AAAA entries
  2. ::getaddrinfo returns the AAAA entry first
  3. The client tries to connect via IPv6 but there's no IPv6 connectivity available (or it doesn't work for other reasons)
  4. Socket::connect throws immediately instead of continuing with the A entry

  I haven't seen this happening on Windows because it doesn't seem to
  return the AAAA entry if there is no (public) IPv6 connectivity
  available. However, Linux systems seem to generally return the AAAA
  first by default, regardless of the available connectivity. The
  attached patch should fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1245179/+subscriptions