*BSD News Article 49027


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!recepsen.aa.msen.com!zib-berlin.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: How to set up routing tables?
Date: 18 Aug 1995 11:40:44 +0200
Organization: Private U**x site, Dresden.
Lines: 49
Message-ID: <411n6s$e62@bonnie.tcd-dresden.de>
References: <ARNULF.95Aug17095614@arnulf.dialup.fu-berlin.de>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

& H.-P. Guenther <arnulf@arnulf.dialup.fu-berlin.de> wrote:

>I have a second computer now with FreeBSD installed (what else?).
>And I have a serial line, later this will be replaced by ethernet.
>So I configured GATEWAY into the kernel and set up my first system as
>a slipserver.

options GATEWAY is almost a no-op and will disappear in one of the
next releases.  Use

	sysconf -w net.inet.ip.forwarding=1

in your /etc/netstart instead.

>I made an /etc/sliphome/slip.{hosts,login,logout}.  Works fine, with
>one exception: I have to delete the default route on my first system
>to work properly.  Without it netstat -i hangs, ping B (if A is the
>slipserver) hangs.  Only ping A on B works.  But not telnet etc.

(You can try ``netstat -in'' btw.)

I think machine A is configured to use DNS, and it tries to query (or
reverse-lookup) B's address on the Internet DNS, and fails.  There
are multiple ways out of this.

The hacky way: change the default lookup order in /etc/host.conf to
first look in /etc/hosts, and if this fails, ask DNS.  Maintain a
small /etc/hosts containing just only your local addresses (so there
will never be a chance that it would disagree with DNS).

The correct way: get the address of box B registered with DNS, so
everybody outside does know about it. :)

The practical way: get your own subdomain, make it a privately
maintained separate DNS zone (that's perhaps being shadowed by an
official name server from an outside point of view), set up a local
name server for it, make it also mirror the appropriate in-addr.arpa
zone from its primary (thus making it a secondary and hence also
authoritative name server for reverse lookups).  A bit more of work,
but works like a charm for me, and takes some DNS load off the wire
since you benefit from the caching abilities.

Needless to say, your IP provider must also route the packets for box
B.
-- 
cheers, J"org                      private:   joerg_wunsch@uriah.heep.sax.de
                                   http://www.sax.de/~joerg/

Never trust an operating system you don't have sources for. ;-)