Op 2-11-2011 12:47, Ondrej Zajicek schreef:
protocol bgp rr_cl_ft by rr_client_bb {
neighbor 10.4.7.2 as 65000;
}
(Not being native english speaker i am not sure whether 'by'
is really the most apt keyword, any comments on that? Perhaps
'from'?)
Programming languages tend to use 'inherits' or
Op 31-5-2011 2:00, Ondrej Zajicek schreef:
On Mon, May 30, 2011 at 05:45:20PM +0200, Ivo Smits wrote:
...
Disabling this peer fixed the crashes, enabling the peer brought them
back. After some investigation, it turned out that this BGP peer sends
an ORIGIN attribute even with BGP packets that
After running into trouble with bird 1.2.3 trying to display 32 bit AS
numbers (show route all resulted in a segmentation fault), we decided to
upgrade to 1.3.1. Unfortunately 1.3.1 crashed even sooner than 1.2.3.
One of the logs looks like this:
bird: UFO_4_0_bgp > added 1.0.49.0/24 via 1.82
I've created attached patches to prevent BGP route loops from turning
into ghosts (issue reported earlier to the mailing list:
http://marc.info/?l=bird-users&m=129433651229774&w=2).
Instead of completely ignoring received BGP routes containing the
router's own AS number, it should now handle t
Op 6-1-2011 20:27, Martin Barry schreef:
$quoted_author = "Ivo Smits" ;
On the dn42 network (http://www.dn42.net) we have been seeing quite
a few BGP ghost routes lately. After some research, it turns out
that bird may not correctly handle received AS-paths containing the
own AS nu
Hello,
On the dn42 network (http://www.dn42.net) we have been seeing quite a
few BGP ghost routes lately. After some research, it turns out that bird
may not correctly handle received AS-paths containing the own AS number.
Bird ignores incoming BGP routes containing the local AS number -
comp
