Re: [vpp-dev] VPP crashing if we configure srv6 policy with five sids in the sidlist

Simone, This should help: vpp-dev@lists.fd.io | VLIB headroom buffer size modfification Cheers, Pablo. From: vpp-dev@lists.fd.io On Behalf Of simone nafra via lists.fd.io Sent: martes, 6 de septiembre de 2022 9:02 To: vpp-dev@lists.fd.io Sub

Re: [vpp-dev] SRv6 on VPP running on Ubuntu VM

Rajesh, Hermant, You can find detailed SRv6 documentation in here https://docs.fd.io/vpp/21.01/db/d9b/srv6_doc.html In addition, there is a small SRv6 L3VPN tutorial available in here: https://wiki.fd.io/view/VPP/Segment_Routing_for_IPv6 Cheers, Pablo. From: vpp-dev@lists.fd.io On Behalf Of he

Re: [vpp-dev] Support for localsid behaviors (T.Insert, T.Encaps, H.Insert and H.Encaps)

Hi Chinmaya, Not sure I understand what you want to achieve. The SR policy is set to one of either H.Insert or H.Encaps. Any packet steered into that policy will use that behavior. Same applies for the relevant BindingSID. If you want to get both H.Insert and H.Encaps for the same SR Policy, the

Re: [vpp-dev] Support for localsid behaviors (T.Insert, T.Encaps, H.Insert and H.Encaps)

Hi Chinmaya, Yes, those are supported. T.Insert and T.Encaps were renamed into H.Insert and H.Encaps; and they are not localsid behaviors but rather an SR Headend behavior. Documentation is in here: https://docs.fd.io/vpp/20.09/db/db5/srv6_policy_doc.html Cheers, Pablo. From: vpp-dev@lists.fd

Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error

Chinmaya, Please see https://docs.fd.io/vpp/20.09/df/d96/sr__api_8c.html Regards, Pablo. From: vpp-dev@lists.fd.io On Behalf Of Chinmaya Aggarwal Sent: miércoles, 10 de junio de 2020 6:33 To: vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution givi

Re: [vpp-dev] Inline mode in Spray Policy

Hi Chinmaya, By default the SR policy uses encapsulation. If you want to change this behavior add the keyword “insert” to the sr policy command. Thanks, Pablo. From: vpp-dev@lists.fd.io On Behalf Of Chinmaya Aggarwal Sent: lunes, 30 de marzo de 2020 8:37 To: vpp-dev@lists.fd.io Subject: [vpp-d

Re: [vpp-dev] Interface Address as SRv6 SID

Hi Chinmaya, This feature is not supported in VPP. There is an open ticket for it. https://jira.fd.io/browse/VPP-1500 What is your use-case? Cheers, Pablo. From: on behalf of Chinmaya Aggarwal Date: Thursday, 6 February 2020 at 11:32 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] Interface Ad

Re: [vpp-dev] SRv6 header processing

Hi Feroz, Many thanks for testing this. I have opened a JIRA ticket to fix it. https://jira.fd.io/browse/VPP-1835 Thanks, Pablo. From: vpp-dev@lists.fd.io on behalf of Mohamed feroz Abdul majeeth Sent: Friday, January 31, 2020 12:36 PM To: vpp-dev Subject: [

Re: [vpp-dev] #govpp #vpp_1804 #vnet #vpp #vpp_hard_code #counters

Hi Ayyappa, An SRv6 LocalSID is represented as a /128 FIB entry. The FIB entry will bring the packet up to the graph node implementing the function associated with that segment. For each SRv6 LocalSID we will have some attributes associated to each one of them. These attributes might be for exa

Re: [vpp-dev] Questions about SIDs

Hi Yosh, The command is correct. The parameters to create each different type of SID are documented here: https://docs.fd.io/vpp/19.01/srv6_localsid_doc.html Thanks, Pablo. From: on behalf of Yosh Kikuchi Date: Wednesday, 21 November 2018 at 16:28 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev

Re: [vpp-dev] Destination Options processing in VPP

Thomas, AFAIC, the SRv6 code is compliant both with RFC8200 and the segment routing drafts. The VPP support for Destination Options header is independent from SR. Thanks, Pablo. From: on behalf of Thomas F Herbert Date: Tuesday, 21 August 2018 at 19:15 To: "dmar...@me.com" , Tom Herbert Cc:

Re: [vpp-dev] Destination Options processing in VPP

Tom, If a Destination Option appears before a Routing header, the Destination Option header is ignored (packet is NOT dropped). If you think its relevant to implement the Destination Option header option types 01, 10 and 11, please open a Jira ticket for it. [1] Thanks, Pablo. [1] http