Le 21 nov. 2018 à 20:26, David Ahern a écrit :
>
> On 11/21/18 6:30 AM, Alexis Bauvin wrote:
>> Le 20 nov. 2018 à 22:45, David Ahern a écrit :
>>>
>>> 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
On 11/21/18 6:30 AM, Alexis Bauvin wrote:
> Le 20 nov. 2018 à 22:45, David Ahern a écrit :
>>
>> 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:
>>>
>>> +-+
Le 20 nov. 2018 à 22:45, David Ahern a écrit :
>
> 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:
>>
>> +-+ ++
>> | +--+
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:
>
> +-+ ++
> | +--+| | ++ |
> | | |
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:
>
> +-+ ++
> | +--+| | ++ |
> | | |
v2 -> v3:
- fix build when CONFIG_NET_IPV6 is off
- fix build "unused l3mdev_master_upper_ifindex_by_index" build error with some
configs
v1 -> v2:
- move vxlan_get_l3mdev from vxlan driver to l3mdev driver as
l3mdev_master_upper_ifindex_by_index
- vxlan: rename variables named l3mdev_ifindex
