On 2018-10-26 7:26 p.m., Fred Licht via discuss wrote:
I am not able to find a basic document or instruction on how to best configure
VLAN translation with OVS. I would be using the LTS OVS 2.5.5. Can someone
point me to some good examples or provide one.
It comes down to these two lines for
Hey,
I am not able to find a basic document or instruction on how to best
configure VLAN translation with OVS. I would be using the LTS OVS 2.5.5. Can
someone point me to some good examples or provide one.
A basic setup would be two OVS bridges with a Patch interface between them.
The
Lightning quick with your answers as always Ben!
I appreciate ya taking the time!
On Fri, Oct 26, 2018 at 4:55 PM Ben Pfaff wrote:
> On Fri, Oct 26, 2018 at 04:42:29PM -0600, Sterdnot Shaken wrote:
> > Why is it that vnic ports show as having a speed of 10 Mbps under the
> > command ovs-ofctl
On Sat, Oct 27, 2018 at 12:31:25AM +0200, Bo Yu wrote:
> How to easily add a flow to block port 1 to port 2 traffic assuming there
> are 5 ports ? Do I have to explicitly specify 'actions=3,4,5' ?
That's a typical way to do it.
> How to easily add a flow for a 'NOT EQUAL' logic ? I am very
On Fri, Oct 26, 2018 at 04:42:29PM -0600, Sterdnot Shaken wrote:
> Why is it that vnic ports show as having a speed of 10 Mbps under the
> command ovs-ofctl dump-ports-desc ?
>
> I've done many tests and the 10 Mbps value obviously has no implications on
> actual throughput for the OVS bridges. I
On 10/19/2018 1:39 AM, Jaime Caamaño Ruiz wrote:
Hello
When using nsh encapsulation, it's useful to normalize your pipeline to
packet_type=nsh, poping an ethernet header on input if necessary and
pushing an ethernet header again if required before output.
But it seems to be problematic:
---
Hi,
How to easily add a flow to block port 1 to port 2 traffic assuming
there are 5 ports ? Do I have to explicitly specify 'actions=3,4,5' ?
How to easily add a flow for a 'NOT EQUAL' logic ? I am very surprised
that 'inverse logic' is not supported in any openflow spec and ovs
extension.
On 10/26/2018 10:26 AM, Gregory Rose wrote:
On 10/17/2018 6:06 AM, Yousong Zhou wrote:
On Wed, 17 Oct 2018 at 21:01, Yousong Zhou
wrote:
...
ovs-vsctl add-port br0 tun0 -- set interface tun0 type=gre
options:remote_ip=flow options:key=flow options:packet_type=legacy_l2
ofport_request=2
On 10/17/2018 6:06 AM, Yousong Zhou wrote:
On Wed, 17 Oct 2018 at 21:01, Yousong Zhou wrote:
...
ovs-vsctl add-port br0 tun0 -- set interface tun0 type=gre
options:remote_ip=flow options:key=flow options:packet_type=legacy_l2
ofport_request=2
Pasted the wrong line. packet_type=legacy_l3
Hi,
I have a performance issue on vxlan tunnelling at dpdk built ovs platform.
Bridge and port structure and other system informations of both sides are
shown below.
Our scenario is iperf load test between VM's, which are connected to br-int
switches at both sides. Firstly I have route the
On 10/25/18 4:35 PM, Mehmet Yaren wrote:
>
> Hi Ian,
>
>
>
> We are using XL710 as below
>
>
>
> argela@dsfc-ovs:~$ lspci
>
> ...
>
> 08:00.0 Ethernet controller: Intel Corporation Ethernet Controller
> XL710 for 40GbE QSFP+ (rev 02)
>
> 08:00.1 Ethernet controller: Intel Corporation Ethernet
On 10/25/2018 12:05 PM, Mehmet Yaren wrote:
Hi Ian,
We are using XL710 as below
argela@dsfc-ovs:~$ lspci
...
08:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710
for 40GbE QSFP+ (rev 02)
08:00.1 Ethernet controller: Intel Corporation Ethernet Controller XL710
for
Hi all,
While analyzing a problem in OpenStack I think I have found out a
severe bug in OVN when it comes to reuse floating IPs (which is a very
common use case in OpenStack and Kubernetes). Let me explain the
scenario, issue and possible solutions:
* Three logical switches (Neutron networks)
13 matches
Mail list logo
