[ovs-discuss] [HELP] Question about capture pkts sent to OVN

2019-05-13 Thread txfh2007 via discuss
Hi all: I am using OVN as controller to set/modify flow entries of OVS in openstack Pike environment. I have found sometimes pkts should sent to OVN as the following openflow entry: cookie=0x569f90ea, duration=402799.438s, table=22, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534,

[ovs-discuss] can OVS DPDK userspace support full features of conntrack and NAT in kernel data path?

2019-05-13 Thread 杨�D
Hi, guys I’m evaluating if OVS DPDK can play a NAT gateway role very well, anybody can tell me if OVS DPDK userspace can support full features of conntrack and NAT in kernel data path? Which version is ok for this? smime.p7s Description: S/MIME cryptographic signature

Re: [ovs-discuss] can OVS DPDK userspace support full features of conntrack and NAT in kernel data path?

2019-05-13 Thread solomon
Yi Yang (杨燚)-云服务集团 wrote: > Hi, guys > > > > I’m evaluating if OVS DPDK can play a NAT gateway role very well, anybody > can tell me if OVS DPDK userspace can support full features of conntrack and > NAT in kernel data path? Which version is ok for this? We have used ovs(2.10)+dpdk as a gatewa

[ovs-discuss] 答复: can OVS DPDK userspace support full features of conntrack and NAT in kernel data path?

2019-05-13 Thread 杨�D
Thank for your reply, how about performance compared to Linux kernel? -邮件原件- 发件人: solomon [mailto:shanwe...@gmail.com] 发送时间: 2019年5月14日 10:18 收件人: Yi Yang (杨�D)-云服务集团 ; disc...@openvswitch.org 主题: Re: [ovs-discuss] can OVS DPDK userspace support full features of conntrack and NAT in kerne

[ovs-discuss] Only allow traffic between the bridge port and OVS (not other ports)

2019-05-13 Thread Kevin Olbrich
Hi! I've got an OVS that has a bridge "br0" and has about 100x L2TP tunnels. These tunnels run batman-adv, a mesh protocol for L2 routing over L3. For efficient routing, only nodes that are in the same building are allowed to see each other. To filter out traffic between the ports, I used ebtable

Re: [ovs-discuss] Only allow traffic between the bridge port and OVS (not other ports)

2019-05-13 Thread Kevin Olbrich
Am Di., 14. Mai 2019 um 07:26 Uhr schrieb Kevin Olbrich : > Hi! > > I've got an OVS that has a bridge "br0" and has about 100x L2TP tunnels. > These tunnels run batman-adv, a mesh protocol for L2 routing over L3. > > For efficient routing, only nodes that are in the same building are > allowed to

Re: [ovs-discuss] Only allow traffic between the bridge port and OVS (not other ports)

2019-05-13 Thread Matthias May via discuss
On 14/05/2019 07:26, Kevin Olbrich wrote: > Hi! > > I've got an OVS that has a bridge "br0" and has about 100x L2TP tunnels. > These tunnels run batman-adv, a mesh protocol for L2 routing over L3. > > For efficient routing, only nodes that are in the same building are allowed > to see each other.

Re: [ovs-discuss] Only allow traffic between the bridge port and OVS (not other ports)

2019-05-13 Thread Kevin Olbrich
Hi Matthias, do I need to create an "int" port for this? Currently I bind an IP directly to br0. Thank you! Kind regards Kevin Am Di., 14. Mai 2019 um 08:00 Uhr schrieb Matthias May via discuss < ovs-discuss@openvswitch.org>: > On 14/05/2019 07:26, Kevin Olbrich wrote: > > Hi! > > > > I've go

Re: [ovs-discuss] Only allow traffic between the bridge port and OVS (not other ports)

2019-05-13 Thread Kevin Olbrich
Ok, there already is "br0" as int interface, didn't read correctly. Your command is missing some pieces, can you check again? Kind regards Kevin Am Di., 14. Mai 2019 um 08:32 Uhr schrieb Kevin Olbrich : > Hi Matthias, > > do I need to create an "int" port for this? > Currently I bind an IP dire