p-dev@lists.fd.io" , "Neale Ranns (nranns)"
Subject: Re: [vpp-dev] #vpp vpls configuration
Thanks for reply. I change my configuration vpls based on topolgy.
VPLS configuration: MPLS L2VPN VPLS
VPP1-VM1
set int state eth1 up set int s
https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#packet_tracer
/neale
From: Omid Zeinalpour
Date: Tuesday, 1 May 2018 at 08:49
To: "vpp-dev@lists.fd.io" , "Neale Ranns (nranns)"
Subject: Re: [vpp-dev] #vpp vpls configuration
Thanks for reply. I change m
Thanks for reply. I change my configuration vpls based on topolgy.VPLS
configuration:MPLS L2VPN VPLS VPP1-VM1
set int state eth1 upset int state eth0 upset int ip address eth1
2.1.1.1/24
mpls tabel add 0 set interface mpls eth1 enablempls tunnel l
Looks OK to me. Packet trace maybe?
Just a note, you don’t need two out-labels on your tunnel (and so you don’t
need to neos entry on RX)
/neale
From: on behalf of "omid via Lists.Fd.Io"
Reply-To: "zeinalpouro...@yahoo.com"
Date: Monday, 30 April 2018 at 14:45
To: "vpp-dev@lists.fd.io"
Cc:
Hi,
Please try:
https://gerrit.fd.io/r/12014
you don’t need a next=hop when specifying an L2 receive path, so:
mpls local-label add eos 1023 via l2-input-on mpls-tunnel0
regards,
neale
From: on behalf of "omid via Lists.Fd.Io"
Reply-To: "zeinalpouro...@yahoo.com"
Date: Monday, 23 April
