Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!col.hp.com!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!pipeline!psinntp!psinntp!psinntp!jadpc!jdeitch
From: jdeitch@jadpc.jd.com (Jim Deitch)
Subject: Re: pppd and routing?
Message-ID: <DKH7qL.1vy@jadpc.jd.com>
Organization: J. Deitch & Associates, San Diego, CA.
References: <4bq6p3$o7j@osprey.unf.edu> <4c48ti$f8v@uriah.heep.sax.de>
Date: Mon, 1 Jan 1996 00:23:08 GMT
Lines: 44
In article <4c48ti$f8v@uriah.heep.sax.de>,
J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote:
>caddy@osprey.unf.edu (Cliff Addy) writes:
>> We have pppd servicing dialins into a standalone tcp/ip network. This works
>> fine as long as you're only accessing the machine running pppd. If, for
>> instance, you telnet or ping another machine on the network, it fails. I
>> have a feeling that it's a misconfiguration of pppd or routed. The ip#
>> line from /etc/ppp/options is something like 200.1.2.100:200.1.2.101. The
>> ip # for the server on the tcp/ip network is 200.1.1.1. Now, from 200.1.1.3
>> I can ping 200.1.1.1 and 200.1.2.100, but not 200.1.2.101.
>
>Well, i think this is one of the most frequently asked questions...
>
>For FreeBSD 2.0.5:
>
> add
> sysctl -nw net.inet.ip.forwarding=1
>
> somewhere to your /etc/netstart (or /etc/rc.local)
>
>For FreeBSD 2.1:
>
> put
> gateway=YES
>
> into your /etc/sysconfig.
>
>Of course, you must make sure that the _outside_ router is willing to
>forward all packets for the 200.1.2.* (PPP) network to your box.
>
>Btw., i don't think 200.1.{1,2} are official IP net numbers for you,
>so don't use them! Instead, use the reserved networks that are
>mentioned in /etc/hosts.
>
>
You may also want him to check out the proxyarp option also.
(Just my $0.02 worth)
Jim
--
INTERNET: jdeitch@jadpc.jd.com
UUCP: cg57!jadpc!jdeitch