[c-nsp] Looking for suggestions on how to link old colo with the new colo for routing purposes until new circuits are in place

[David Coulson]

Build an basic IP tunnel or IPSec connection between the two locations 
and treat it as a point to point for EIGRP, OSPF or BGP?

Dan Troxel wrote:
> The issue is we cannot advertise to the net any sub /24 nets. Thus, we need
> to control those some how with an internal mesh - but the old and the new
> locations are not physically connected in anyway (yet), except through the
> internet.
>
> -----Original Message-----
> From: Steve Bertrand [mailto:cisco at ibctech.ca] 
> Sent: Friday, September 14, 2007 1:14 AM
> To: Dan Troxel
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Looking for suggestions on how to link old colo with
> the new colo for routing purposes until new circuits are in place
>
>   
>> Problem: Since we cannot run BGP on any network smaller than a /24, how do
>> we connect all the networks together, so that we can route internet
>> connectivity to the small subnets (smaller than class C)? 
>>     
>
> I'm very new to this game, but from my understanding I will try. Please
> correct me if I am wrong, or if I am misunderstanding the problem:
>
> If you control all of the network routers, could you not advertise the
> sub /24 nets across your infrastructure via iBGP, and then aggregate
> them all together at your border routers that face the 100Mbps
> connections and advertise them aggregated from there?
>
> >From what I do know for fact, is that adding in any type of encryption
> just to do routing adds a burden of overhead that is apparently not what
> you want.
>
> Or do I have this all wrong?
>
> Steve
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>