{"id":895,"date":"2021-09-22T10:10:12","date_gmt":"2021-09-22T10:10:12","guid":{"rendered":"https:\/\/www.practicallynetworked.com\/?page_id=895"},"modified":"2021-10-05T16:59:22","modified_gmt":"2021-10-05T16:59:22","slug":"static-dhcp","status":"publish","type":"post","link":"https:\/\/www.practicallynetworked.com\/static-dhcp\/","title":{"rendered":"Static DHCP Offers Consistent Remote Access"},"content":{"rendered":"

Open source router firmware such as DD-WRT does things the factory-installed stuff never offers. For example, you can give a computer the same IP address every time so you’ll always have remote access.<\/strong><\/p>\n

by Aaron Weiss<\/strong><\/p>\n

By now, you probably know that upgrading the near-legendary Linksys WRT54G series routers with free, often open-source firmware is one of the best bargains going. Replacement firmware typically offers a plethora of advanced router and firewall features rarely found on sub-$100 hardware.<\/p>\n

DD-WRT<\/a>, a free, open-source firmware coded and distributed by \u201cBrainSlayer,\u201d has emerged as one of the leading, most powerful and also user-friendly firmware replacements for the WRT54G series. DD-WRT is available for an increasingly wide range of routers besides the WRT54G, including models by Asus, Belkin, Buffalo Devices, Motorola and Siemens.<\/p>\n

There are caveats to upgrading your router, and the\u00a0process is not without risk<\/a>, so beware. We’ll assume you’ve got DD-WRT successfully installed, and forge ahead…<\/p>\n

In this first detailed look at new features you can get from open source router firmware, prepare to be dazzled by the capabilities of… the Dynamic Host Configuration Protocol (DHCP).<\/p>\n

Static DHCP<\/strong><\/p>\n

Out of the box, most routers and PCs are designed to manage their IP addresses automatically. The PC, whether wired or wireless, requests an IP address and related network parameters from the router using the DHCP protocol. The router plucks an unused address from its pool of available addresses, hands it to the client, and everyone is smiling.<\/p>\n\n\n\n
\n

What’s That Term?<\/strong><\/span><\/h4>\n

Not sure what a particular term means? Check out the searchable\u00a0PracticallyNetworked Glossary<\/a>.<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

This process results in what is called a \u201cdynamic IP address\u201d \u2013 every time the PC connects to the router (on boot-up, for example, or wireless association), it is assigned a new IP address. The router may assign the same address it assigned in the previous session. Or it may not. You don\u2019t know and, usually, you don\u2019t care.<\/p>\n

There are cases, though, when you want your client to receive a predictable, consistent IP address. The most common scenario is when you run a server on your client PC. Suppose you run a Web site on a PC at home, and you need access to this server from elsewhere \u2013 work, school, your laptop in the park. Your router \u201chides\u201d your server from the outside world, which is normally a good thing for security. This is why a higher power invented\u00a0Port Forwarding<\/a>\u00a0.<\/p>\n

Your router will allow you to forward traffic destined for a specified port to a specific machine. In its simplest form, you can configure your router to forward incoming traffic destined for port 80 \u2013 the default port number for Web traffic \u2013 to the IP address of the PC running your Web server.<\/p>\n

What is your Web server PC\u2019s IP address? If it receives its address automatically from the router \u2013 you don\u2019t know for sure. It could change, and your port forwarding would become unreliable.<\/p>\n

One solution is to manually assign your Web server its IP address and network parameters, rather than use DHCP. However, this may limit your ability to easily connect that machine to other networks \u2014 a more likely problem for laptops. If your ISP changes name servers on occasion, this could also break your manual network configuration.<\/p>\n

Ideally, if you continue using DHCP on your client yet can rely on always receiving the same IP address, you\u2019re having your cake and eating it, too. Which begs the question \u2013 why would you have a cake if you weren\u2019t going to eat it? Isn\u2019t that the purpose of cake?<\/p>\n

Step-By-Step<\/strong><\/p>\n

Fortunately, DD-WRT makes it easy to create static DHCP addresses for your network. Combining the best of both worlds, a static DHCP address allows your clients to continue receiving their network parameters automatically, yet you know exactly which IP address will be assigned.<\/p>\n

    \n
  1. Open a browser and connect to your router\u2019s administration page. The default address for DD-WRT is http:\/\/192.168.1.1, but may vary if you\u2019ve reconfigured it.<\/li>\n
  2. Go to the\u00a0Setup\/Basic Settings<\/em>\u00a0menu. The router may first ask you to log in with your administrator password. (The default is root\/admin). Scroll down the page to \u201cNetwork Address Server Settings (DHCP).\u201d<\/li>\n<\/ol>\n

    \"\"<\/p>\n

      \n
    1. Make a note of the pool of addresses the router uses when assigning dynamic IPs. Here, we see a pool of 100 addresses, beginning at 192.168.0.100 and ending at 192.168.0.200. It will be important later that your static DHCP address assignments fall\u00a0outside<\/em>\u00a0this pool. (If you make any changes here, be sure to save your settings.)<\/li>\n
    2. Go to the page\u00a0Administration\/Services<\/em>. Here\u2019s where the action is. Below the \u201cStatic Leases\u201d heading, click the \u201cAdd\u201d button to create a new DHCP entry field.<\/li>\n
    3. Enter three values: the MAC address of your client machine\u2019s network adapter, a host name for the machine, and the IP address you want it to be assigned. Choose any host name you like, such as \u201cwebserver\u201d or \u201cgameserver\u201d. Choose an IP address which follows the same pattern as those in your DHCP address pool (in our example, 192.168.0.x). Choose a number for\u00a0x<\/em>\u00a0which is outside the address pool seen in step 3 (in our example, 201).<\/li>\n<\/ol>\n

      \"\"<\/p>\n

      You can find the MAC address for your network adapter in either Windows XP or Mac OS X with a few clicks.<\/p>\n

      Windows XP<\/strong>
      \nClick\u00a0Start\/Settings\/Control Panel\/Network Connections<\/em>\u00a0and click the name of your network connection. Wired connections are typically named \u201cLocal Area Connection,\u201d while wireless connections are called \u201cWireless Connection\u201d. In the Status window, click\u00a0Support<\/em>, and in that window, click\u00a0Details<\/em>. Your MAC address is the series of hexadecimal pairs labeled \u201cPhysical Address\u201d. Use colons rather than dashes to separate the pairs in the DD-WRT interface.<\/p>\n

      \"\"<\/p>\n

      Mac OS X<\/strong>
      \nGo to the Dock\/System Preferences\/Network<\/em>. Click the\u00a0Ethernet<\/em>\u00a0tab. Your MAC address is labeled \u201cEthernet ID\u201d.<\/p>\n

      \"\"<\/p>\n

        \n
      1. With your MAC address, host name and chosen IP address entered into DD-WRT, be sure to click\u00a0Save Settings<\/em>\u00a0at the bottom of the page. If you want to add another static DHCP entry, you must save your settings first, then click\u00a0Add<\/em>\u00a0to create a new entry.<\/li>\n
      2. If you like, add a port forwarding entry for your new static DHCP address. In our example, we set up a Web server on our client PC. Our Web server listens for traffic on the default port 80. But our ISP blocks incoming traffic to port 80, because they don\u2019t want us running Web servers (ours is for private personal use, we\u00a0totally<\/em>\u00a0swear). Go to\u00a0Applications & Gaming\/Port Forwarding<\/em>\u00a0in the DD-WRT menu. Click\u00a0Add<\/em>\u00a0to create a new forwarding entry. We enter an identifier into the \u201cApplication\u201d field, in this case, \u201cwebserver\u201d. The router will listen for traffic on port 8088, so that we can connect from outside without being blocked by the ISP. Our destination IP address is the static DHCP entry created in step 5, and our destination port is where our Web server is actually listening, port 80. Be sure to check\u00a0Enable<\/em>\u00a0for this definition to take effect. And, of course,\u00a0Save Settings.<\/em><\/li>\n<\/ol>\n

        \"\"<\/p>\n

        You are now, as they say in the new Taco Bell ads which are vastly inferior to the ones with the talking Chihuahua, \u201cgood to go.\u201d Even if you don\u2019t run Web, game or other servers on your local machines, you never know when a stable, predictable IP address will come in handy.<\/p>\n

        Article courtesy of Wi-Fi Planet.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

        Open source router firmware such as DD-WRT does things the factory-installed stuff never offers. For example, you can give a computer the same IP address every time so you’ll always have remote access. by Aaron Weiss By now, you probably know that upgrading the near-legendary Linksys WRT54G series routers with free, often open-source firmware is one of the best bargains going. Replacement firmware typically offers a plethora of advanced router and firewall features rarely found on sub-$100 hardware. DD-WRT, a free, open-source firmware coded and distributed by \u201cBrainSlayer,\u201d has emerged as one of the leading, most powerful and also user-friendly <\/p>\n","protected":false},"author":2,"featured_media":5597,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/895"}],"collection":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/comments?post=895"}],"version-history":[{"count":0,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/895\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media\/5597"}],"wp:attachment":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media?parent=895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/categories?post=895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/tags?post=895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}