Hi IWAMOTO,
I updated the changes in this commit (on top of your route reflector change)
https://github.com/sureshkvl/ryu/commit/aebf3974d121134931d79805b35f8f252db9d7a5
Could you review?
How to submit this in upstream?. Is it pull request or some other process?
Thanks
suresh
On Thu, Jun 21, 2018 at 8:18 AM, IWAMOTO Toshihiro <iwam...@valinux.co.jp>
wrote:
> On Thu, 21 Jun 2018 00:39:17 +0900,
> knet solutions wrote:
> >
> > [1 <multipart/alternative (7bit)>]
> > [1.1 <text/plain; UTF-8 (7bit)>]
> > In peer.py file, PEER port number is hard coded to BGP Port Num.
> >
> > peer_address = (self._neigh_conf.ip_address,
> > const.STD_BGP_SERVER_PORT_NUM)
> >
> > I think, it can be configurable parameter from the API.
>
> It should default to 179 but it's good to be configurable.
> Can you make a patch?
>
> > On Wed, Jun 20, 2018 at 4:15 PM, knet solutions <
> knetsolutio...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > neighbor_add api doesnot have the "port number" parameter.
> > >
> > >
> > > For examples
> > >
> > > Traditional BGP Router <-----------------------------
> ---------------------->
> > > RYU BGP Speaker
> > > (BGP runs in port 180)
> > >
> > >
> > >
> > > In the RYU BGP Speaker,
> > > bgp_speaker.neighbor_add(remote_router_id, remote_as)
> > >
> > > no option to specify the remote port number.
> > >
> > > Any suggestions?
> > >
> > > Thanks
> > > suresh
> > >
>
--
*Regards, *
*Knet solutions.*
https://github.com/knetsolutions/KNet
http://knet-topology-builder.readthedocs.io/
http://knetsolutions.in/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
