From owner-freebsd-current Mon Aug 7 23:44:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id XAA29594 for current-outgoing; Mon, 7 Aug 1995 23:44:17 -0700 Received: from rover.village.org (rover.village.org [198.137.146.49]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id XAA29584 for ; Mon, 7 Aug 1995 23:44:14 -0700 Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id AAA04185; Tue, 8 Aug 1995 00:44:05 -0600 Message-Id: <199508080644.AAA04185@rover.village.org> To: davidg@Root.COM Subject: Re: workaround for talk's address problem Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) In-reply-to: Your message of Sun, 06 Aug 1995 15:29:19 PDT Date: Tue, 08 Aug 1995 00:44:05 -0600 From: Warner Losh Sender: current-owner@FreeBSD.ORG Precedence: bulk : What is the problem with specifying INADDR_ANY for the local address? The problem with Kerberos had to do with which interface that was talking was important, and the IP address was somehow mixed up in the tickets that were returned. We have a few machines in the village that are multi-homed, and Kerberos didn't like them at all. It didn't have to do with the connection code, but what happened after everything got connected. Warner