From owner-freebsd-hackers Sat Aug 12 0:41:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id D783137B87F for ; Sat, 12 Aug 2000 00:41:38 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id e7C6e5214161; Sat, 12 Aug 2000 15:40:05 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:PyIpMsRvogWwjShDByyquCfZpKtv8xsGMPNtzUh8B8q9dwjhpcjPx3Xg6nHEWJjy@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.10.2/8.10.2/chaos) with ESMTP/inet6 id e7C6cM027572; Sat, 12 Aug 2000 15:38:22 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 12 Aug 2000 15:38:21 +0900 (JST) Message-Id: <20000812.153821.102583385.ume@mahoroba.org> To: cactoss@yahoo.com Cc: freebsd-hackers@freebsd.org Subject: Re: localhost cannot be resolved From: Hajimu UMEMOTO In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.95b38 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Fri, 11 Aug 2000 21:57:50 -0400 (EDT) >>>>> Alexander Anderson said: cactoss> I'm having trouble resolving "localhost" for telnet and fetchmail. All cactoss> other programs (ftp, rlogin, rsh, ping, lynx) seem to understand cactoss> "localhost". Which version of FreeBSD are you using? cactoss> I'm going to include my configuration files. Please tell me if you'd like cactoss> to get more info on something. cactoss> > cat /etc/hosts cactoss> 127.0.0.1 localhost localhost.my.domain myname.my.domain cactoss> ::1 localhost localhost.my.domain myname.my.domain cactoss> > cat /etc/host.conf cactoss> hosts cactoss> bind cactoss> > cat /etc/resolv.conf cactoss> nameserver 209.226.175.224 cactoss> nameserver 204.101.251.2 cactoss> All looks right, does it? It seems right for me. cactoss> Now, when I run telnet or fetchmail, they complain. > telnet localhost cactoss> localhost: No address associated with hostname > echo $? cactoss> 1 It seems getaddrinfo(3) was failed. What's curious. Rlogin, rsh and ftp call getaddrinfo(3), too. Why is it only telnet and fetchmail? cactoss> > fetchmail cactoss> 9 messages for MYUSERNAME at pop.mail.yahoo.com (64648 octets). cactoss> reading message 1 of 9 (13403 octets) .fetchmail: SMTP connect to cactoss> localhost failed cactoss> fetchmail: SMTP transaction error while fetching from pop.mail.yahoo.com cactoss> fetchmail: Query status=SMTP > echo $? cactoss> 10 cactoss> At the same time fetchmail causes ipfw to produce these messages: cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from cactoss> ::0001:1063 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 cactoss> from 127.0.0.1:1065 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from cactoss> ::0001:1066 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 cactoss> from 127.0.0.1:1067 You don't have SMTP/IPv6 listen. This should be OK. So, SMTP connection to ::1 was fail. Then, SMTP connection to 127.0.0.1 was tried. It seems IDENT query was made in correspondings to SMTP connection to 127.0.0.1. I think you have SMTP/IPv4 listen. cactoss> Actually, could someone tell me, what does ::0001 mean? Should this be in cactoss> /etc/hosts with an alias of localhost? ::0001 is same as ::1. Leading zero can be omittled in IPv6 address format. cactoss> These strange things started to happen soon after I cvsup'ed ports-all and cactoss> reinstalled libtool. I also compiled firewall support into the kernel a cactoss> few days ago. Just in case any of this might be related to the problem. I think libtool has no relation with this problem. It may rely on firewall rule. -- 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-hackers" in the body of the message