daffy said:
Aah.. now comes the fun Binary part

Its actually a bitmap that determans the bitmask on a .0.0 subnet
Warning: BINARY
if the address starts in 0 (ie: addresses from 0 up to 127.255.255.255) its a /8
if the address starts in 10 (ie: 128.0.0.0 - 191.255.255.255) its a /16
if the address tarts in 110 (ie: 192.0.0.0 - 223.255.255.255 ) its a /24
Any address above 224.0.0.0 is a Multicast address.. and wont really be applicable here.
Nice reference here.
(
http://www.eventhelix.com/RealtimeMantra/Networking/ip_routing.htm)
True, but in real life we use Subnetting to divide to existing ip ranges into smaller parts. Divide logical / physical networks...
Look at the following at is an extract from the public-route server
* 152.112.0.0 168.209.255.8 0 3741 5713 2018 i
* 152.158.80.0/22 168.209.255.8 0 3741 2686 i
* 155.159.0.0 168.209.255.8 0 3741 i
* 155.232.0.0 168.209.255.8 0 3741 5713 2018 i
* 155.234.0.0 168.209.255.8 0 3741 i
* 155.235.0.0 168.209.255.8 0 3741 i
* 155.236.107.0/24 168.209.255.8 0 3741 i
* 155.236.110.0/23 168.209.255.8 0 3741 i
the /23 /23 and /24 subnets are fine - I do understand the subnetting...
Then the ones without any slashes... These examples are on a class B subnet, meaning 255.255.0.0 subnet mask (/16). My initial question was if we can assume that all of them are /16 seeing that it's a class B (0.0)
But we do have other entries that specifically specifies / 16
*> 196.9.0.0/16 168.209.255.8 0 3741 2905 i
*
Hence, why specify the /16 only sometimes?
Think I do have the answer... Looking at the above example we see that it belongs to a class C network (/24), so the mask was specified with /16 because it deviates from the standards.
Thanks for all the input - Im quite ure this is how it works...
Any change that these entries will change?? I need to upload in to my Router - don't want to schedule a weekly update