Originally Posted by Leon
A static IP doesn't change. Hence the word static. You tell your computer what it's IP address is, and that's it.
A dynamic IP is dynamically assigned, and has a lease time associated with it. So your wifi router can hand out addresses to new devices as they come on your network. This is called DHCP. There will be a range of addresses (a pool) that the router has available to hand out. eg: 192.168.1.100 through 192.168.1.199. That lets a network have 99 DHCP devices, and leaves the lower and upper ends of the subnet for static addresses. That prevents your DHCP server from handing out an address to a new device that's already assigned to something else.
Dynamic Host Configuration Protocol - Wikipedia, the free encyclopedia
You want a static IP for your NAS. You don't really need one for your PC, but it never hurts to use one.
You also don't need to xx out the digits of your IP address if it's on a private subnet, which 192.168.*.* is. They are intentionally not internet routable just for that reason. My IP address is 192.168.1.100 right now, but only on my home network. Your actual IP address (the one that you use to get on the internet) is the IP address of your router. There are three private subnets, class A, B and C. The classes determine how many total hosts can be on that subnet.
192.168.1.x is a class C. The subnet is 192.168.1, and last octet is the host. So there can be 254 hosts on that subnet - 192.168.1.1 through 192.168.1.254. That's why your subnet mask is 255.255.255.0.
It looks complicated, but it's just some really simple math.
For basic home use, devices need to be on the same subnet to talk to each other. So if your NAS is 126.96.36.199.1, then your machine needs to also be 192.168.1.xxx. Enterprise level routing can let machines on completely different subnets talk to each other, but you don't really need to care about that. The other part of networking that you've probably had to configure, or at least have seen, is the default gateway. It's exactly what it sounds like - it's the "gateway" that your network traffic uses to get to the rest of the world. That's the INSIDE (the private IP range) address of your wireless router.
So when you visit MG, you type in "http://www.metalguitarist.org". Here's what happens, in really-layman's terms.
- Your computer looks to your DNS server (which your router tells you) and asks "what's the IP address of metalguitarist.org"
- The DNS server responds with "188.8.131.52"
- Your computer then says "Ok, how do I get there?"
- Your router says "You go through me, and I'm 192.168.1.125 on your side"
- Your computer says "Ok! Send me to MG!"
- Your router takes your traffic on the private side, and then tells Comcast/Verizon/Whoever - Hey, my real IP address is 184.108.40.206 (eg: some real IP address that your ISP gives it)
- That traffic goes to my server
- My server says "Here's the br00tz!" and sends the page.
- The page goes from my server, back to your router's "real" IP address
- Your router hands it over to the private IP address side
- Your browser displays the page.
Like magic n' shit.
If you can't hit diskstation.local, it's probably an outdated DNS record. When you type in an address (like metalguitarist.org, google.com, or diskstation.local), DNS is the service that translates that "friendly" name into the IP address. If you open a terminal window and type 'ping diskstation.local', does the IP address it returns match the NAS? If not, there's your problem. Hitting the IP address in your browser is no different than hitting the friendly name, at least in the case of the NAS.
TLDR: Read the last paragraph.