On Thu, Sep 18, 2014 at 10:02:15AM +0530, Nirmalanand Jebakumar wrote:
> On Thu, Sep 18, 2014 at 2:30 AM, Ben Pfaff wrote:
>
> > As it turns out, when output goes through a tunnel, the pkt_mark comes
> > from the tunnel configuration. Currently, OVS forces it to 1 for IPSEC
> > tunnel traffic an
On Thu, Sep 18, 2014 at 2:30 AM, Ben Pfaff wrote:
> As it turns out, when output goes through a tunnel, the pkt_mark comes
> from the tunnel configuration. Currently, OVS forces it to 1 for IPSEC
> tunnel traffic and 0 for other tunnel traffic. This could be changed,
> and it probably should, b
As it turns out, when output goes through a tunnel, the pkt_mark comes
from the tunnel configuration. Currently, OVS forces it to 1 for IPSEC
tunnel traffic and 0 for other tunnel traffic. This could be changed,
and it probably should, because it is surprising, but this is the first
that I've not
OK, this may be a bug. I'll try to investigate soon.
On Wed, Sep 17, 2014 at 11:53:16PM +0530, Nirmalanand Jebakumar wrote:
> Hi Ben,
>
> The ovs-dpctl command output does not show any skb_mark being set for the
> datapath flow:
>
> # ovs-dpctl dump-flows
> skb_priority(0),in_port(4),eth(src=52
Hi Ben,
The ovs-dpctl command output does not show any skb_mark being set for the
datapath flow:
# ovs-dpctl dump-flows
skb_priority(0),in_port(4),eth(src=52:54:00:74:f9:41,dst=52:54:00:aa:93:9e),eth_type(0x0800),ipv4(src=
2.2.2.3/255.255.255.255,dst=2.2.2.2/255.255.255.255,proto=1/0xff,tos=0/0x3
On Wed, Sep 17, 2014 at 05:12:20PM +0530, Nirmalanand Jebakumar wrote:
> In this link below, I read that pkt_mark is supported as a MATCH field.
> Does OVS support pkt_mark as a SET action?
Yes.
> The command I ran is
> /usr/bin/ovs-ofctl add-flow -O Openflow13 br0 "
> hard_timeout=3600,idle_tim
