nanog mailing list archives

Re: Static Routing 172.16.0.0/32


From: Ryan Hamel <Ryan.Hamel () quadranet com>
Date: Fri, 8 Dec 2017 21:37:50 +0000

1. A single known ip address that redirects to the closest internal repo server. 172.16.0.0/32 redirects to a usable 
subnet ip in 172.16.xx.xx by static route.

2. Internal private network that is reachable by clients.

-------- Original message --------
From: William Herrin <bill () herrin us>
Date: 12/8/17 1:34 PM (GMT-08:00)
To: Ryan Hamel <Ryan.Hamel () quadranet com>
Cc: nanog () nanog org
Subject: Re: Static Routing 172.16.0.0/32



On Thu, Dec 7, 2017 at 10:13 PM, Ryan Hamel <Ryan.Hamel () quadranet com<mailto:Ryan.Hamel () quadranet com>> wrote:
A colleague of mine has static routed 172.16.0.0/32<http://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<http://172.31.0.0/24> for example).

Hi Ryan,

Some clarifications:

1. You say, "static routed to a regions closest server." What do you mean by that? A static-routed anycast address?

2. In what reachability context? Is this a private network? An ISP network where the reachability should be the ISP and 
its customers?

Regards,
Bill Herrin


--
William Herrin ................ herrin () dirtside com<mailto:herrin () dirtside com>  bill () herrin us<mailto:bill () 
herrin us>
Dirtside Systems ......... Web: <http://www.dirtside.com/>

Current thread: