netdev - Re: [PATCH net-next v5] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO

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] [day] [month] [year] [list]

Message-Id: <20190329.132933.1730204026304335005.davem@davemloft.net>
Date:   Fri, 29 Mar 2019 13:29:33 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     wenxu@...oud.cn
Cc:     pshelar@....org, netdev@...r.kernel.org, dev@...nvswitch.org
Subject: Re: [PATCH net-next v5] openvswitch: Make metadata_dst tunnel work
 in IP_TUNNEL_INFO_BRIDGE mode

From: wenxu@...oud.cn
Date: Thu, 28 Mar 2019 12:43:23 +0800

> From: wenxu <wenxu@...oud.cn>
> 
> There is currently no support for the multicast/broadcast aspects
> of VXLAN in ovs. In the datapath flow the tun_dst must specific.
> But in the IP_TUNNEL_INFO_BRIDGE mode the tun_dst can not be specific.
> And the packet can forward through the fdb table of vxlan devcice. In
> this mode the broadcast/multicast packet can be sent through the
> following ways in ovs.
> 
> ovs-vsctl add-port br0 vxlan -- set in vxlan type=vxlan \
>         options:key=1000 options:remote_ip=flow
> ovs-ofctl add-flow br0 in_port=LOCAL,dl_dst=ff:ff:ff:ff:ff:ff, \
>         action=output:vxlan
> 
> bridge fdb append ff:ff:ff:ff:ff:ff dev vxlan_sys_4789 dst 172.168.0.1 \
>         src_vni 1000 vni 1000 self
> bridge fdb append ff:ff:ff:ff:ff:ff dev vxlan_sys_4789 dst 172.168.0.2 \
>         src_vni 1000 vni 1000 self
> 
> Signed-off-by: wenxu <wenxu@...oud.cn>

Applied to net-next, thanks.