That seems odd. It's supposed to set PATH when it's being run from a build
directory. (I can even see it using the "-b" option in the output you've
provided.) I run it from my build directory and don't have any problem.
I'm glad you got it working at least in some way, though.
--Justin
> On
Hi Justin,
This what I did.
1) Created a new VM
2) Tried to install the sandbox, but ran into the same isuse. PATH wasn't
getting updated.
3) Installed openvswitch (sudo apt-get install openvswitch-switch)
4) Installed sandbox again.
5) PATH was correctly updated. Commands started working.
So t
What was the issue?
--Justin
> On Apr 29, 2016, at 4:14 PM, Maurice Qureshi
> wrote:
>
> Hi Darrell/Justin,
>
> I got it to work for now. Thanks for your help.
>
> Maurice
>
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Maurice
> Quresh
Hi Darrell/Justin,
I got it to work for now. Thanks for your help.
Maurice
-Original Message-
From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Maurice
Qureshi
Sent: Friday, April 29, 2016 12:43 PM
To: Darrell Ball ; Justin Pettit
Cc: discuss@openvswitch.org
Subject:
On 28 April 2016 at 15:06, Justin Pettit wrote:
>
>> On Apr 28, 2016, at 3:21 PM, Joe Stringer wrote:
>>
>> On 26 April 2016 at 23:35, Prathap T wrote:
>>> Hi OvS-Team:
>>>
>>> Does ovs-2.5 support NAT functionality? From the release notes I only see
>>> description related to CT.
>>> If NAT
This will show you the commits on the 2.3.x release series:
https://github.com/openvswitch/ovs/commits/branch-2.3
On Fri, Apr 29, 2016 at 1:20 PM, Michael Ben-Ami
wrote:
> Thank you, is there any where we can see what commits are part of which
> release?
>
> On Fri, Apr 29, 2016 at 4:02 PM, Jesse
Thank you, is there any where we can see what commits are part of which
release?
On Fri, Apr 29, 2016 at 4:02 PM, Jesse Gross wrote:
> On Fri, Apr 29, 2016 at 12:11 PM, Michael Ben-Ami
> wrote:
> >
> > OVS version:
> >
> > ovs-ofctl (Open vSwitch) 2.3.2
> > Compiled Aug 24 2015 18:39:15
> > Ope
This is not going to be possible in 2.3. It's a feature for an
upcoming release (presumably the next one).
On Fri, Apr 29, 2016 at 10:57 AM, Michael Ben-Ami
wrote:
> I could use help with the OVS requirements, Linux kernel requirements, any
> any flow examples to implement what is described in sl
On Fri, Apr 29, 2016 at 12:11 PM, Michael Ben-Ami
wrote:
>
> OVS version:
>
> ovs-ofctl (Open vSwitch) 2.3.2
> Compiled Aug 24 2015 18:39:15
> OpenFlow versions 0x1:0x4
>
> Linux version:
>
> Linux version 3.13.0-52-generic (buildd@comet) (gcc version 4.8.2 (Ubuntu
> 4.8.2-19ubuntu1) ) #86-Ubuntu
Hi Darrell,
I checked and it looks similar to your
+
PATH=/home/mqureshi/ovs/ovn/controller:/home/mqureshi/ovs/ovn/controller-vtep:/home/mqureshi/ovs/ovn/northd:/home/mqureshi/ovs/ovn/utilities:/home/mqureshi/ovs/ovsdb:/home/mqureshi/ovs/vswitchd:/home/mqureshi/ovs/utilities:/home/mqureshi/ovs/
I could use help with the OVS requirements, Linux kernel requirements, any
any flow examples to implement what is described in slide 11, here:
http://www.slideshare.net/ThomasGraf5/linuxcon-2015-stateful-nat-with-ovs?next_slideshow=2
On Fri, Apr 29, 2016 at 1:45 PM, Michael Ben-Ami
wrote:
> Can
Can anyone point me to a configuration example for Stateful destination NAT
assuming we are using OVS version 2.3.2? What I am mainly interested in is
IP fragment reassembly so that UDP checksums are correct after the NAT.
___
discuss mailing list
discuss
Hi Volkan
replies inline.
Regards,
Antonio
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of
> Ali Volkan Atli
> Sent: Friday, April 29, 2016 2:16 PM
> To: discuss@openvswitch.org
> Subject: [ovs-discuss] DPDK-OvS Cache Architecture
>
> Hi
>
> I
Applying this to the master branch improves the situation quite a bit.
From 39 down to 7:
ERROR: 1753 tests were run,
7 failed unexpectedly.
286 tests were skipped.
## -- ##
## testsuite.log was created. ##
## -- ##
Please send `tests/testsuite.lo
Hi
I am trying to understand DPDK cache architecture for pmd threads. There are
three hash tables (flow_cache, cls and flow_table) in the dp_netdev_pmd_thread
structure. First, dp_netdev_input() calls emc_processing() and it tries to
match the packet in flow_cache for the related pmd thread. If
I suppose the most elegant fix is to turn
union flow_in_port {
odp_port_t odp_port;
ofp_port_t ofp_port;
};
in lib/packet.h into:
union flow_in_port {
odp_port_t odp_port;
#ifdef WORDS_BIGENDIAN
struct __attribute__((__packed__)) {
ofp_port_t padding;
ofp_port_t
Regards
_Sugesh
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Vivek
> Gupta
> Sent: Friday, April 29, 2016 1:09 PM
> To: discuss@openvswitch.org
> Subject: Re: [ovs-discuss] Unable to add bridge ovsbr0 port vnet0: Operation
> not supported
>
Thanks Sugesh. As suggested, I am making Host-VM communication using
vhost-user port.
Please correct my understanding for vhost-user port which is as below-
After VM creation, I will pass vhost-user socket to VM machine in QEMU but not
able to understand how this socket will get connected to V
Regards
_Sugesh
> -Original Message-
> From: Vivek Gupta [mailto:vive...@hcl.com]
> Sent: Friday, April 29, 2016 7:09 AM
> To: Chandran, Sugesh ;
> discuss@openvswitch.org
> Subject: RE: [ovs-discuss] Unable to add bridge ovsbr0 port vnet0: Operation
> not supported
>
> Hi
>
> thanks f
19 matches
Mail list logo
