From owner-freebsd-questions Wed May 13 13:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03641 for freebsd-questions-outgoing; Wed, 13 May 1998 13:00:07 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from umdsun2.umd.umich.edu (root@[141.215.10.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03467 for ; Wed, 13 May 1998 12:59:49 -0700 (PDT) (envelope-from mszlaga@umdsun2.umd.umich.edu) Received: from esun11.umd.umich.edu (mszlaga@esun11 [141.215.10.133]) by umdsun2.umd.umich.edu (8.8.7/8.8.7) with SMTP id PAA13327; Wed, 13 May 1998 15:56:58 -0400 (EDT) Received: from localhost by esun11.umd.umich.edu (SMI-8.6/SMI-SVR4) id PAA19180; Wed, 13 May 1998 15:56:57 -0400 Date: Wed, 13 May 1998 15:56:57 -0400 (EDT) From: Mark Szlaga To: Julian Elischer cc: Doug White , freebsd-questions@FreeBSD.ORG, jenkins.mike@epamail.epa.gov Subject: Re: Ethernet -> natd -> Dynamic-IP dialup (solved) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 May 1998, Julian Elischer wrote: > One think not mentionned.. > the user-mode ppp daemon has a natd built-din > I would suggest you use this instead.. > I think it's option -alias > Thanks to everyone that responded. I got it up and running within a few hours of your mail. And I am _*VERY*_ happy with the performance and flexability of the FreeBSD networking and ppp program. Only two other questions. IIRC there was a way to have pppd under linux to do a keepalive. Is this possible for ppp? As I want to keep a permanent connection as much as possible, with the least amount of extra programs being run (I had a keepup program written to dial and maintain the link in linux, but had many problems...). Second, I read the "academic" section of the ppp primer and it set up a working DNS system. This works nicely and I have no problems... for the local machine (eg. 127.0.0.1). The problem is that it complains that 192.168.1.1 does not have a valid DNS entry, but it works. using nameserver 127.0.0.1 in /etc/resolv.conf works fine. using server 192.168.1.1 in nslookup works beautifully, but nameserver 192.168.1.1 fails. Thanks again and keep up the good work! Mark Szlaga mszlaga@umd.umich.edu http://www.umd.umich.edu/~mszlaga/ /dev/hdb5 - 0.5Gb of spinning metal, all alone in the night... - unknown - alt.sysadmin.recovery /dev/hdb5 - our last best hope for free space... - Chip Salzenberg - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message