Adding a FreeBSD Gateway on a DSL/ ATM circuit

[Murray Taylor]

look at the defaults in /etc/defaults/rc.conf

specifically look for lines with gateway in them
ie    gateway_enable="NO"

copy the appropriate lines into /etc/rc.conf

edit  
ie    gateway_enable="YES"


You will need to set the the default_route line also to point 
to the isp  I  think ...

HTH
mjt


> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org 
> [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of 
> admin at hdk5.com
> Sent: Friday, 4 August 2006 4:36 AM
> To: freebsd-questions at freebsd.org
> Subject: Adding a FreeBSD Gateway on a DSL/ ATM circuit
> 
> Aloha,
> 
> My current problem is that I need to use a box as a FreeBSD 
> 6.* gateway/firewall to the internet protecting  an MS box 
> that is in the office for doing a lot of photo work and 
> uploading to servers for the company my wife works with. I 
> was going to use a freesco (Linux)disk 
> /firewall/gateway/router like I have on my single dsl 1.5/384 line. 
> (This is currently what is protecting the MS box on this circuit.)
> 
> However, the freesco setup does not work as a gateway on the 
> leg of the ATM 5 IP circuit where we want to move the MS box 
> to. I have tried to get it setup and have emailed the freesco 
> lists and apparently no one has accomplished this.
> 
> I have now built a FreeBSD box with 2 nics to use as a 
> gateway/router/firewall between the single MS box and the 
> internet. ed1 is on the 66.xxx.132.236 leg of the ATM. The 
> defaultgateway on the internet side of the ATM is 66.xxx.132.233.
> The LAN side of the box ed0 is 192.168.1.1 to which the MS 
> box is directed.  ( I am using a test box 192.168.1.29 with 
> FreeBSD 6* in place of the MS box at this point.)
> 
> I can ping from the gateway box nic to the internet ok. I can 
> ping from the Test box to the Lan side of the gateway box OK. 
> I cant reach the internet thru the gateway. I have read 
> probably 5 howtos from the FreeBSD hand book and elsewhere 
> and none are exactly what I am doing.
> 
> On FreeBSD Questions list recently there was a similar issue 
> question posted but no body answered the post.
> 
> It had to do with rc.conf
> 
> Listing both Nics  ifconfig_ed0 =66.xxx.132.236  netmask
> 255.255.255.248  #inet side
>                                    ifconfig -ed1=192.168.1.1 netmask 
> 255. 255.255.0           # lan side
>                                and gateway_enable="YES" which 
> I have done.
> 
> At this point I have not attempted a firewall PF or IPFW 
> since I cant reach the internet thru the gateway and I want 
> to understand what is not right with this setup first.
> 
> If I use: route add -net 192.168.1 .29    192.168.1.1
> 
> I can no longer ping the Lan side of the gateway from the test box.
> 
> Can you direct me to or give me a howto on setting this up so 
> I can reach the internet if indeed its possible using a 
> gateway/firewall on the leg of an ATM circuit? Any help would 
> be appreciated.
> 
> Thanks,
> 
> Al Plant - Honolulu, Hawaii
> 
> - Admin -- http://hawaiidakine.com -- http://hdk5.com --
> -- http://internetohana.org -- http://freeBSDinfo.org --  + 
> Supporting open source computing - FreeBSD 6.* +
> 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"
> 
> ***This Email has been scanned for Viruses by MailMarshal.***
> 
---------------------------------------------------------------
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---------------------------------------------------------------

***This Email has been scanned for Viruses by MailMarshal.***