Editing Futotemporarywikipage (section)

==== 4.1 Why a Static IP? ====

We are going to set up a server that we are going to consistently access. This means we always want it to be at the same place.

Imagine trying to deliver mail to someone who lives on 20 Main Street today, and 90 Chandler Avenue tomorrow. Imagine trying to frequent a restaurant whose address changes every week. It would be annoying, inconvenient, and perhaps downright impossible.

We want our server to always be at the same address. The “D” in “DHCP” means “dynamic” – as in, changing. We don’t want that. We want a “static” IP, meaning it does NOT change.

When setting up your server, we need to give it a static IP, so we always know where to find it, and it never changes. How do we know what IP to give it? Go back to '''pfSense'''’s DHCP server configuration page &amp; you can find it by going to '''Services —&gt; DHCP Server'''. The ''“subnet range”'' tells you the list of available IPs. Keep in mind that you cannot use the IP address of your '''pfSense''' router here.

* '''Router Gateway''': My router’s IP is 192.168.5.1. This is the gateway address.
* '''Address Pool Range''': My address pool range is from .15 to .245, leaving .246 to .254 and .2 to .14 available. This setup provides a buffer of IPs for servers and other devices.

'''Why the Buffer?''' I don’t want any conflicts where someone plugs in their computer while mine is rebooting and steals my IP. We will be setting up STATIC MAPPINGS so that nobody else can grab the IP address of my server – the IP we choose for our server will be reserved for our server’s specific network interface card and not some hated brother in law that thinks he’ll play games when your spouse has him over. However, this is still good practice.

<span id="choosing-a-static-ip"></span>