On Wed, May 08, 2019 at 02:54:58PM -0600, Carl Baldwin wrote:
> Thanks for your quick response. Your assessment makes sense to me. For
> IPv4, I don't think 0 would be a valid protocol number but for IPv6 it
> would mean that the hop-by-hop options are present.
For IPv6, OVS does not literally
Ben,
Thanks for your quick response. Your assessment makes sense to me. For
IPv4, I don't think 0 would be a valid protocol number but for IPv6 it
would mean that the hop-by-hop options are present.
What do you think about the extra no-op actions in the datapath
actions when I set the protocol
I investigated this a little bit by putting the following in a file
named 'flows':
table=0 ip,in_port=4,dl_dst=a6:c1:a7:15:a4:3d,nw_dst=10.39.176.4,priority=3100,
actions=resubmit(,25)
table=25, ip,vlan_tci=0x1000/0x1000,nw_dst=10.39.176.4, priority=3100,
Greetings,
I have been using ofproto/trace to verify the actions taken on various
packets through an OVS bridge. My methodology is basically to specify
the action in br_flow format to ovs-appctl ofproto/trace and then
comparing the datapath actions line with expected actions. I ran into
an
