From owner-freebsd-current Mon Aug 7 12:34:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA27130 for current-outgoing; Mon, 7 Aug 1995 12:34:06 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id MAA27123 ; Mon, 7 Aug 1995 12:34:04 -0700 Message-Id: <199508071934.MAA27123@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Pete Carah cc: current@freebsd.org Subject: Re: workaround for talk's address problem In-reply-to: Your message of "Mon, 07 Aug 95 12:02:26 PDT." <199508071902.MAA08206@puffin.pelican.com> Date: Mon, 07 Aug 1995 12:34:03 -0700 From: "Justin T. Gibbs" Sender: current-owner@freebsd.org Precedence: bulk >In article <405f3m$l4h$1@haywire.DIALix.COM> you write: >>j@uriah.heep.sax.de (J Wunsch) writes: >>>talk(1) has problems with multi-homed hosts. To negotiate the >>>connection with the remote peer, it uses the first address as returned >>>by a call to gethostbyname(). This will cause the connection to hang > >..... >This problem is more general than it looks; kadmind and kerberos daemon >both don't do listens on other interfaces than the first one. >From our kerberos server with a netstat -a -n: tcp 0 0 *.751 *.* LISTEN udp 0 0 *.750 *.* Both kerberos and kadmind (as of my fix a few days ago) listen on all interfaces. >I don't know about other udp daemons. The suggested fix about using >the routing socket would work for these two since they run as root, >but that isn't super general. You don't need to use the routing sockett for either of them. ... -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================