Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken.llnl.gov!uop!pacbell.com!ico.net!usenet
From: Paul Stith <pauls@cats.ucsc.edu>
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD: pppd install/options
Date: 20 Feb 1995 21:38:52 GMT
Organization: The Internet Connection, Scotts Valley, CA. 408-438-8989
Lines: 56
Message-ID: <3ib25c$ald@kane.ico.net>
References: <3ib1ll$alc@kane.ico.net>
NNTP-Posting-Host: paul.sum.com
(What I meant to post - including pppd startup messages) - Sorry
I've been working through setting up our FreeBSD box as a router to our
local LAN via PPP to our ISP. Our PPP account works fine for
Windows/Trumpet PPP dialup - but seems to still have troubles with the
BSD dialup access. LAN access to the FreeBSD system is fine.
Once pppd is started - and supposedly linked to tty01 - I see the
following error (after about 30 seconds).
]Feb 20 13:17:41 tick pppd[238]: pppd 2.1.2 started by root, uid 0
]Feb 20 13:17:44 tick pppd[239]: Connect: ppp0 <--> /dev/tty01
]Feb 20 13:18:17 tick pppd[239]: IPCP: timeout sending Config-Requests
I've been digging through the FAQs, etc. - with no luck yet. I'd
appreciate it if someone could confirm my assumptions in the ppp
options file.
Beyond that - I think I understand that the route should be established
automatically, correct? I can't ping xxx.xxx.xxx.PPP :{
xxx.xxx.xxx.PPP
yyy.yyy.yyy.PPP | xxx.xxx.xxx.NIC
----- ppp0 ------- ed0 ----
'net<->| ISP |<-PPP-> |FreeBSD|<-LAN->| WS |
----- ------- ----
IPS gave us yyy.yyy.yyy.ppp
and our own range of IPs xxx.xxx.xxx.xxx
/etc/netstart
..
ifconfig ppp0 xxx.xxx.xxx.PPP
/etc/ppp/options ppp Host options
crtscts # Hardware flow control
defaultroute #
netmask 255.255.255.0 # netmask ( not required )
xxx.xxx.xxx.PPP:yyy.yyy.yyy.PPP # ip's of local and remote hosts
# local ip must be different from one
# you assigned to the ethernet ( or
# interface on your machine.
# remote IP is ip address that will be
# assigned to the remote machine
domain xxx.com # your domain
passive # wait for LCP
modem # modem line
Thanks for any helpful hints.
-Paul