Static Routing 172.16.0.0/32

valdis.kletnieks at vt.edu valdis.kletnieks at vt.edu
Fri Dec 8 20:09:49 CST 2017


On Fri, 08 Dec 2017 03:13:57 +0000, Ryan Hamel said:
> Greetings,

> A colleague of mine has static routed 172.16.0.0/32 to a usable IP address,
> to have a single known IP address be static routed to a regions closest server.
> While I understand the IP address does work (pings and what not), I don't feel
> this should be the proper IP address used, but something more feasible like a
> usable IP in a dedicated range (172.31.0.0/24 for example).

Probably depends on what your colleague is trying to do.  Nothing in the
rules says the .0 address on a subnet is reserved (though you're in for a
surprise if there's any gear still on the net with a 4.2BSD stack).

> I would to hear everyone's thoughts on this, as this the first IP address in
> an RFC1918 range.

At some point, some chucklehead  is going to look at that .0.0 and mentally think /16,
and things will go pear-shaped pretty quickly....

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20171208/eaea9a9e/attachment.sig>


More information about the NANOG mailing list