Date: Tue, 20 Jun 2000 23:26:53 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: Danny <dannyh@idx.com.au> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NAT Query Message-ID: <20000620232653.G469@dialin-client.earthlink.net> In-Reply-To: <00062210124004.00310@desktop.freebsd.org>; from dannyh@idx.com.au on Thu, Jun 22, 2000 at 10:04:51AM %2B1000 References: <00062210124004.00310@desktop.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 22, 2000 at 10:04:51AM +1000, Danny wrote: > > -- > > - Hello I am trying to develop a prototype of NAT. > - I am running FreeBSD 3.3 > > - I have found the instructions in the handbook and decided to create a > checklist whcih is as follows : - > > > > 1) Compile the kernel with :- > > options IPFIREWALL > options IPDIVERT > > > 2) In /etc/rc.conf add:- > > gateway_enable=YES > firewall_enable=YES natd_enable=YES natd_interface=<interface | address> natd_flags="" The last one may or may not be needed depending on whether you need any special command line arguments. > 3) Make sure your network cards are already configured. > If you're using ppp, make sure you > start ppp before running natd. You might want to try the NAT built into ppp(8). > 4) Ensure the following line appears in /etc/services: > > natd 8668/divert # Network Address Translation socket > > 5) Start natd > > In /usr/local/etc/rc.d/ Nope, nope. It's started automagically in the rc* files with the above lines in rc.conf. > Remember to change ed0 to your external network card (i.e. the > one that goes to your ISP). > > natd -interface ed0 > > 6) Redirecting traffic to natd > > You will need at least the following commands. Remember to change ed0 > to your external network card (i.e. the one that > goes to your ISP). > > /sbin/ipfw -f flush > /sbin/ipfw add divert natd all from any to any via ed0 This line is also included in the default rc.firewall automagically when you have natd_enable set. > /sbin/ipfw add pass all from any to any > > 7) Reboot > In order for the changes you've made to take effect, you'll need to reboot. Well, you can start things without rebooting, but rebooting is easiest for the beginner. > Things should run smoothly now. > Making these changes permanent > These steps will ensure that natd is configured when you need to reboot. > > Make sure the following is in /etc/rc.conf. Remember to change ed0 > to your external network card (i.e. the one that goes to your ISP). These > lines tell the system that you will be using natd, the interface which needs > to be diverted, and the flags which natd needs. In this case, we'll be adding > our flags to a file for ease of maintenance.. > > natd_enable="YES" > natd_interface="ed0" > natd_flags="-f /etc/natd.conf" OK... why is this down here? > Then make sure the following is in /etc/natd.conf. Remember to change ed0 to your external network card (i.e. the one > that goes to your ISP). > > interface ed0 > use_sockets yes > same_ports yes None of those is actually required for the average user. > Situation > > -For the testing environment I have a dial up account with myISP which is not > flat rate. > - For the last 3 to 4 years I have been running Winproxy. > > Question > > 1) Does it mean I have to have some kind of permaent line to be running natd? Not sure what that means. > 2) Can I use my existing dial up account? I would not see why not. > 3) If so have do I have to do exactly to detect my internal netcom 33.6 modem? It should be detected as something like sio2 if the kernel is properly configured. What is its IRQ? Port? It isn't a Winmodem, is it? If it is, you are out of luck for anything but Win9x. -- Crist J. Clark cjclark@alum.mit.edu 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?20000620232653.G469>