From owner-freebsd-stable Mon Jul 19 13:34:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 036E014E63 for ; Mon, 19 Jul 1999 13:34:01 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id PAA03891 for ; Mon, 19 Jul 1999 15:33:57 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990719163310.00742ab8@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 19 Jul 1999 16:33:10 -0400 To: freebsd-stable@freebsd.org From: Tom Embt Subject: Re: Problem with cvsup Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:53 AM 7/20/99 +1000, you wrote: >Dag-Erling Smorgrav wrote: >> Yes, in some cases you may save up to 1% CPU power using kernel PPP. >> On the other hand, userland PPP is actively maintained, whereas >> nobody's touched kernel PPP for over a year except to keep it in sync >> with architectural changes in the kernel. >> >> Userland PPP has builtin NAT based on libalias (which does all kinds >> of magic to make active FTP and the like work across NAT). It also has >> a much nicer configuration syntax (though that may be a matter of >> personal preference). > >You've sold me! My family refuse to use anything but M$ Internet >Explorer for their web/ftp needs, and the damn thing doesn't support >passive mode FTP (neither does their DOS based client for that matter). >I had to add a rule to specifically allow TCP traffic on port 20... > >Thanks for the info. > Of course (in my experience) this will only work if the FTP site is on its well-known port 21. Otherwise you'll need to use a PASV-capable client. Not usually a problem, but once in a while... Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message