Date: Tue, 08 Aug 1995 23:23:12 -0400 From: Chris Shenton <cshenton@apollo.hq.nasa.gov> To: John Capo <jc@irbs.com> Cc: freebsd-hackers@freebsd.org Subject: Re: client & server ppp Message-ID: <199508090323.DAA01696@wirehead.hq.nasa.gov> In-Reply-To: Your message of "Tue, 08 Aug 1995 15:18:29 EDT."
next in thread | raw e-mail | index | archive | help
On Tue, 8 Aug 1995 15:18:29 -0400 (EDT), John Capo <jc@irbs.com> said: John> It sounds like you have the getty on the wrong port or you are John> dialing out on the wrong port. Getty should not wake up when John> you dial out on a /dev/cuxxx port. John> You may want to use ppp, aka iijppp, to dial into the John> Portmaster. I have been using it for uni-directional demand John> dialing for a year and used it for several months for John> bi-directional demand dialing. I've been dialing into a FreeBSD (Release, -current, and now -stable) system running pppd, mostly in server mode, but also dialing back to my home (Sunos pppd) in client mode. In both, FreeBSD pppd refuses to die and and free up the port for getty (on cuaa0) so I can dial in again from home. FBSD pppd also consumes all CPU available: on a system with two pppds, they both run at 50%. W.R.T. die-on-hangup and CPU load, pppd works fine on my SunOS box, as it has on Linux, and I think FBSD-1.*. But not FBSD-2.* Last week I brought up iijppp and with some work, got it running as both client and server. It kills ppp when the modem hangs up like it should, and uses a modest amount of CPU. Hurray! Problem is, we're subnetting the FBSD box (0xfffffff0) so we can have a couple of home nets and a play net at work, off the `real' work net. iijppp doesn't appear to have a place to specify a netmask, so this hoses our routing :-( If anyone's got a fix for this, or a pointer to further docs, I'd appreciate it. Didn't see anything in the docs or example config files. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508090323.DAA01696>