Re: Howto connect a FreeBSD to the Internet
From: Daniel Rudy (dcrudy_at_invalid.pacbell.nospam.net.0123456789)
Date: 10/11/03
- Next message: Simone Ackermann: "Re: ports update"
- Previous message: Daniel Rudy: "Re: fxp, jumbo frames, pppoe"
- In reply to: Eoin Lane: "Howto connect a FreeBSD to the Internet"
- Next in thread: Eoin Lane: "Re: Howto connect a FreeBSD to the Internet"
- Reply: Eoin Lane: "Re: Howto connect a FreeBSD to the Internet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 11 Oct 2003 08:43:35 GMT
Somewhere around the time of 10/08/2003 19:31, the world stopped and
listened as Eoin Lane contributed this to humanity:
> I have the following question about connecting a FreeBSD to the internet.
>
> Below is the current setup I have at home:
>
> Internet connection via a (Comcast) cable modem
> Cable modem is connected directly to a DI-614+ Enhanced 2.4GHz Wireless
> router
> My Intranet contains two FreeBSD systems and one Win XP system, The
> three computers are hardwired to the router
> The router provides firewall protection to my intranet
Good job on having a firewall there.
> I now want to expose one of the FreeBSD boxes to the internet primarily
> as a web server on port 80
>
> I have a number of options here
> 1. Connect one of my FreeBSD boxes directly to the internet by
> connecting it between my cable modem and my router
This is the method that I use. I have a computer with two ethernet
adapters. It's the firewall/DNS server/NTP server/DHCP server/Internet
Gateway. It's been running reliably like this for a number of years
now. One interesting thing to note about having a full computer as the
network gateway is configurability. You can do almost anything with the
correct ports and custom scripts.
> 2. Configure the router to only allow traffic on port 80 to the
> designated FreeBSD box behind my firewall
This would be the most simple way of doing it. But, you will not only
need to open port 80 on the router for incoming, you will also need to
forward that port to a computer inside your network. It would also be a
good idea to have the machine that is the recipiant of the port forward
to have a static IP address.
> 3. Configure the designated FreeBSD box to be in a DMZ, this I can also
> do with my router.
I'm not entirely sure what you mean by this.
> I am just wondering at the merits of each approach to see if anyone here
> has a similar setup and what they would recommend?
>
> I also have the problem that my ISP does not provide a static IP
> address. I have been considering using something like easydns dynamic
> DNS solution (http://easydns.com/dynamicdns.php3) and again I am
> wondering if this group has had any experience with such providers
> and/or any other recommendations?
>
I use dyndns. Here's the link: http://www.dyndns.org. They offer 5
subdomains for free, and $29.95/year for custom DNS if you have your own
domain name. You will want a dynamic DNS client running on a machine on
your LAN. I use ddclient which can be found in the ports. It is a perl
script program that offers a number of features and easy config and setup.
If you use your option 1 above, then in the ppp.linkup, you need to have
the command to execute a shell script. Then you can call ddclient from
that script automaticly whenever the datachannel link comes up.
> Thanks in advance.
No problem.
>
> Eoin
>
-- Daniel Rudy Remove nospam, invalid, and 0123456789 to reply.
- Next message: Simone Ackermann: "Re: ports update"
- Previous message: Daniel Rudy: "Re: fxp, jumbo frames, pppoe"
- In reply to: Eoin Lane: "Howto connect a FreeBSD to the Internet"
- Next in thread: Eoin Lane: "Re: Howto connect a FreeBSD to the Internet"
- Reply: Eoin Lane: "Re: Howto connect a FreeBSD to the Internet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
