[t.tsubo2...@gmail.com]
> Sent: Thursday, February 12, 2015 2:22 PM
> To: Alan Quillin
> Cc: ryu-devel@lists.sourceforge.net
> Subject: Re: [Ryu-devel] [PATCH] Modified BGP Update logic to use the path
> nexthop value first
>
> Hi, Alan
>
> It seems your patch doesn’t
]
Sent: Thursday, February 12, 2015 2:22 PM
To: Alan Quillin
Cc: ryu-devel@lists.sourceforge.net
Subject: Re: [Ryu-devel] [PATCH] Modified BGP Update logic to use the path
nexthop value first
Hi, Alan
It seems your patch doesn’t work properly in the following topology.
Because RyuBGP1 has sent BGP
Hi, Alan
It seems your patch doesn’t work properly in the following topology.
Because RyuBGP1 has sent BGP UPDATE(Nexthop: y.y.y.y) to R2.
iBGP eBGP
--- R1 ---> RyuBGP1 -> R2
x.x.x.x y.y.y.yz.z.z.z => UPDATE(Nexthop:
From: Alan Quillin
If the path has a next hop value set, it should be used in the BGP
Update message first. This changes to logic to use the check for the
next hop in the order prefix/path->peer config->speaker config. This
will allow for sending the nexthop as part of the add_prefix message an
