Hello together, I would like to follow up on this.
Meanwhile I was able to find the following discussion [1] in this mailing list some time ago which looks like is about the same topic. Is this something that's currently not possible within OVS? If so, are there plans to add this? I had a look at how OVN is doing it, and it seems like OVN is sending this type of traffic to their controller for external processing. Would be nice if we could answer NDP NS packets with OVS flows directly like we already can for ARP requests. [1] https://www.mail-archive.com/ovs-dev@openvswitch.org/msg46880.html [2] https://github.com/openvswitch/ovs/blob/8045c0f8de5192355ca438ed7eef77457c3c1625/ofproto/ofproto-dpif.c#L4695 Thanks in advance for your time! Best regards Maximilian ________________________________ From: discuss <ovs-discuss-boun...@openvswitch.org> on behalf of Sesterhenn, Maximilian via discuss <ovs-disc...@openvswitch.org> Sent: Monday, May 22, 2023 22:16 To: ovs-disc...@openvswitch.org <ovs-disc...@openvswitch.org> Subject: [ovs-discuss] OVS NDP proxy / nd_options_type ovs-disc...@openvswitch.org appears similar to someone who previously sent you email, but may not be that person. Learn why this could be a risk<https://aka.ms/LearnAboutSenderIdentification> OUTSIDE-EPG! Hey there, maybe someone from this list can help me. I'm currently trying to implement a simple NDP proxy using OVS. For that, I defined two basic flows that should do the trick: cookie=0x3e6,priority=1100,icmp6,icmp_type=135,icmp_code=0,in_port=patch-provnet-f,dl_src=MAC actions=set_field:136->icmpv6_type,set_field:0->icmpv6_code,goto_table:10 cookie=0x3e6,priority=1000,table=10,icmp6,icmp_type=136,icmp_code=0,in_port=patch-provnet-f,dl_src=MAC actions=move:NXM_OF_ETH_SRC[]->NXM_OF_ETH_DST[], mod_dl_src:MAC,move:NXM_NX_IPV6_SRC[]->NXM_NX_IPV6_DST[],move:NXM_NX_ND_TARGET[]->NXM_NX_IPV6_SRC[],set_field:MAC->nd_tll,set_field:2->nd_options_type,in_port However, I'm unable to install the second flow, it works without the nd_options_type field. It errors out with the message "OFPT_ERROR (xid=0xa): OFPBAC_BAD_SET_ARGUMENT". The problem is that without that field my NA messages are incorrect. I digged further and realized that this is something that older version of the OVS do not support. I think I found the feature on the release notes of OVS 2.12.0 [1]. However, I'm on a quite recent system so that should not be a problem. Is someone with more experience able to tell me what the reason could be? Versioning: Rocky Linux 9.1 Linux 5.14.0-162.23.1.el9_1.x86_64 # ovs-ofctl --version ovs-ofctl (Open vSwitch) 3.1.2 OpenFlow versions 0x1:0x6 # ovs-vsctl --version ovs-vsctl (Open vSwitch) 3.1.2 DB Schema 8.3.1 # modinfo openvswitch filename: /lib/modules/5.14.0-162.23.1.el9_1.x86_64/kernel/net/openvswitch/openvswitch.ko.xz alias: net-pf-16-proto-16-family-ovs_ct_limit alias: net-pf-16-proto-16-family-ovs_meter alias: net-pf-16-proto-16-family-ovs_packet alias: net-pf-16-proto-16-family-ovs_flow alias: net-pf-16-proto-16-family-ovs_vport alias: net-pf-16-proto-16-family-ovs_datapath license: GPL description: Open vSwitch switching datapath rhelversion: 9.1 srcversion: C1E5F3D9CD0C9A09006C69E depends: nf_conntrack,nf_nat,nf_conncount,libcrc32c,nf_defrag_ipv6 retpoline: Y intree: Y name: openvswitch vermagic: 5.14.0-162.23.1.el9_1.x86_64 SMP preempt mod_unload modversions [1] https://mail.openvswitch.org/pipermail/ovs-announce/2019-September/000255.html Best regards Maximilian _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
