I think you might need to specify that it's IP traffic. Try adding "ip" to
your flow definition.
--Justin
> On Sep 8, 2016, at 7:38 PM, Warsang wrote:
>
> Hello, I am trying to add a rule in ryu to drop packets where TTL=0.
> However in ovs when I use sudo ovs-ofctl -O OpenFlow14 add-flow 0_
Hello, I am trying to add a rule in ryu to drop packets where TTL=0.
However in ovs when I use sudo ovs-ofctl -O OpenFlow14 add-flow 0_0_1
"nw_ttl=0 actions=DROP"
And then do: mininet@mininet-vm:~$ sudo ovs-ofctl dump-flows 0_0_1
I get NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=495.989s,
Hi,
Please don't drop the list, it could be interesting to more people.
On 09/08/2016 06:55 PM, Junguk Cho wrote:
Hi, Mauricio.
Thank you for reply.
I have following questions.
Are you using physical ports?
If yes, are they physically connected to socket1?
Currently, I did not add physical p
There wasn't a direct followup but the problem was effectively
addressed by the lightweight tunnel changes and I don't believe that
it can happen at this point. Those changes were introduced in OVS 2.5.
I think it's unlikely that we will do another release off of the 2.3.x
series at this point so
Hi Junguk,
On 09/08/2016 05:07 PM, Junguk Cho wrote:
Hi, I used OVS with dpdk.
When I started ovs, I used this option to pin some cores for ovs.
sudo ovs-vsctl --no-wait set Open_vSwitch .
other_config:pmd-cpu-mask=0xf000
In my setup, it has two sockets, but with this option, two cores in
Hi, I used OVS with dpdk.
When I started ovs, I used this option to pin some cores for ovs.
sudo ovs-vsctl --no-wait set Open_vSwitch .
other_config:pmd-cpu-mask=0xf000
In my setup, it has two sockets, but with this option, two cores in first
socket shows 100% cpu utilization. In addition, wh
On Thu, Sep 08, 2016 at 01:21:46PM +0200, Ashish Kurian wrote:
> Dear Team,
>
> I have installed the ovs through debian packages by following
> install.debian.md and the install was successful.
>
> Then I applied the ovs gtp u patch manually using the patch command. Now I
> need to build new debi
The thing is, that at least in my installation(the default on ubuntu
16.04), it does not learn the new location. It just drops any package when
it comes in on a port where it's not expected. I have to wait until the old
cached mac disappears (seems to be something like 300 seconds), as shown
when r
Hello,
was this issue ever followed up ?
I see no corresponding changes in the kernel nor anywhere else,
but I appear to have hit the same kernel crash.
I see it on RHEL7.2 with openvswitch-2.3.2.
Cheers,
Dirk
Hi jesse,
I will submit this patch to upstream then backport it to OVS
At 20
Dear Team,
I have installed the ovs through debian packages by following
install.debian.md and the install was successful.
Then I applied the ovs gtp u patch manually using the patch command. Now I
need to build new debian files using the updated source files.
So I went into the directory of ope
10 matches
Mail list logo
