Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
>> Zak had completed most of the work to set the RSO flags, so I'm sure he'd be >> happy >> to send it out if you want to take the patches in yourself. However, I >> don't think it >> makes sense to include that functionality more generally in OVS. Hi Justin, Can you please share the patch for this feature ? We would like to work on it as our product requires this feature to be supported in OVS. Do you have any alternatives apart from controller based mechanism ? Regards, Vishal ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
>>I believe you should already be able to set the SLL and TLL options. Does >>that not work for you? >> In order to set up IPv6 NA responder we will be required to modify incoming >> solicitations with SLL >> option (multicast solicitations) to an Advertisement with TLL option. My >> understanding is that current >> support is only to modify existing TLL >> option, if already present in the packet. Hi Justin, Can we get a preliminary patch for this feature, in case it is ready ? Warm Regards, Vishal ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
>> Zak is working on that feature; I expect patches will hit the mailing list >> in the next week or two. >> >> Hi Justin, >> >> As part of this feature, will it also enable us to rewrite the options >> tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to >> rewrite these fields in Options TLV. This will help in supporting multicast >> solicitations. >>I believe you should already be able to set the SLL and TLL options. Does >>that not work for you? In order to set up IPv6 NA responder we will be required to modify incoming solicitations with SLL option (multicast solicitations) to an Advertisement with TLL option. My understanding is that current support is only to modify existing TLL option, if already present in the packet. Regards, Vishal ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
> On May 2, 2018, at 2:50 AM, Vishal Deep Ajmera >wrote: > >> Zak is working on that feature; I expect patches will hit the mailing list >> in the next week or two. >> >> Hi Justin, >> >> As part of this feature, will it also enable us to rewrite the options >> tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to >> rewrite these fields in Options TLV. This will help in supporting multicast >> solicitations. I believe you should already be able to set the SLL and TLL options. Does that not work for you? > In case you have an RFC patch ready for this feature, can you please post it > ? We can help in reviewing and testing it. Zak said he should be posting it this week. We always appreciate help reviewing and testing code. --Justin ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
> Zak is working on that feature; I expect patches will hit the mailing list in > the next week or two. > > Hi Justin, > > As part of this feature, will it also enable us to rewrite the options > tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to > rewrite these fields in Options TLV. This will help in supporting multicast > solicitations. Hi Justin, In case you have an RFC patch ready for this feature, can you please post it ? We can help in reviewing and testing it. Warm Regards, Vishal Ajmera ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
> Zak is working on that feature; I expect patches will hit the mailing list in > the next week or two. Hi Justin, As part of this feature, will it also enable us to rewrite the options tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to rewrite these fields in Options TLV. This will help in supporting multicast solicitations. Warm Regards, Vishal ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
> On Apr 8, 2018, at 9:55 AM, Ben Pfaffwrote: > > On Sun, Apr 08, 2018 at 04:34:16PM +, Vishal Deep Ajmera wrote: >> >> In the above message, fields R (Router flag), S (Solicited flag) and O >> (Override flag) cannot be set. Is my understanding correct ? > > Yes. > > It would be reasonable to be able to match and set these, so I imagine > that we would accept patches to enable that. > Zak is working on that feature; I expect patches will hit the mailing list in > the next week or two. Thank you Ben and Justin. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
> On Apr 8, 2018, at 9:55 AM, Ben Pfaffwrote: > > On Sun, Apr 08, 2018 at 04:34:16PM +, Vishal Deep Ajmera wrote: >> >> In the above message, fields R (Router flag), S (Solicited flag) and O >> (Override flag) cannot be set. Is my understanding correct ? > > Yes. > > It would be reasonable to be able to match and set these, so I imagine > that we would accept patches to enable that. Zak is working on that feature; I expect patches will hit the mailing list in the next week or two. --Justin ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Reg IPv6 Neighbor Advertisement Message fields
On Sun, Apr 08, 2018 at 04:34:16PM +, Vishal Deep Ajmera wrote: > Hi, > > We are trying to setup Neighbor Solicitation Responder using OpenFlow > pipeline in OVS however it seems some of the fields in Neighbor Advertisement > Message Format cannot be set using OpenFlow set actions. Following is the > frame format of NA message: > > 0 1 2 3 >0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type | Code | Checksum | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |R|S|O| Reserved| > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > + + > | | > + Target Address + > | | > + + > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Options ... > +-+-+-+-+-+-+-+-+-+-+-+- > > In the above message, fields R (Router flag), S (Solicited flag) and O > (Override flag) cannot be set. Is my understanding correct ? Yes. It would be reasonable to be able to match and set these, so I imagine that we would accept patches to enable that. > Also, is there a way to recalculate the checksum and write it to > checksum field when we set the Target Address? Whenever OVS changes any field, it updates the associated checksum. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss