On Thu, May 23, 2013 at 07:35:29PM +0200, Matthias Schiffer wrote:
> > There is also a question of how BGP attribute on non-BGP route should be
> > interpreted by BGP protocol - either like BGP routes, or like non-BGP
> > routes with the attribute assigned by BGP export filter. I would prefer
> > t
On Fri, May 24, 2013 at 12:10:45AM +0200, Aragon Gouveia wrote:
> Hi,
>
> So I've seen this issue mentioned in past mailings, and the FAQ, but I
> think I might be experiencing a buggy form of it in Bird 1.3.10.
> ...
> Any ideas please? Before I start fumbling in source code... :)
Hello
What
On Wed, May 22, 2013 at 10:29:49AM -0700, Bao Nguyen wrote:
> Ondrej,
>
> You are correct, the issue is not related to OSPF but related to BIRD's
> ability to install a route into the kernel routing table. It look like the
> issue was that the new kernel doesn't have this option enabled (which is
Hi,
So I've seen this issue mentioned in past mailings, and the FAQ, but I
think I might be experiencing a buggy form of it in Bird 1.3.10.
In debug mode I'm getting this:
May 23 23:59:06 wugpi bird: device1: Scanning interfaces
May 23 23:59:06 wugpi bird: CTWUG: HELLO packet sent via eth0
Ma
On 05/22/2013 12:36 PM, Ondrej Zajicek wrote:
> On Fri, May 17, 2013 at 04:31:07PM +0200, Matthias Schiffer wrote:
>> There is no reason to overwrite attributes like AS path, next hop, etc. when
>> the
>> route source is not BGP. Preserving them has several advantages:
>>
>> * no attributes are l
