On Tue, Jun 12, 2018 at 01:59:47PM +0200, Ondrej Zajicek wrote: > On Tue, Jun 12, 2018 at 08:00:50AM +0530, knet solutions wrote: > > Hi, > > > > I am implementing this below topology (BGP IGP), > > > > > > R1--------------------------------R2------------------------------------------R3 > > (192.168.2.2) 192.168.2.1/1.1 192.168.1.2 > > > > Here > > > > R1 and R3 are bird routers > > R2 is RYU BGP Speaker (act as Route reflector). > > > > This is not working as expected. Bird routers(R1) sends error notification > > to R2. > > > > BIRD R > > > > Attached the packet traces. Can you help me to identify what went wrong? > > Hi > > Do you have any error messages in BIRD log?
Also according to pcap, it seems like mandatory NEXT_HOP attribute is missing: Update Message (2), length: 48 Originator ID (9), length: 4, Flags [O]: 192.168.1.1 Cluster List (10), length: 4, Flags [O]: 192.168.1.1 Origin (1), length: 1, Flags [T]: IGP AS Path (2), length: 0, Flags [T]: empty Updated routes: 10.2.1.0/24 Although it is true that in such case BIRD should just handle the the update as withdraw instaad of sending notification. But in general, it seems like a bug in RYU BGP Speaker. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."