Return to BSD News archive
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!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!usenet.eel.ufl.edu!usenet.cis.ufl.edu!usenet.ufl.edu!livia.unf.edu!usenet.unf.edu!osprey.unf.edu!caddy From: caddy@osprey.unf.edu (Cliff Addy) Newsgroups: comp.unix.bsd.freebsd.misc Subject: pppd and routing? Date: 27 Dec 1995 01:16:19 GMT Organization: University of North Florida Lines: 13 Message-ID: <4bq6p3$o7j@osprey.unf.edu> NNTP-Posting-Host: osprey.unf.edu X-Newsreader: TIN [version 1.2 PL2] 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. A suggestions on what may be wrong here? I'd like to dedicate a machine to just handling dialins, but can't if the ppp client can't reach the rest of the network. Cliff