What does an IP address mean? Why can't external networks starting with 192.168 connect? One image clearly distinguishes between public and private assets

last week, my cousin was on a business trip and left me with the remote access to Synology at home to keep an eye on. He sent me the NAS address 192.168.0.30. I typed it into my own home computer, circled around for half a minute, but couldn't connect—not because of their internet speed, but because this address simply couldn't get out of their door.

Later, I told him plainly: Your number is for the apartment in the community, with hundreds of thousands of 192.168.0.30 numbers nationwide. The routers outside have no idea whose door to knock on. After this incident, I thought, IP addresses are seen every day, and if you really gave a clear explanation, most people would really get stuck. This article will break it down and explain it all in detail.

What exactly is

IP: 32 bits split into four segments

IP address is the number assigned to networked devices. The widely used IPv4 version has 32 bits per address, broken into four segments with 8 bits per segment, separated by dots in between, for example, 192.168.31.108. Each segment can represent 0 to 255, and if all four segments are arranged together, there are about 4.3 billion accounts in total.

43 sounds like a lot, but with 8 billion people worldwide, each person has two phones, a computer, and a camera, and that's all that's going to blow. In the 1990s, it was already clear that accounts weren't enough, so IPv6 — 128-bit — was created, with so many accounts that you could write one for every grain of sand on Earth. I previously wrote a separate article about the IPv6 address string that looks like garbled text starting with 240e how to read IPv6 addresses; this article only covers the old IPv4.

four segments of numbers, you can also see some tricks: the first few segments correspond to "which residential complex," while the latter segments represent "which unit in the community." Specifically, the first few paragraphs count the community, the last few count the room number, and the subnet mask decides. I wrote about what the masking 255.255.255.0 actually handles Here, just remember the rough idea of "Number = Neighborhood Name + Room Number" is sufficient.

want to check your device's number, you can find it in three places: on the computer command line, type ipconfig to check the IPv4 line; View the WiFi detail page on the phone; The router's backend device list is the most comprehensive; whoever picks up a few numbers will display it all in one screen. After reading, it's recommended to take a screenshot and save it. Later, when a device runs out, it's much faster to find people by account than to unplug power one by one.

Public and Private IPs: The critical watershed

house numbers and house numbers in communities worldwide. Among the 4.3 billion accounts, a large portion was deliberately circled and ruled to only be used at the doorstep, with no validity outside the door—this is a private address. The rules for land RFC1918 are written in this document, consisting of three sections:

home routers almost always come out of the factory with the 192.168 range, so for your home, my home, and my cousin's home, all backend addresses start with 192.168. Countless communities use the same room numbers—why not fight? Because private accounts are useless when you step out: internet routers see the address in these three segments and just throw away the package, refusing to forward. This is also why you always have to screen the 192.168.1.108 at home at the office, which never works.

how do internal network devices get online? Relying on the router as a translator. With the internal room number 192.168.31.108 on your phone, go out. First, swap the router to your broadband public IP before sending it out. The returned packet is translated and distributed to the corresponding device. This craft is called NAT. For gamers familiar with NAT 1/2/3, it's about how it works. NAT the article about the genre I wrote about how to check and modify. A public account with dozens of private accounts, 4.3 billion accounts, barely held on to this day.

there's another common misconception: which segment you use at home isn't predestined; the number of LAN ports you set to is exactly what your whole family uses. My AX3000T was set to 192.168.31.1 back then, so the whole family was 31.x; my cousin's Mercury factory default was 192.168.0.1, but his whole family had 0.x. The public IP outside the door is issued by the carrier, and you don't have the final say—it might even drift every now and then—my home Telecom line switched from a number starting with 117.136 to a number starting with 111.72. If you want to pin it, you have to rely on DDNS, but that's another story.

those strange addresses that look alike, each has its own meaning

besides public and private ones, there are also several special sections that you encounter daily during troubleshooting. Knowing them all can help you avoid detours:

169.254 part: the optical modem was having a flashback, the computer got a number starting with 169.254, the webpage wouldn't open but the network card looked fine, 192.168.1.1 The that can't be opened has written about how to save yourself. 0.0.0.0 may look mysterious, but it's actually a 'if you can't recognize anything else, just leave it to me' safety net. the routing table article when discussing route print.

100.64 One more word in this passage. My home has two broadbands; the main line for Telecom is a genuine public IP, and the secondary line I got from China Mobile started with 100.89—a patch of users sharing a small group of public network exits. Normally, watching videos doesn't feel like it, but when you're out, even the home NAS is overwhelmed. If you want to know what type of broadband your company has, you can check in three steps. how to check public networks IP that article is thoroughly covered.

who sends IPs, why does the number change themselves

The home IP is issued by the router's DHCP, like the property management issuing the number, and it's rented—when the lease expires, the device is reconnected, the router restarts, the number can change. DHCP article I broke down the four steps to issuing the number. NAS and printers—devices that people want to find are useless once the rules change. You have to stick to this: either do DHCP static binding on the router, or manually fill in static IP addresses on the device. Both have their pros and cons. comparison the article on static IP binding. If the

account is heavily issued, it causes IP conflicts, with two devices competing for a room number, causing the network to be unstable and unresponsive. You don't need to install any tools to check it; arp -a just checks whether the MAC behind the same IP has swapped faces. ARP the entire process is clear. There's also a scenario where both devices feel they should use 192.168.1.1, and the optical modem and router are fighting over the same IP. Who should let go has to be strict? the article on IP conflicts the judgment method.

IP, MAC, gateway, mask—each of these four roles is handled

these concepts are the easiest to mix together. I used my cousin's Synology machine to strangle it together. 192.168.0.30 is its IP, room number, and can be changed; The string starting with 00-11-32 is MAC, the ID card printed in the network card pre-installed. I have written separately about the difference between MAC and IP the difference; 192.168.0.1 is the gateway, the community communication room. All packages leaving the community are handed over to it. the gateway article about what happens if you fill in the wrong information; 255.255.255.0 is the mask, which numbers count as direct calls within the same community and which must be sent to the relay room. By the way, the last time Synology couldn't connect was because his computer had a Win11 signature issue. isn't the same this time—the number was right that time, but the handshake rules have changed.

in short, everyone goes their separate ways: IP handles 'what number are you', MAC manages 'which device are you' for, gateway manages 'who you go out looking for', mask manages 'does it count as a neighbor?' The four of them each did their own thing, and none of them could get online.

back to my cousin's NAS: How do you even get in from outside

Once you figure out whether it's public or private, the idea for remote access is smooth: if your private account can't leave the house, there are two options—either let the bag outside the door in, or let the device at home come out to pick you up.

the premise for the former, your own broadband really has a public IP address. If your phone starts with 100.64, give up and call 10,000 to see if they can provide it. With a public IP address, you can forward ports on the router, directing a high-level public port to the NAS's private number. port forwarding and the DMZ have complete steps. The latter offers more options: Synology's QuickConnect, FRP relay, or setting up a VPN on the router to connect home yourself. This offers better security and freedom. VPN the post about going home I ran three routes. My cousin's broadband happens to have real public internet, so they use public IP and port forwarding, and it's clear in one go.

wrap up and give the order of judgments:

IP essentially a numbering system. Distinguishing between "effective when going out" and "valid only at home" gives you a clear direction for identifying most network issues. First, check which segment the account belongs to, then check who posted it, and finally check if the account has collided with anyone—I've used this sequence for years, and it's much more effective than restarting randomly.