> On Sat, Sep 01, 2018 at 07:28:29PM +0200, nm_r wrote:
>> I was wondering why the log shows two actions
>>
>> "actions:set(ipv6(label=0,hlimit=63))"
>>
>> as there is only one defined in the flow "dec_ttl"? The flow label
>> is only matched if its 0 so why set it to 0 again in the action?
>
>
> I agree that it sets more than it needs to, but that wouldn't be the
> source of the actual problem as far as I can tell.
It seems that IPv6 flow label support in OVS has some other problems too.
Assume that in one flow table the IPv6 flow label of a packet is set and its
then
resubmitted to another table. In the second table some other matches on IPv6
flow label exists.
The simplified flows:
Table 0
ipv6,in_port=LOCAL actions=load:0x1234->NXM_NX_IPV6_LABEL[],resubmit(,1)
Table 1
ipv6,ipv6_label=0x01234 actions=output:"ovs_p1"
This produces the following erros in openvswitch and system log file:
2018-09-06T11:11:22.436Z|00029|dpif(handler15)|WARN|system@ovs-system
failed to put[create] (Invalid argument)
ufid:47f16081-1bc0-48ee-bcbd-dfce4539808c
recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(1),skb_mark(0/0),
ct_state(0x21/0),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),
eth(
src=7e:e2:bf:60:a4:45,
dst=00:01:bb:04:01:01),
eth_type(0x86dd),
ipv6(
src=2001:db8:1000::100/::,
dst=2001:db8:1000::1/::,
label=0,
proto=58/0,tclass=0/0,hlimit=64/0,frag=no),
icmpv6(type=128/0,code=0/0),
actions:set(ipv6(label=0x1234)),2
2018-09-06T11:11:22.436Z|00030|dpif(handler15)|WARN|system@ovs-system:
execute set(ipv6(label=0x1234)),2 failed
(Invalid argument) on packet
icmp6,vlan_tci=0x0000,
dl_src=7e:e2:bf:60:a4:45,dl_dst=00:01:bb:04:01:01,
ipv6_src=2001:db8:1000::100,ipv6_dst=2001:db8:1000::1,
ipv6_label=0x00000,
nw_tos=0,nw_ecn=0,nw_ttl=64,
icmp_type=128,icmp_code=0 icmp6_csum:8367
with metadata skb_priority(0),skb_mark(0),ct_state(0x21),in_port(1) mtu 0
In the system logfile the following error is logged:
[78961.012834] openvswitch: netlink: Flow actions may not be safe on all
matching packets.
Could someone please explain if such types of flows are generally not possible
with OVS or if this
behavior is a bug.
Regards
Richard
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
