Static Routing

William Herrin bill at
Fri Dec 8 22:25:58 CST 2017

On Fri, Dec 8, 2017 at 4:50 PM, Ryan Hamel <Ryan.Hamel at> wrote:
> I'm not implying HTTP, I'm implying a static route at each sites private
layer 3 router (it'll move to BGP in the future). The repository server
listens on the IP as well.
> My original question was the fact of using as a usable IP
address (not even caring about anycast).

> Internal private network that is reachable by clients.

Hi Ryan,

Clients meaning employee computers or clients meaning other networks who
subscribe to your service and connect with a VPN?

The the former, save yourself grief and use a different /32.

For the latter, it's semi-clever. It neatly avoids the problem of customers
using the same RFC1918 addresses as you. Even if they're using a subnet
like, a /32 route can usually override that one address
without ill effect.

It's only semi-clever because the .0 address is a corner case in the code
and corner cases are where bugs are most likely to happen.  And if you're
sending clients from that address to another host with a regular 172.16
address anyway...

Bill Herrin

> -------- Original message --------
> From: William Herrin <bill at>
> Date: 12/8/17 1:45 PM (GMT-08:00)
> To: Ryan Hamel <Ryan.Hamel at>
> Cc: nanog at
> Subject: Re: Static Routing
> On Fri, Dec 8, 2017 at 4:37 PM, Ryan Hamel <Ryan.Hamel at>
> wrote:
> > 1. A single known ip address that redirects to the closest internal repo
> server. redirects to a usable subnet ip in 172.16.xx.xx by
> static route.
> Hi Ryan,
> Maybe if would help if you write the extended version because that's about
> as clear as mud. First you asked about routing. Now you imply HTTP.
> Regards,
> Bill Herrin
> --
> William Herrin ................ herrin at  bill at
> Dirtside Systems ......... Web: <>

William Herrin ................ herrin at  bill at
Dirtside Systems ......... Web: <>

More information about the NANOG mailing list