From owner-freebsd-current Tue Oct 2 9:52:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id 4795837B406; Tue, 2 Oct 2001 09:52:28 -0700 (PDT) Received: (from root@localhost) by cheer.mahoroba.org (8.12.1/8.12.1) id f92Gq94h049093; Wed, 3 Oct 2001 01:52:09 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:UvZ7gfn9pSzYgS1RZKbl26aXkRlMkdErzjZYkNkoDTMFWyEo9qRU7p41mOKTn0Lf@peace.mahoroba.org [IPv6:2001:200:301:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.1/8.12.1/av) with ESMTP/inet6 id f92Gq57Q079564; Wed, 3 Oct 2001 01:52:07 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 03 Oct 2001 01:52:04 +0900 (JST) Message-Id: <20011003.015204.133265112.ume@mahoroba.org> To: drosih@rpi.edu Cc: alex@big.endian.de, current@freebsd.org, gad@freebsd.org Subject: Re: lpd: Host name for your address (fe80:....%xl0) unknown From: Hajimu UMEMOTO In-Reply-To: References: <20010930.234428.102494221.ume@mahoroba.org> <20011001141916.A24281@fump.kawo2.rwth-aachen.de> 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-Operating-System: FreeBSD 5.0-CURRENT X-Mailer: xcite1.38> Mew version 2.0.54 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Tue, 2 Oct 2001 12:30:33 -0400 >>>>> Garance A Drosihn said: drosih> On the print *client* machine, you start lpd with '-4', meaning that drosih> it (the client) should only accept jobs from IPv4-style connections. drosih> Note that this flag only effects what lpd will accept, this flag has drosih> no effect on what lpr/lpq/lprm will do when they need to connect to drosih> a remote queue. Yes, it's right. drosih> The print queue for 'lp' on oink refers to a remote machine that drosih> is named neutron. That hostname maps to an IPv6 address. Thus, drosih> lpq/lpr/lprm have no choice on how to connect to that remote host. drosih> They use the IPv6 address. (note, for instance, that your 'ping6' drosih> knows about neutron via IPv6, not IPv4). So, the print client drosih> connects to the print server via IPv6. When the print client drosih> connects to the print server, the print server looks up the IPv6 drosih> address of the *client*, because the client made an IPv6 connection drosih> to the server. Again, this has nothing to do with 'lpd -4' on the drosih> client. The print server apparently can not find a hostname to drosih> match the IPv6 address of the client, so it returns the first error drosih> message, listing the IPv6 address of the client. No, a client does query AAAA RR for IPv6 and A RR for IPv4. If AAAA RR is found, a client tries to connect using IPv6, 1st. However, lpd accepts only IPv4 connection, in this case. Then, if A RR is found, a client falls down and tries to connect using IPv4. So, a client never connects using IPv6 to an IPv4 only listening server. drosih> Assuming that all of the above is correct, then I *think* everything drosih> is working the way it is supposed to. However, I do not know the drosih> finer points of how IPv6 is supposed to work. Can a single hostname drosih> have both an IPv4 address and an IPv6 address? (as far as DNS is drosih> concerned, I mean). This I do not know. In any case, the parameters drosih> to 'lpd' are not going to effect how 'lpq' handles the printcap file. It is usual way that a dual stack host has both AAAA RR and A RR. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}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