I see.. so there is a need to add the "add eos" to the "mpls local-label" command if I want to send the packet to the IP lookup after popping a single (the only) label.
Thanks, Neale! On Mon, Aug 14, 2017 at 1:01 PM, Neale Ranns (nranns) <nra...@cisco.com> wrote: > > > Hi Michael, > > > > ‘add’ is the default. > > It’s necessary to specify ‘eos’ because it I the end-of-stack entry you > are adding and the default (i.e. without ‘eos’) is to add the > non-end-of-stack entry. > > > > Regards, > > neale > > > > *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Michael Borokhovich < > michael...@gmail.com> > *Date: *Monday, 14 August 2017 at 16:58 > *To: *"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> > *Subject: *[vpp-dev] MPLS labels question > > > > Hi, > > > > I'm adding a label using the following command: > > > > ip route add 10.100.2.0/24 table 1 via 10.100.4.12 GigabitEthernet0/6/0 > out-label 222 > > > > And on the receiving side poping it with: > > > > set interface mpls GigabitEthernet0/6/0 enable > > mpls local-label 222 ip4-lookup-in-table 1 > > > > However, this didn't work until I added "*add **eos*" to the last > command, i.e., the following worked: > > > > mpls local-label add eos 222 ip4-lookup-in-table 1 > > > > Why is it necessary to specify "*add **eos*" at the receiving side? Or > maybe my configuration of the sender's side is wrong? > > > > Thanks, > > Michael. > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
