Can you test or examine the recent patches to see if they avoid the
problem you mention? It probably won't be obvious as a problem during
review.
On Tue, Apr 25, 2017 at 01:46:41AM +, Hexin Wang wrote:
> Thanks. Good to know that this is being merged back to OVS mainline.
>
> The old way of
If I were to qualify the NAT action based on some route lookup instead of
outport, is there any bit/register available for me to carry the nat decision
down in the pipeline?
Thanks.
Hexin
From:
>
on behalf of
Thanks. Good to know that this is being merged back to OVS mainline.
The old way of Layer3 GRE implementation via “base_layer” seems to have an
issue with ct_state_nat feature.
Specifically if pop_mpls happens before ct(nat,), pop_mpls recirculation would
cause both flow->base_layer and
the valgrind's report as follows:
2017-04-25T01:38:16Z|00025|coverage|INFO|bridge_reconfigure 0.0/sec
0.000/sec0./sec total: 1
2017-04-25T01:38:16Z|00026|coverage|INFO|ofproto_flush 0.0/sec
0.000/sec0./sec total: 1
The userspace L3 patch set Zoltan posted has included L3 support for GRE, here
it is.
https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330490.html
-Original Message-
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Hexin Wang
Hi Guru,
Thanks. You probably referred to the unit test "ovn -- DNAT and SNAT on
distributed router - E/W" in tests/system-ovn.at? Is there anyway for me to
configure route based dnat_and_snat from ovn-nbctl? Specifically can I qualify
the following command with some prefix routes?
On 24 April 2017 at 11:39, Hexin Wang wrote:
> Hi Guru,
>
> Let me try with the following use cases.
> 1. No floating IP is used for east-west routing traffic.
> E.g. VM1 <-> VM2: Private IPs are used. No NAT applied.
>
> 2. Floating IP is used for south-north default
Oh, I see.
Lori or Simon, are you planning to send patches for master?
On Mon, Apr 24, 2017 at 06:42:07PM +, Hexin Wang wrote:
> Right. I was specifically referring to the OVS layer3 tunnel support
> originated by Lorand Jakab and Simon Horman.
> The changes made in kernel data path is
Right. I was specifically referring to the OVS layer3 tunnel support originated
by Lorand Jakab and Simon Horman.
The changes made in kernel data path is merged back to Linux mainline by Jiri
Benc. But the user space OVS changes are missing in ovs main tree.
Thanks.
Hexin
On 4/24/17, 11:37
Hi Guru,
Let me try with the following use cases.
1. No floating IP is used for east-west routing traffic.
E.g. VM1 <-> VM2: Private IPs are used. No NAT applied.
2. Floating IP is used for south-north default route to internet traffic.
E.g. VM originated internet traffic: SNAT is applied to
On Mon, Apr 24, 2017 at 06:25:07PM +, Hexin Wang wrote:
> I got a question on OVS layer3 GRE tunnel support. The OVS kernel
> piece that supports layer 3 GRE is merged into linux upstream since
> 4.10 RC6. Do we need any extra user land OVS merge for it to work
> end-to-end? I am referring to
On 24 April 2017 at 11:31, Hexin Wang wrote:
> Hi,
>
> Is there any knob in OVN to control when floating IP will be applied in
> the distributed NAT? Specifically:
>
>1. If the destination IP is part of some private layer3 domain, the
>usual private IP is used to
Hi,
Is there any knob in OVN to control when floating IP will be applied in the
distributed NAT? Specifically:
1. If the destination IP is part of some private layer3 domain, the usual
private IP is used to to reach the destination in the private layer3 domain.
2. If the destination IP
Hi Ben,
I got a question on OVS layer3 GRE tunnel support. The OVS kernel piece that
supports layer 3 GRE is merged into linux upstream since 4.10 RC6. Do we need
any extra user land OVS merge for it to work end-to-end? I am referring to the
“options:layer3=true” ovs-vsctl interface changes.
OK, let's figure out the problem. Can you provide a backtrace? Or run
OVS until valgrind and provide valgrind's report? Or can you provide
reproduction information for us?
Thanks,
Ben.
On Thu, Apr 20, 2017 at 08:21:54AM +, qintao (F) wrote:
> hi,Pettit
> I have reprodeuced the same
On Mon, Apr 24, 2017 at 04:30:51PM +, Hexin Wang wrote:
> In ovs 2.6.90, we are seeing NULL reference to in_port if
> lookup_input_bundle() sets in_port to NULL.
>
> /* Learn source MAC. */
> if (ctx->xin->may_learn && !in_port->is_layer3) {
>
Hi,
In ovs 2.6.90, we are seeing NULL reference to in_port if lookup_input_bundle()
sets in_port to NULL.
/* Learn source MAC. */
if (ctx->xin->may_learn && !in_port->is_layer3) {
update_learning_table(ctx->xbridge, flow, wc, vlan, in_xbundle);
}
This happens when a flow
No, select buckets don't use mod-n to select a bucket. Instead, for
each live bucket, OVS hashes flow data with the bucket ID and multiplies
by the bucket weight to obtain a "score", and then selects the bucket
with the highest score.
On Mon, Apr 24, 2017 at 12:27:16AM +0530, Ahmed Khan wrote:
>
Hi : )
I'm facing an weird behavior regarding on role change.
When I send a role message to change the role of one specific switch,
all switches change to this role.
I think the problem is when open vSwitch mount the transaction message
to send to ovsdb.
A simple test is, start a mininet
If that's useful, then it makes sense to me and I'd have no objection.
On Mon, Apr 24, 2017 at 10:06:17AM +, O Mahony, Billy wrote:
> Hi Ben, Darrell,
>
> I've done some PoC work on this kind of traffic prioritization. However with
> OVS-DPDK's run-to-completion model the issue I find the
Hi Ben, Darrell,
I've done some PoC work on this kind of traffic prioritization. However with
OVS-DPDK's run-to-completion model the issue I find the same issue as you
outlined - by the time the priority of the packet has been determined most of
the effort to process the packet has already
Hello
I have some question about ovs' flow table implementation after visiting
this url
https://software.intel.com/en-us/articles/ovs-dpdk-datapath-classifier-part-2
Are there some difference in flow table implementation between original ovs
and dpdk ovs?
Also, are there any differences in
Regards
_Sugesh
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Vishal Deep Ajmera
Sent: Monday, April 24, 2017 8:01 AM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] ovs-dpdk bond mode
Are we using DPDK Bond-PMD library for OVS
23 matches
Mail list logo