PuTTY bug multiple-addresses

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: PuTTY mishandles machines with multiple addresses
class: bug: This is clearly an actual problem we want fixed.
difficulty: tricky: Needs many tuits.
priority: medium: This should be fixed one day.
fixed-in: 2005-01-17 f70efc5cc6ae0e86b3354ec4ef71ea04bd0d84d9 (0.58)

At present, if a host has multiple addresses, PuTTY merely connects to the first one it gets. This is arguably incorrect behaviour, and PuTTY should try each address in turn until it gets one that works. My feeling is that a Socket_Addr should be able to contain multiple addresses, and sk_new should handle the retries, but I haven't thought out how proxying would work.

Ref: <3E1AE612.6060308@magdalen.oxford.ac.uk>

RFC 1123 has this to say on the subject:

When the remote host is multihomed, the name-to-address translation will return a list of alternative IP addresses. As specified in Section 6.1.3.4, this list should be in order of decreasing preference. Application protocol implementations SHOULD be prepared to try multiple addresses from the list until success is obtained. More specific requirements for SMTP are given in Section 5.3.4.

SGT, 2005-01-16: This is much more important in an IPv6-supporting world, since there's the possibility that your DNS lookup will return you an IPv6 and an IPv4 address in that order, and if you can't route to the former then you must fall back to the latter or else the introduction of IPv6 support has made matters worse for you. Hence, done.


If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2016-12-27 11:40:22 +0000)