On Thu, Aug 29, 2019 at 8:40 AM Yifeng Sun wrote:
> Thanks Ben and Darrell, let me check it out.
>
Can you also add a use case description ?
>From a controller POV, defining which interface is a vtep can be done in
one place and
distributed to the rest of the system; it is not much code. There
Thanks Ben and Darrell, let me check it out.
On Wed, Aug 28, 2019 at 12:46 PM Darrell Ball wrote:
>
> Thanks for the patch
>
> How about writing a system test ?
>
> Darrell
>
> On Wed, Aug 28, 2019 at 10:50 AM Yifeng Sun wrote:
>>
>> For userspace datapath, currently only the bridge itself, the
Thanks for the patch
How about writing a system test ?
Darrell
On Wed, Aug 28, 2019 at 10:50 AM Yifeng Sun wrote:
> For userspace datapath, currently only the bridge itself, the LOCAL port,
> can be the tunnel endpoint to encap/decap tunnel packets. This patch
> enables non-bridge port as tun
On Wed, Aug 28, 2019 at 10:49:59AM -0700, Yifeng Sun wrote:
> For userspace datapath, currently only the bridge itself, the LOCAL port,
> can be the tunnel endpoint to encap/decap tunnel packets. This patch
> enables non-bridge port as tunnel endpoint. One use case is for users to
> create a brid
For userspace datapath, currently only the bridge itself, the LOCAL port,
can be the tunnel endpoint to encap/decap tunnel packets. This patch
enables non-bridge port as tunnel endpoint. One use case is for users to
create a bridge and a vtep port as tap, and configure underlay IP at vtep
port as
