Originally posted by: SONYFX
Is this arbitrary? Is there a specific meaning for address startgin with 192.168?
This is a "set" rule-of-tumb to avoid conflicts ... around the globe there are lot's of IPs give. For example, your ISP may give you an IP like 83.20.?.? (or something like that), a top DSN server (TLDs) will have another specific IP, ...
So to avoid conflicts, it's a set rule that private IPs should be set around 192.168.*.* ... that means you'll avoid conflict/missanderstandings (sp?) when managing IPs.
If your ISP gives you an IP 83.20.0.1 (for example), and you give your private network IPs in the range 83.20.0.1 - 83.20.0.100, it would be a real mess and it would potentially bring you big problems (if your network worked in the first place).
So hence the reason ...
<edit>
One more add ... if you ping
localhost, you're pinging the local machine ... and what if you ping
127.0.0.1 ? Well, you're pinging the local machine too ... it's another "rule" that 127.0.0.1 points to the local machine. If you start giving IPs from 127.0.0.1 to 127.0.0.100 you'll begin having problems, specially with the 127.0.0.1 one (that is, if your operating system let's you set 127.0.0.* as an IP, in the first place).
IP is a global identifier, and as a global identifier, must have some "rules" or the global integration of networks would be a pain.
</edit>