Bug 1894 - ssh requests ipv6 addresses even with ipv6 disabled
Summary: ssh requests ipv6 addresses even with ipv6 disabled
Status: NEW
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 5.8p1
Hardware: All Linux
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 20:13 AEST by jchadima
Modified: 2019-08-24 02:35 AEST (History)
4 users (show)

See Also:

Attachments
patch solving the problem (610 bytes, patch)
2011-04-27 20:14 AEST, jchadima 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jchadima 2011-04-27 20:13:11 AEST 
ssh tries to resolve and use ipv6 addresses even if ipv6 is disabled. This is caused by the inappropriate flags for getaddrinfo. I'm not sure if this is only glibc nuance or it is a global bug.
Comment 1 jchadima 2011-04-27 20:14:08 AEST 
Created attachment 2036 [details]
patch solving the problem
Comment 2 Damien Miller 2011-06-03 10:51:12 AEST 
How does this problem manifest? If a host no IPv6 addresses configured but getaddrinfo returns AF_INET6 addresses and attempts to use them, then these connections should harmlessly and quickly fail. Is something else happening?
Comment 3 jchadima 2011-06-03 17:34:36 AEST 
problem is with DNS servers which do not correctly responds to AAAA records, this cause inability of resolution.


the full description is at
https://bugzilla.redhat.com/show_bug.cgi?id=699421
Comment 4 Mélanie Chauvel 2019-08-24 02:35:36 AEST 
With openssh 8.0p1, openssh hangs a very long time trying to use an IPv6 then falls back to IPv4. I had to explicitly disable IPv6 in NetworkManager, although no other software I use had a problem with it.

Does this match the current bug report or should I open a new one?