Le 21/10/2011 11:18, Mathias Wolkert a écrit :
Hi all
As I'm moving forward on my bird implementation, the bugs/change
requests get smaller and smaller.
Now I'm down to picky little details such as default config path in Debian.
If I'm not mistaken, it's good Debian behavior to have daemon spec
Le 19/12/2010 08:44, Nick a écrit :
On Fri, Dec 17, 2010 at 09:06:16AM -0300, Andrew Latham wrote:
Sorry, I am a bit of a lurker on this list but I must chime in. In
the last 15 years I have watched many projects grow and let me say
that community documentation is a good step. It is hard and c
Le 03/09/2010 16:09, Ondrej Zajicek a écrit :
On Tue, Aug 31, 2010 at 02:36:38PM +0200, Stéphane Bunel wrote:
Hi there,
I'm working on a use case with two routers (foundry) emiting RIPv2
messages in multicast over an ethernet link and one Ubuntu/Linux/64
server with BIRD configured
Le 01/09/2010 10:33, Ondrej Zajicek a écrit :
On Wed, Sep 01, 2010 at 10:18:53AM +0200, Stéphane Bunel wrote:
Hi,
Morning at 09:54 (GMT+2)
r...@srtools:~# birdc
BIRD 1.2.4 ready.
bird> show memory
BIRD memory usage
Routing tables: 12 MB
Route attributes: 4592 B
Protocols: 34
is not a normal behavior isn't it ?
Regards,
Stéphane.
Le 31/08/2010 14:36, Stéphane Bunel a écrit :
Hi there,
I'm working on a use case with two routers (foundry) emiting RIPv2
messages in multicast over an ethernet link and one Ubuntu/Linux/64
server with BIRD configured as a quiet
Hi there,
I'm working on a use case with two routers (foundry) emiting RIPv2
messages in multicast over an ethernet link and one Ubuntu/Linux/64
server with BIRD configured as a quiet RIP listener.
Configuration is simple and working well. But as you can see below,
BIRD seems to eat memo
