Reply to thread

Message

<blockquote data-quote="ForgottenSeer 58943" data-source="post: 707010">Subnetting and networking 101.192 scope is not reserved for private use, the second octet denotes the private Class C subnet. 10.0-10.255(CA), 172.16-172.32(CB), 192.168-192.168.255(CC). Many people falsley believe that 172 denotes a private subnet. Not correct - 172.15.0.0 would be public, whereas 172.16.0.0 would be private.Also, most people don&#039;t realize this, but you don&#039;t have to use private IP spaces defined by IANA. You can vary from it as you wish. You can use any range you want on your internal LAN including routable internet address ranges. The only problem it could manifest in is if a public website/server coincides with that scope there would be a routing loop. Also there is a chance your internal could be exposed publicly if your security isn&#039;t tight. I&#039;ve worked on corporate networks with a DHCP pool of 1,200 clients running on 169 public ranges. So it happens.</blockquote>

[QUOTE="ForgottenSeer 58943, post: 707010"] Subnetting and networking 101. 192 scope is not reserved for private use, the second octet denotes the private Class C subnet. 10.0-10.255(CA), 172.16-172.32(CB), 192.168-192.168.255(CC). Many people falsley believe that 172 denotes a private subnet. Not correct - 172.15.0.0 would be public, whereas 172.16.0.0 would be private. Also, most people don't realize this, but you don't have to use private IP spaces defined by IANA. You can vary from it as you wish. You can use any range you want on your internal LAN including routable internet address ranges. The only problem it could manifest in is if a public website/server coincides with that scope there would be a routing loop. Also there is a chance your internal could be exposed publicly if your security isn't tight. I've worked on corporate networks with a DHCP pool of 1,200 clients running on 169 public ranges. So it happens. [/QUOTE]

Verification