On Nov 30, 2009, at 21:18 , Ondrej Zajicek wrote:
...
I checked the source for the loop check and it seems that there are some
problems in that code.
ok.
Second, in some situations the loop check does not work and that causes
that the first problem manifests less often :-).
allright
On Dec 1, 2009, at 13:09 , Ondrej Zajicek wrote:
On Tue, Dec 01, 2009 at 10:48:56AM +0100, Wolfgang Hennerbichler wrote:
Every route passes through at most one pipe according to your expected
filter behavior?
well, a route can be distributed from one table to let's say 10 other
tables by
On Mo, 23.11.2009, 18:09, Ondrej Zajicek wrote:
It was clear for me. I checked route refresh specification and it
seems to be pretty easy to implement (at least 'the requesting side'
of it), therefore i hope we can implement it soon.
woooh, great news, thank you so much!
BTW, what kind
On Tue, Nov 24, 2009 at 04:03:32PM +0100, Wolfgang Hennerbichler wrote:
- per protocol request for route refresh
hm. I'm not exactly sure how you mean this - something like:
bird restart protocol R1234 soft
Yes.
like
bird configure route-refresh
= i'd prefer the per protocol thing
On Nov 23, 2009, at 08:19 , Wolfgang Hennerbichler wrote:
On Nov 20, 2009, at 16:17 , Ondrej Zajicek wrote:
On Fri, Nov 20, 2009 at 02:19:05PM +0100, Wolfgang Hennerbichler wrote:
Fellow Bird Users,
Now I realized that if I changed the definition for 'allnet' and do a
'configure soft'
On Fri, Nov 20, 2009 at 02:19:05PM +0100, Wolfgang Hennerbichler wrote:
Fellow Bird Users,
Now I realized that if I changed the definition for 'allnet' and do a
'configure soft' these routes that are added or removed to 'allnet' are
not rejected or added, because it seems that there is no
