Re: [Ryu-devel] Query BGP speaker

2018-06-12 Thread knet solutions
Thanks. the patch works fine. On Tue, Jun 12, 2018 at 11:38 AM, Iwase Yusuke wrote: > Hi, > > Hmmm... the current implementation seems not to suppose to have the locally > generated routes when configured itself as a Route Reflector. Only > supposed to > reflect the received routes. > > The atta

Re: [Ryu-devel] Query BGP speaker

2018-06-11 Thread Iwase Yusuke
Hi, Hmmm... the current implementation seems not to suppose to have the locally generated routes when configured itself as a Route Reflector. Only supposed to reflect the received routes. The attached patch fixes this problem? Thanks, Iwase On 2018年06月11日 20:36, knet solutions wrote: Hi Iwase

Re: [Ryu-devel] Query BGP speaker

2018-06-11 Thread knet solutions
Hi Iwase, When i configure route_reflector, RYU BGP Speaker couldnt establish the comminication with traditional bird router. My code snippet is as below, # code snippet self.bgp_speaker = BGPSpeaker(64511, router_id, ssh_console=True, ssh_po

Re: [Ryu-devel] Query BGP speaker

2018-05-30 Thread Iwase Yusuke
Hi, > All routers are same AS number. This means Ryu and other routers are connected with the iBGP(internal BGP) peering, right? On the iBGP, generally the received routes from other iBGP peers will not be advertised in order to avoid network loops. If you need to advertise the iBGP routers to o