Help: HOWTO buy IP address blocks from ARIN?

Bill Freeman ke1g.nh at gmail.com
Tue Jan 13 14:29:27 EST 2015


"non-routable" range IPs are what are used where I'm working now, a company
with several thousand employees, at perhaps a dozen sites across North
America.  Making it work requires an infrastructue team.  Going outside
requires going through a proxy.  Subnets at other sites are, I presume,
routed to the proxy, or possibly to a different proxy, which routes to the
other site over a VPN or other tunnel.  I'm not on the infrastructure team,
and don't know the details.  But we do make it work.  (Getting the proxy
settings wrong on your local box, however, is a constant source of
entertainment.)

On Tue, Jan 13, 2015 at 2:21 PM, Joshua Judson Rosen <rozzin at hackerposse.com
> wrote:

> On 2015-01-13 13:45, John Abreau wrote:
> > If I were doing it, I'd consider setting up several redundant vpn
> servers.
> >
> > RFC1918 defines three private address blocks:
> >
> >      10.x.x.x/8
> >      172.16.x.x/12
> >      192.168.x.x/16
> >
> > I'd start with 3 vpn servers, each using one of these blocks. Odds are
> one of
> > them would work at a given customer site. Maybe throw in a fourth one
> with a
> > small pool of public addresses for the hypothetical pathological cases
> where the
> > customer is using all three private address blocks.
>
> And what subnet would you put all of your fixed infrastructure on to
> guarantee
> that hosts coming in through all of those VPNs can actually route to it?
> And to each other?
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20150113/5f798371/attachment.html 


More information about the gnhlug-discuss mailing list