Hi Iwase,
Thanks . It works nicely :)
Thanks
Suresh.
On Fri, Jun 1, 2018 at 12:09 PM, Iwase Yusuke <iwase.yusu...@gmail.com>
wrote:
> Hi Suresh,
>
> > 1) Routes(for extenal BGP Routers) on the RYU Host required for return
> traffic
> > to reach OF Switch. (i think, i have to add manual routing entry)
>
> Yeah, you need to install flows manually to forward ARP and BGP packets
> before
> starting Ryu BGP Speaker. This can be implemented by using Ryu's OpenFlow
> components, I guess.
>
> > 2)The major second problem is "router id", which one to be used as
> router "id"
> > in the BGP Speaker. Ryu host ip ??
>
> I think this should follow the BGP convention. AFAIK, in most case, the
> Router
> ID uses the own loopback IPv4 address for iBGP, and the source IPv4 address
> against its neighbor for eBGP. (Or it is depending on your network
> design...)
>
> Thanks,
> Iwase
>
>
> On 2018年06月01日 12:32, knet solutions wrote:
>
>> Hi Iwase, Yi,
>>
>> Thanks for the detailed explanation. Let me setup this and try.
>>
>> This solves some extend. But i guess, this two problems will be
>> addressed.
>>
>> 1) Routes(for extenal BGP Routers) on the RYU Host required for return
>> traffic to reach OF Switch. (i think, i have to add manual routing entry)
>>
>> 2)The major second problem is "router id", which one to be used as router
>> "id" in the BGP Speaker. Ryu host ip ??
>>
>> I am making ovs switch as ROUTER(it has own IPs for each interfaces). I
>> want to use those IP for advertising routes.
>>
>> Let me experiment and come back.
>>
>> Thanks
>> Suresj
>>
>>
>>
>> How about reverse di
>>
>> On Fri, Jun 1, 2018 at 5:13 AM, Iwase Yusuke <iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com>> wrote:
>>
>> Hi,
>>
>> > I believe the high level topology which Iwase mentioned looks like:
>> > <image>
>>
>> Great! Thanks Yi! That's exactly what I wanted to describe!
>>
>> > To connect from Ryu to OF-Switch is simple, all you need is to
>> connect
>> > NIC/interface from your Ryu machine to the OF-Switch with a
>> ethernet cable ;)
>>
>> FYI, if your Ryu is running on the same host with your OVS, you can
>> use a "tap"
>> device to create a port for BGP link. Or if you can assign IP address
>> to OVS
>> bridge device, we can use the reserved port "OFPP_LOCAL" for BGP link.
>>
>> e.g.)
>> If Ryu BGP Speaker will listen on "10.0.0.1" and OVS bridge name is
>> "s1";
>> $ sudo ip addr add 10.0.0.0/24 <http://10.0.0.0/24> dev s1
>> $ sudo ip link set s1 up
>> Then, Ryu BGP Speaker can listen on the OFPP_LOCAL port of "s1".
>>
>> Thanks,
>> Iwase
>>
>> On 2018年05月31日 22:59, Yi Tseng wrote:
>>
>> Hi,
>>
>> I believe the high level topology which Iwase mentioned looks
>> like:
>>
>> You need to config Ryu BGP speaker so Ryu BGP speaker can send BGP
>> advertise to external BGP speaker, vice versa.
>>
>> For OF-Switch, you need to install flows to it so it can forward
>> both
>> ARP and BGP messages between Ryu BGP speaker and external BGP
>> speaker
>>
>> To connect from Ryu to OF-Switch is simple, all you need is to
>> connect
>> NIC/interface from your Ryu machine to the OF-Switch with a
>> ethernet
>> cable ;)
>>
>>
>> 2018-05-31 20:31 GMT+08:00 Yusuke Iwase <iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com> <mailto:iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com>>>:
>>
>> Hi,
>>
>>
>> 1) BGP Speaker, Do we need to specify a configuration to
>> connect to
>> openflow switch?, instead of listening on a bgp port?
>>
>>
>> I guess no special configuration is required. BGP Speaker
>> should
>> act as a
>> “host” connecting to your OpenFlow network.
>>
>> 2) In Openflow switch, how do we configure send the
>> packets to
>> BGP Speaker
>> on separate channel. ?
>>
>>
>> Not so complex, just execute OUTPUT action to forward BGP
>> packets
>> (also ARP)
>> to the port connecting to Ryu BGP Speaker’s host.
>> For example, if tcp_dst=179 then output to port 1 or so.
>>
>> Thanks,
>> Iwase
>>
>> 2018/05/31 18:25、knet solutions <knetsolutio...@gmail.com
>> <mailto:knetsolutio...@gmail.com>
>> <mailto:knetsolutio...@gmail.com
>> <mailto:knetsolutio...@gmail.com>>>のメール:
>>
>> Hi Iwase, Logically i understood . But technically i
>> dont
>> know how to do it.
>>
>> 1) BGP Speaker, Do we need to specify a configuration to
>> connect to
>> openflow switch?, instead of listening on a bgp port?
>>
>> 2) In Openflow switch, how do we configure send the
>> packets to
>> BGP Speaker
>> on separate channel. ?
>>
>>
>> Sorry about more questions.
>>
>> Thanks
>> Suresh.
>>
>> On Thu, May 31, 2018 at 2:37 PM, Yusuke Iwase
>> <iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>
>> <mailto:iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com>>> wrote:
>>
>> Hi,
>>
>> Just I mean Ryu BGP Speaker should connect to the
>> OpenFlow
>> port on
>> OF-Switch as the same as the traditional routers.
>> I want to describe we should not use the
>> Controller-Switch
>> channel to
>> receive BGP packets (e.g. receive BGP packets via
>> Packet-In) and
>> should separate the link for BGP from that for
>> OpenFlow.
>>
>> Thanks,
>> Iwase
>>
>> 2018/05/31 17:34、knet solutions <
>> knetsolutio...@gmail.com
>> <mailto:knetsolutio...@gmail.com>
>> <mailto:knetsolutio...@gmail.com
>> <mailto:knetsolutio...@gmail.com>>>のメール:
>>
>> Hi Iwase ,
>> thanks for the response.
>>
>> Regarding the below line,
>>
>> >The BGP port on Ryu is connected as a "to host"
>> port
>> onthe OF-Switch,
>>
>> I couldnot understand this point. How to
>> configure
>> this, and little
>> more details about this.
>>
>> Can you share something more about this.
>>
>> Thanks
>> Suresh.
>>
>>
>> On Thu, May 31, 2018 at 12:02 PM, Iwase Yusuke
>> <iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com> <mailto:
>> iwase.yusu...@gmail.com
>>
>> <mailto:iwase.yusu...@gmail.com>>> wrote:
>>
>> Hi Suresh,
>>
>>
>> > Query1)
>> > Can we use the RYU BGP Speaker libaray, in
>> this
>> use case?
>>
>> Yes.
>> I guess that use case is what exactly Ryu
>> BGP speaker
>> implementation is
>> targeting.
>>
>> > if yes, could you provide some guide lines
>> on how
>> to use it.
>>
>> Sorry, I have no good document for such, but
>> for
>> example, the
>> following
>> architecture is one of the candidates.
>>
>> Ryu
>> OpenFlow || BGP
>> OF-Switch -------- Router
>>
>> Ryu has two (or more) connections with the
>> OF-Switch, one is for
>> OpenFlow and
>> the other is for BGP. The BGP port on Ryu is
>> connected as a "to
>> host" port on
>> the OF-Switch, then the OF-Switch will
>> forward BGP
>> packets (TCP
>> port = 179) to
>> Ryu's BGP port and the other packets will be
>> forwarded based on
>> the OpenFlow
>> table.
>>
>> Thanks,
>> Iwase
>>
>>
>> On 2018年05月23日 21:33, knet solutions wrote:
>>
>>
>> The BGP Speaker example shows that, the
>> RYU BGP
>> Speaker is a
>> separate process which handles packets
>> directly
>> from the
>> socket/kernel (not via Openflow
>> encapsualtion).
>>
>>
>> My use case some thing like below,
>>
>> In this below diagram, Tradiational BGP
>> Router
>> (Bird routing
>> daemon) run BGP and connect to the
>> openvswtich
>> managed by the
>> RYU controller. I would like to enable
>> the
>> BGP application
>> in the controller, so that when the BGP
>> Packet
>> comes to the
>> switch, switch sends the packet to the
>> RYU ,
>> RYU will use BGP
>> Speaker to manage the control plane for
>> this
>> siwtch1.
>>
>> -------------------------------------------
>> |---------------------
>> Traditional BGP Router |
>> ----------------------------------|switch1
>> |
>> (Bird Router) |
>> | |
>> ------------------------------------------
>> ----------------------
>>
>> Query1)
>> Can we use the RYU BGP Speaker libaray,
>> in this
>> use case? if
>> yes, could you provide some guide lines
>> on how
>> to use it.
>>
>>
>> -- */Regards,
>> /*
>> */Knet solutions./*
>> Suresh.
>> https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>
>> <https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>>
>> <https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>
>> <https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>>>
>> http://knet-topology-builder.readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>
>> <http://knet-topology-builder.
>> readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>>
>> <http://knet-topology-builder.
>> readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>
>> <http://knet-topology-builder.
>> readthedocs.io/
>> <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://Slashdot.org>!
>> http://sdm.link/slashdot
>>
>>
>>
>> ______________________________
>> _________________
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> <mailto:Ryu-devel@lists.sourceforge.net>
>> <mailto:Ryu-devel@lists.sourceforge.net
>> <mailto:Ryu-devel@lists.sourceforge.net>>
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> <https://lists.sourceforge.net/lists/listinfo/ryu-devel>
>> <
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> <https://lists.sourceforge.net/lists/listinfo/ryu-devel>>
>>
>>
>>
>>
>> -- */Regards,
>> /*
>> */Knet solutions./*
>>
>> https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>
>> <https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>>
>> http://knet-topology-builder.readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>
>> <http://knet-topology-builder.readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>>
>> http://knetsolutions.in/
>>
>>
>>
>>
>> -- */Regards,
>> /*
>> */Knet solutions./*
>>
>> https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>
>> <https://github.com/knetsolutions/KNet
>> <https://github.com/knetsolutions/KNet>>
>> http://knet-topology-builder.readthedocs.io/
>> <http://knet-topology-builder.readthedocs.io/>
>> <http://knet-topology-builder.readthedocs.io/
>> <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 <mailto:Ryu-devel@lists.source
>> forge.net>
>> <mailto:Ryu-devel@lists.sourceforge.net
>> <mailto:Ryu-devel@lists.sourceforge.net>>
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> <https://lists.sourceforge.net/lists/listinfo/ryu-devel>
>> <https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> <https://lists.sourceforge.net/lists/listinfo/ryu-devel>>
>>
>>
>>
>>
>> -- Yi Tseng (a.k.a Takeshi)
>> Taiwan National Chiao Tung University
>> Department of Computer Science
>> W2CNLab
>>
>> https://takeshi.tw
>>
>>
>>
>>
>> --
>> */Regards,
>> /*
>> */Knet solutions./*
>>
>> https://github.com/knetsolutions/KNet
>> http://knet-topology-builder.readthedocs.io/
>> http://knetsolutions.in/
>>
>>
--
*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
