On 2 Sep 2010, at 5:30 PM, Graham Beneke wrote:
> I have been asked to investigate moving an entire network to multi-hop on all
> the eBGP sessions. Basically all upstreams, downstreams and peers will eBGP
> with a route reflector located in the core. This RR will be some kind of
> quagga or s
On Sep 2, 2010, at 2:30 AM, Graham Beneke wrote:
> I have been asked to investigate moving an entire network to multi-hop on all
> the eBGP sessions. Basically all upstreams, downstreams and peers will eBGP
> with a route reflector located in the core. This RR will be some kind of
> quagga or
On 02/09/2010 10:30, Graham Beneke wrote:
> I have been asked to investigate moving an entire network to multi-hop
> on all the eBGP sessions. Basically all upstreams, downstreams and peers
> will eBGP with a route reflector located in the core. This RR will be
> some kind of quagga or similar box.
On Thu, Sep 2, 2010 at 11:30 AM, Graham Beneke wrote:
> I have been asked to investigate moving an entire network to multi-hop on
> all the eBGP sessions. Basically all upstreams, downstreams and peers will
> eBGP with a route reflector located in the core. This RR will be some kind
> of quagga or
The last company I worked for moved to eBGP Multi-Hop where there were
two connections to the same provider (same AS). This allowed them to
utilize both links in both directions vs only one link in one direction
and have failover.
As you have mentioned link state detection gets a bit crazy with t
>> The dev guys want to be able to poke at the BGP feeds directly and do
*magic* that standard router aren't capable of.
This should scare you in a significant manner.
-Jack Carrozzo
On Thu, Sep 2, 2010 at 5:30 AM, Graham Beneke wrote:
> I have been asked to investigate moving an entire networ
6 matches
Mail list logo
