What we're doing with CARDIGAN is pairing an instance of Quagga (sitting in
a VM/Linux Container) with multiple OpenFlow-capable switches. This allows
us to leverage Quagga's protocol support for things like BGP.
RouteFlow specifically is the software glue between the VM(s) and the
switch(es). It listens to route updates from the kernel, and turns these
into OpenFlow rules to send to the switches. It can map VMs to switches in
1:1 or 1:N configurations.
On 22 April 2014 05:48, Andrew Niteesh <andrewece87(a)gmail.com> wrote:
I have few clarifications, the table you shown have matric, local
preference, path and next hop.
1. So how you are setting up these attributes in SDN?
(Or) you have an application developed for BGP?
(Or) you are running SDN on top of traditional networks?
2. What is Route flow – according to my understanding it’s like
getting connecting a set of open flow capable switches to single controller.
Please correct me if am wrong.
Thanks & Regards,
University of Houston
NZNOG mailing list