Yeah, I'm not sure there's a great answer to this. Even just choosing random blocks of public IP's can get you into trouble if the other company has guys that think just like you. :)
-Adam On Wed, Oct 28, 2015 at 4:41 PM, David Lang <da...@lang.hm> wrote: > On Tue, 27 Oct 2015, John Stoffel wrote: > > And using public IP spaces... really dumb outside a lab environment. >> I mean how hard is it to use 10.x.x.x for everything these days? >> > > that depends, how hard is it to change your IPs when you merge with > someone else who is already using the 10.x.x.x and you now need to > deconflict things. > > or how hard is it to setup a VPN to a business partner who's using > 10.x.x.x internally and has conflicting addresses. Especially if the two > servers that need to connect are both 10.1.1.1 > > Now, think about a company that's connecting to hundreds or thousands of > businesses that all have "just use 10.x.x.x" as their policy. > > that's where things get ugly and using publicly allocated addresses for > internal stuff is attractive because it already de-dups the ranges. > > David Lang >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
