From owner-freebsd-hackers  Tue Sep 23 03:22:41 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA03032
          for hackers-outgoing; Tue, 23 Sep 1997 03:22:41 -0700 (PDT)
Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA03015
          for <freebsd-hackers@freefall.FreeBSD.org>; Tue, 23 Sep 1997 03:22:36 -0700 (PDT)
Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48])
          by elvis.vnet.net (8.8.5/8.8.4) with ESMTP
	  id GAA10443; Tue, 23 Sep 1997 06:22:32 -0400 (EDT)
Received: from lakes.dignus.com (lakes [10.0.0.3])
	by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id GAA09331;
	Tue, 23 Sep 1997 06:33:37 -0400 (EDT)
Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA03822; Tue, 23 Sep 1997 06:25:16 -0400 (EDT)
Date: Tue, 23 Sep 1997 06:25:16 -0400 (EDT)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <199709231025.GAA03822@lakes.dignus.com>
To: rivers@dignus.com, sef@Kithrup.COM
Subject: Re: r-cmds and DNS and /etc/host.conf
Cc: freebsd-hackers@freefall.FreeBSD.org, tlambert@primenet.com
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> In article <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you write:
> > What's strange is that things on the gateway machine seem to access
> >the local network (presumably using /etc/hosts) just fine.  It's
> >only rlogin's to the gateway machine from the internal network
> >that are causing the problem... 
> 
> Hm.  Both you and Terry report essentially the same thing, which I haven't
> been able to reproduce.
> 
> But I did not set my machine up to be a gateway -- yet both you and Terry
> have.
> 
> If you do
> 
> 	netstat -f inet -n
> 
> on the gateway, when it's not connected, what does it look like?  In
> particular, does it have two or more entries towards the end that are
> listening for '*.*'?
> 
> I can't think why it would be unique to a gateway, but...
> 
> Sean.
> 

 I'm experiencing the problem now, here's the info (this is all
done on the 'gateway' machine) 

The result of netstat -f inet -n:

[ponds.dignus.com]$ netstat -f inet -n
Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp        0      0  10.0.0.1.23            10.0.0.3.3358          ESTABLISHED
tcp        0      0  10.0.0.1.513           10.0.0.3.977           ESTABLISHED
tcp        0      0  166.82.177.48.1200     166.82.1.5.25          SYN_SENT
udp        0      0  10.0.0.1.1027          10.0.0.3.2049         
udp        0      0  10.0.0.1.1026          10.0.0.3.2049         
udp        0      0  10.0.0.1.1025          10.0.0.3.2049         
udp        0      0  10.0.0.1.1024          10.0.0.3.2049         


  My /etc/resolv.conf looks like:

domain vnet.net
nameserver 166.82.1.3
nameserver 166.82.1.8


 And, my /etc/host.conf looks like:

# $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $
# For our situation, use /etc/hosts first...
hosts
# Then, use the nameserver
bind
# If you have YP/NIS configured, uncomment the next line
# nis


 Just for completeness, here's the result of ifconfig -a:

ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        ether 66:66:77:00:0b:31 
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=9010<POINTOPOINT,LINK0,MULTICAST> mtu 552
        inet 166.82.177.48 --> 166.82.100.202 netmask 0xffffff00 
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 

	- Dave Rivers -