Return to BSD News archive
Path: sserve!newshost.anu.edu.au!dubhe.anu.edu.au!sirius.anu.edu.au!not-for-mail From: paulus@cs.anu.edu.au (Paul Mackerras) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD, pppd 2.0, ifconfig, interface must be set 'up' by hand? Date: 3 Jun 1994 09:58:42 +1000 Organization: Department of Computer Science, Australian National University Lines: 33 Message-ID: <2slrniINNioj@sirius.anu.edu.au> References: <2sfq0v$571@sophia.inria.fr> NNTP-Posting-Host: sirius.anu.edu.au Keywords: FreeBSD, pppd 2.0, ifconfig jpg@django.inria.fr (Jean-Patrick Giacometti) writes: >Hi there, I am running FreeBSD 1.1-RELEASE and have a couple of PCs connected >thru tty00. I want to run pppd version 2.0 on the line. Almost everythimg works >but the fact I must set (on both sides) the interface 'up' by hand -- 'ifconfig ppp0 up'. >Upon starting pppd warns "Could not determine local IP address" on both sides but >stays running. I set each ppp0 interface with correct (?) addresses, say >'ifconfig ppp0 inet slc100 slc401 netmask 255.255.255.240' on first host and >'ifconfig ppp0 inet slc401 slc100 netmask 255.255.255.240' on other. >On both sides pppd 2.0 is started as >'/usr/libexec/pppd passive /dev/tty00 115200' pppd expects to work out the local and remote IP addresses by means of the IPCP (IP Control Protocol) negotiation. I suggest you start pppd like this: pppd tty00 115200 slc100: on the first host, and pppd tty00 115200 slc401: on the second. You could use the passive option if you want, also, and if you really want to set the netmask, you could add `netmask 255.255.255.240' to the command lines, but I don't know that you need to bother. In general, when you're using pppd, you shouldn't (need to) use ifconfig except to see if the interface is up. Paul Mackerras paulus@cs.anu.edu.au Dept. of Computer Science Australian National University