The EOS bit does get set automatically. This is necessary because when we do: ip route add 1.1.1.1/32 via 10.10.10.10 Eth out-label 66 we want the EOS bit for label 66 to be on. But when we then add ip route add 2.2.2.2/32 via 1.1.1.1 out-label 77 we now need the EOS bit for 66 to be both 0 and 1, depending on whether the traffic is destined to 2.2.2.2 or 1.1.1.1 resp. To handle this VPP builds EOS and non-EOS forwarding chains/DPOs – you can see these if you do ‘sh ip fib 1.1.1.1/32 detail’
Regards, neale From: Nagaprabhanjan Bellari <[email protected]> Date: Monday, 5 June 2017 at 08:56 To: "Neale Ranns (nranns)" <[email protected]> Cc: vpp-dev <[email protected]> Subject: Re: [vpp-dev] Can we set MPLS exp and ttl fields when programming out labels? Ok great! I will try to get a shot at it. Another related question: When we push one or more labels for a route - does the eos bit get set automatically for the bottom most label? Because - in the route api - we only push label values to the frp_label_stack - I was wondering how to set the eos bit for a label. Thanks, -nagp On Mon, Jun 5, 2017 at 1:23 PM, Neale Ranns (nranns) <[email protected]<mailto:[email protected]>> wrote: Hi nagp, There’s no means to do that currently, but it would be a welcome addition. Regards, Neale From: <[email protected]<mailto:[email protected]>> on behalf of Nagaprabhanjan Bellari <[email protected]<mailto:[email protected]>> Date: Monday, 5 June 2017 at 08:24 To: vpp-dev <[email protected]<mailto:[email protected]>> Subject: [vpp-dev] Can we set MPLS exp and ttl fields when programming out labels? The standard route API does not seem to allow this, so was wondering if there is any other means to achieve the same. Thanks, -nagp
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
