netdev - Re: [RFC v3 0/3] Add VRF support for VXLAN underlay

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fc2d195c-15f2-e60c-d35a-e3bca7978e8d@cumulusnetworks.com>
Date:   Tue, 20 Nov 2018 07:48:42 -0700
From:   David Ahern <dsa@...ulusnetworks.com>
To:     Alexis Bauvin <abauvin@...leway.com>, roopa@...ulusnetworks.com
Cc:     netdev@...r.kernel.org, akherbouche@...leway.com
Subject: Re: [RFC v3 0/3] Add VRF support for VXLAN underlay

On 11/20/18 7:23 AM, Alexis Bauvin wrote:
> We are trying to isolate the VXLAN traffic from different VMs with VRF as shown
> in the schemas below:
> 
> +-------------------------+   +----------------------------+
> | +----------+            |   |     +------------+         |
> | |          |            |   |     |            |         |
> | | tap-red  |            |   |     |  tap-blue  |         |
> | |          |            |   |     |            |         |
> | +----+-----+            |   |     +-----+------+         |
> |      |                  |   |           |                |
> |      |                  |   |           |                |
> | +----+---+              |   |      +----+----+           |
> | |        |              |   |      |         |           |
> | | br-red |              |   |      | br-blue |           |
> | |        |              |   |      |         |           |
> | +----+---+              |   |      +----+----+           |
> |      |                  |   |           |                |
> |      |                  |   |           |                |
> |      |                  |   |           |                |
> | +----+--------+         |   |     +--------------+       |
> | |             |         |   |     |              |       |
> | |  vxlan-red  |         |   |     |  vxlan-blue  |       |
> | |             |         |   |     |              |       |
> | +------+------+         |   |     +-------+------+       |
> |        |                |   |             |              |
> |        |           VRF  |   |             |          VRF |
> |        |           red  |   |             |         blue |
> +-------------------------+   +----------------------------+
>          |                                  |
>          |                                  |
>  +---------------------------------------------------------+
>  |       |                                  |              |
>  |       |                                  |              |
>  |       |         +--------------+         |              |
>  |       |         |              |         |              |
>  |       +---------+  eth0.2030   +---------+              |
>  |                 |  10.0.0.1/24 |                        |
>  |                 +-----+--------+                    VRF |
>  |                       |                            green|
>  +---------------------------------------------------------+
>                          |
>                          |
>                     +----+---+
>                     |        |
>                     |  eth0  |
>                     |        |
>                     +--------+
> 
> 
> iproute2 commands to reproduce the setup:

Thanks for putting the diagram and commands in the cover letter. Really
helps to understood (and test) what you are wanting to do.