Date: Sat, 9 May 1998 14:49:28 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: Mark Szlaga <mszlaga@umdsun2.umd.umich.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: Ethernet -> natd -> Dynamic-IP dialup Message-ID: <Pine.BSF.3.95.980509144610.5333B-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.3.96.980509133404.3051n-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 It's actually the SAME natd, as there is a library libnat that does NAT, and is included by both NATD and ppp but for ppp installations it's less troublesome to use the ppp version obviously as the ppp daemon takes care of a lot of the configuration for you and you can leave the firewall to purely firewalling.. (of course with NAT you probably don't NEED firewalling bery much as it's only outgoing :-) julian On Sat, 9 May 1998, Doug White wrote: > On Sat, 9 May 1998, Mark Szlaga wrote: > > > I recently changed the operating system on my internet firewall from > > Linux to FreeBSD. This was done because I am tired of all the timeouts that > > IP-Masquerade causes, and was told that Natd is a far more superior program. > > That and FreeBSD networking runs much better as a router than Linux will > > ever pray to. So far I am impressed in the performance of the machine, > > but cannot get networking to work properly. > > Good to hear! :) > > > Ok. Here's the problem. I can get the non-firewall enabled kernel > > to dialout (what I am using now) and I can set up the routes by hand (I > > am trying to fix this problem) but this is the only way I can get the > > machine to dialout. When I do the proper kernel settings to get > > firewalling to work (IP_DIVERT and IP_FIREWALL) I can only get the > > network to work internally, and cannot even touch the dialup device. > > That is, until I disable ed0, but then I cannot get the routes quite > > correct. > > When you turn the firewall on, it by default blocks everything until you > program other rules into it. I'd suggest setting your firewall_type to > `open' mode in /etc/rc.conf, and then tune /etc/rc.firewall to taste. > Type `open' allows everything. > > Note that you have to add a rule to divert packets to natd. That rule > should be on the natd manpage. > > > My question is if anyone sees anything blatently wrong, what can I do > > to change this. I am happy with the operating system, just frustrated > > that it won't do what I want it to do... And also it would be > > appreciated if you could point me in the right direction if this is > > somewhere in the FAQ or handbook, as I just compiled Lynx to be able to > > read it locally (lyn on vt100 is murder...) > > http://www.freebsd.org/docs.html should get you started. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980509144610.5333B-100000>