Re: Protocol direct

On Fri, Dec 22, 2017 at 08:41:30AM +0100, Daniel Czerwonk wrote: > > Miłosz Oller > > 22. December 2017 at 00:46 > > protocol direct { > > ipv4; > > ipv6; > > interface "*"; > > } > > > > And it doesn't announced any local prefix to upstream peers, only to > >

Re: Reacting to Link Failure

On Fri, Dec 22, 2017 at 08:46:28AM -0500, Liam Kelly wrote: > Is there any way for other programs to listen for Bird events regarding Link > Failure (IE: OSPF/BFD dead neighbor)? > > Bird is great, but the modems and device drivers I am working with are > not. I can get some pretty odd ‘zombie’

Re: bug in bird6 1.6.2 and 1.6.3

On Fri, Dec 22, 2017 at 03:54:10PM +0300, Михаил Манерко wrote: > Hello. > > I'm using a bird6 1.6.3. > it runs ospfv3 and radv protocols on all interfaces of the system. Hello According to config, it runs OSPFv3 just on vlan7. Is that true? > Today I noticed that the launch of birdc6, causes s

Re: Bird Installation Guide

On Fri, Dec 22, 2017 at 11:38:27AM +0530, Pardeep Sharma wrote: > Hi All, > > We are purposing L3 IXP design to one of our customer as below, where all > ISP routers will have one eBGP peering with Quagga/Bird Route-Server. As > we are new in IXPs design so would like to take your suggestions if

Re: One BGP session flapping but not the other

Hi, By digging a bit more, I found that the issue seems to be with CARP. I found that the mastership is flapping between the routers as budic is a bit overloaded: Dec 22 23:42:32 nominoe kernel: carp: 4@em1.31: BACKUP -> MASTER (master timed out) Dec 22 23:42:32 nominoe kernel: carp: 4@em1.31: MA

Re: Bird Installation Guide

Thanks.. On 23 December 2017 at 18:59, Ondrej Zajicek wrote: > On Fri, Dec 22, 2017 at 11:38:27AM +0530, Pardeep Sharma wrote: > > Hi All, > > > > We are purposing L3 IXP design to one of our customer as below, where all > > ISP routers will have one eBGP peering with Quagga/Bird Route-Server.