On Mon, Aug 29, 2016 at 07:22:10PM +1200, Warsang wrote:
> Hello,
>
> I was wondering how the bucket selection is made in OVS 2.4 I found this in
> the ml archive
> http://openvswitch.org/pipermail/discuss/2016-January/019984.html
> saying that :"
>
> Open vSwitch 2.4 and later by default hashes
Hello,
I was wondering how the bucket selection is made in OVS 2.4 I found this
in the ml archive
http://openvswitch.org/pipermail/discuss/2016-January/019984.html
saying that :"
Open vSwitch 2.4 and later by default hashes the source and
destination Ethernet address, VLAN ID, Ethernet typ
Hi Neil,
Seems that's a possible fix because in most case, there might not be mixed
tunnel types, set tunnel type to unknown will not affect analysis much.
However, seems this patch is also present on master branch, I am wondering
the stability and test coverity of sFlow feature of OVS.
Since we
Please don't drop the mailing list.
A number of extensions exist in "include/openflow/nicira-ext.h". If you run
"git blame" on that file, you'll see a bunch of commit ids. You can then run
"git show" on the commit id, and see how the extension was added. For example,
"git show fb8f22c1" will
On Sat, Aug 27, 2016 at 08:00:15PM +0200, Richard Mayers wrote:
> I am trying to modify the ip_proto field using an SET_FIELD action.
> However, it seems that OVS does not allow that, and ip_porto is
> only-read field. error message:
>
> destination field nw_proto is not writable
>
> Why is this
On Fri, Aug 26, 2016 at 09:40:04PM +0530, Lohit Prasad wrote:
> I am having good interest in open switch so tested it and found multiole
> issues. How to report ?
If you really have OpenSwitch issues, then you should find an OpenSwitch
forum or bug tracker.
If you have Open vSwitch issues, though
