*BSD News Article 60202


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.hawaii.edu!ames!hookup!solaris.cc.vt.edu!news.mathworks.com!gatech!swrinde!howland.reston.ans.net!sol.ctr.columbia.edu!news.mindlink.net!uniserve!usenet
From: tom@uniserve.com (Tom Samplonius)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Please Help! with routing and slip
Date: 26 Jan 1996 19:27:29 GMT
Organization: UNIServe Online
Lines: 116
Distribution: world
Message-ID: <4eb9v1$kes@atlas.uniserve.com>
References: <31079315.52BFA1D7@ee.cornell.edu> <4e8hsm$9or@atlas.uniserve.com> <3107DBC7.FF6D5DF@ee.cornell.edu>
NNTP-Posting-Host: tapehost.uniserve.com
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
X-Newsreader: WinVN 0.99.6

In article <3107DBC7.FF6D5DF@ee.cornell.edu>, weber@ee.cornell.edu says...
>
>I have ipforwarding turned on and I have arp compiled into the kernel.  What we

  Err.. arp is always compiled into the kernel.  If you are talking
about the proxyarp option, you probably don't want that, as that is
for automatic arp proxy.  You only need manual arp publishing via "arp".

>are trying to do is have five static slip ip numbers and use proxyarp to do the
>routing for the five numbers. Also, we are using gated.  Slip seems to semi work
>we can connect to our pop server some of the time, which is on our local
>128.84.239 net, but we can not connect to any WWW servers or ftp sites that are
>not on our local net using slip.  We always get a domain name lookup failure
>making it impossible to connect to outside sources.  Many times after doing a
>domain name lookup packets are no longer being forwarded to the slip interface.
>
>I have also tried to point to several different name servers and I still get DNS
>failures.
>
>We are using FreeBSD 2.0 and our slip.login looks like this :
>
>#!/bin/sh -
>     #
>     #       @(#)slip.login  5.1 (Berkeley) 7/1/90
>
>     #
>     # generic login file for a slip line.  sliplogin invokes this with
>     # the parameters:
>     #      1        2         3        4          5         6     7-n
>     #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
>     #
>     /sbin/ifconfig sl$1 inet $4 $5 netmask $6 mtu 1500 arp
>     # Answer ARP requests for the SLIP client with our Ethernet addr
>     /usr/sbin/arp -s $5 00:61:8c:11:23:aa pub
>
>We have done a route add 128.84.239.187 128.84.239.188 on our slip server.
>128.84.239.187 is a slip client and 128.84.239.188 is the slip server and
>gateway.

  You don't need to add this route.  ifconfig adds this for you.

>Our gated.conf looks like this:
>
>    #
>    #
>    # tracing options
>    #
>    traceoptions "/var/tmp/gated.output" replace size 100k files 2 general ;
>
>    rip yes {
>     interface sl noripout noripin ;
>     interface ie0 ripin ripout version 1 ;
>     traceoptions route ;
>    } ;
>
>    #
>    # Turn on a bunch of tracing info for the interface to the kernel:
>    kernel {
>     traceoptions remnants request routes info interface ;
>  } ;
>
>    #
>    # Propagate the route to xxx.xxx.yy out the Ethernet interface via RIP
>    #
>
>    export proto rip interface ie0 {
>            proto direct {
>                    128.84.239 mask 255.255.255.0 metric 1; # SLIP connections
>
>            } ;
>    } ;
>
>    #
>    # Accept routes from RIP via ed Ethernet interfaces
>
>    import proto rip interface ie0 {
>            all ;
>    } ;
>
>I have also tried using routed -s with about the same results.

  You don't really need either gated, and routed to do this.  In fact,
it just makes it more complicated.

>I have tried to ping our slip server from the slip client and it seems to work.
>However sometimes after sending 20+ packets the packets no longer get returned to
>the client.  It is like things just stop working. If I ping our main gateway (
>128.84.239.1 ) to the Internet from the client packets go out but they never get
>returned to the client.
>

  Can the slip server ping outside hosts?  Can it ping the DNS server?

Tom

>I just can't seem to figure it out.  We are so close to having it work and I'm
>not sure what we could be missing to make it work.  Any ideas are very much
>appreciated.
>-- 
>
>
>          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>          ~                      Paul R. Weber                     ~
>          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>          ~      Computer Operations Manager II                    ~
>          ~      301 Phillips Hall                                 ~
>          ~      Electrical Engineering                            ~
>          ~      Cornell University                                ~
>          ~      Ithaca, NY 14853-6401                             ~
>          ~                                                        ~
>          ~      E-mail: prw1@cornell.edu                          ~
>          ~      Phone:  (607) 255-1460                            ~
>          ~      Fax:    (607) 254-4565                            ~
>          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~