Date: Tue, 24 Sep 1996 14:32:13 +0200 (MET DST) From: Slaven Rezic <eserte@cabulja.herceg.de> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/1674: strange behaviour of pppd (daemonize, defaultroute) Message-ID: <199609241232.OAA01525@cabulja.herceg.de> Resent-Message-ID: <199609241340.GAA20739@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1674 >Category: bin >Synopsis: strange behaviour of pppd (daemonize, defaultroute) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 24 06:40:01 PDT 1996 >Last-Modified: >Originator: Slaven Rezic >Organization: Private FreeBSD site, Berlin, Germany >Release: FreeBSD 2.2-960801-SNAP i386 >Environment: System build with "make world" from a FreeBSD-2.0.5-RELEASE system. >Description: As I switched from FreeBSD-2.0.5-RELEASE to this 2.2-SNAP I found that behaviour of pppd (unintentionally?) changed. In 2.0.5, pppd correctly daemonized and made a default route (see my invocation of pppd below). Now, pppd does not become a background process, and it does not add a default route. Further, I got following message in /var/log/messages: Sep 24 13:03:35 cabulja pppd[1199]: CCP: timeout sending Config-Requests >How-To-Repeat: My invocation of pppd is as follows: pppd /dev/cuaa1 38400 crtscts defaultroute netmask 255.255.255.0 noipdefault passive mru 1500 debug domain herceg.de There is no /etc/ppp/options >Fix: Workaround: Send pppd to background and start explicity /sbin/route add default $5 in /etc/ppp/ip-up >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609241232.OAA01525>