From owner-freebsd-current Mon Mar 20 12:47:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id B546137BD0C for ; Mon, 20 Mar 2000 12:39:15 -0800 (PST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:eF+08oQGN3mqtUXYLMqya8Ehh1agI5bWZQqKiYYQRhjazXJj6MFZzNfmxByagTQm@localhost [::1]) by peace.mahoroba.org (8.10.0/3.7W-peace) with ESMTP id e2KKaNc07860; Tue, 21 Mar 2000 05:36:23 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 21 Mar 2000 05:36:23 +0900 (JST) Message-Id: <200003202036.e2KKaNc07860@peace.mahoroba.org> To: cpiazza@jaxon.net Cc: visigoth@telemere.net, current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <20000320120221.A517@norn.ca.eu.org> References: <20000319150009.A404@norn.ca.eu.org> <20000320120221.A517@norn.ca.eu.org> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Hajimu UMEMOTO (=?ISO-2022-JP?B?GyRCR19LXBsoQiA=?= =?ISO-2022-JP?B?GyRCSCUbKEI=?=) X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 20 Mar 2000 12:02:21 -0800 >>>>> Chris Piazza said: > According to Mr. Stevens (Unix Network Programing Vol 1 > chapt 9.4) this option, or having the env. variable RES_OPTIONS=inet6 set > will cause the behavior you are describing... It's a behavior of gethostbyname(). Ssh uses getaddrinfo() instead of gethostbyname(). See RFC2553. cpiazza> No, neither of those. FreeBSD searches inet6 first at the moment. cpiazza> I don't know if I made this clear in my email, but this just started cpiazza> happening... Hmm... it's fixed again: Don't you see packet loss or name server problem? Your previous log seems 128.189.4.1 didn't answer to AAAA RR query. cpiazza> 12:01:15.622122 24.113.19.137.1253 > 24.2.10.36.53: 61892+ AAAA? beast.freebsd.org. (35) cpiazza> 12:01:15.706319 24.2.10.36.53 > 24.113.19.137.1253: 61892 1/1/0 (132) cpiazza> 12:01:15.707070 24.113.19.137.1254 > 24.2.10.36.53: 61893+ A? beast.freebsd.org. (35) cpiazza> 12:01:15.750017 24.2.10.36.53 > 24.113.19.137.1254: 61893 2/4/4 (238) Is it a log with `ssh -4'? Why does ssh qurey AAAA RR with -4? > > Using ssh -4 or telnet -4 makes it work right away (of course), but > > I don't want to have to type that all the time. [program] ipv4address > > also works. How about `alias ssh "ssh -4"'? -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message