Re: [mpls-linux-general] Problem with ip route + lsp

[James R. L. <jl...@mi...>]

On Thu, Dec 02, 2004 at 04:18:12PM -0500, Alexandra Alvarado wrote:
> Hello,
> 
> Thanks, now the MPLS-Linux example (http://perso.enst.fr/~casellas/mpls-linux/index.html) is working.  But, what is the real advantage? where can I apply the mpls? What is the sense to have MPLS in to PCs with the same network?
> 
> I would like to apply this between two remote linux!.  I Have for example two simple tunnel linux servers, each of one in differents cities with some routers in the middle, and I can make a vpn without ipsec between two remote edge with differents networks.  The only disadvantage
> is that I can't repeat de networks more than once.  MPLS improve this?, and if do; can you help me with some examples?

I do not quite follow what your points are.  One of the main advantage of MPLS
is the ability to tunnel traffic through a network.  For example I can
tunnel Layer 2 frames (ethernet) over an LSP to create a transparent ethernet
link across a MPLS network.  I can also connect pockets of private address
space to each other by tunneling the packets through an MPLS network.

Does this help answer your questions?

> 
> 
> Thanks for your help.
> 
> 
> Alexandra Alvarado
> 
>   ----- Original Message ----- 
>   From: Alexandra Alvarado 
>   To: mpl...@li... ; Alexandra Alvarado 
>   Sent: Wednesday, December 01, 2004 5:29 PM
>   Subject: [mpls-linux-general] Problem with ip route + lsp
> 
> 
>   Hello,
> 
>   I have installed in my linux fedora core 2 the next package:
> 
>   iproute-2.4.7-14mpls_1_935
>   mplsadm2-1.935-1
>   iptables-1.2.9-2.3.1mpls_1_938
>   quagga-0.96.4-1.1mpls_1_935
>   kernel-sourcecode-2.6.8-1.521mpls_1_938a
>   mplsadm2-1.938-1
>   kernel-2.6.6-1.435.2.3skas3_mpls_1_935
>   iptables-1.2.9-2.3.1mpls_1_935
>   iptables-ipv6-1.2.9-2.3.1mpls_1_935
>   glibc-kernheaders-2.4-8.44mpls
> 
>   After reboot the machine, I tried to configure the example:
> 
>   [root@mplsa 1_935]# mplsadm2 -A -O 0
>   MPLSADM mplsadm.c:692:main: Out segment input: 0
>   Key: 0x00000003
>   Out Segment add: Success
>   [root@mplsa 1_935]# 
> 
>   [root@mplsa 1_935]# mplsadm2 -O 0x3 -o push:gen:16:set:eth0:ipv4:128.104.18.114
>   MPLSADM mplsadm.c:692:main: Out segment input: 0x3
>   MPLSADM mplsadm.c:688:main: Out instr input: push:gen:16:set:eth0:ipv4:128.104.18.114
>   MPLSADM mplsadm.c:292:fill_instructions: Instruction: push
>   MPLSADM mplsadm.c:229:fill_label: Label type: gen
>   MPLSADM mplsadm.c:292:fill_instructions: Instruction: set
>   MPLSADM mplsadm.c:181:parse_nh_info: eth0
>   MPLSADM mplsadm.c:182:parse_nh_info: 128.104.18.114
>   MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol: ipv4
>   MPLSADM mplsadm.c:596:fill_instructions: Length: 2
>   Out Instr: Success
>   You have new mail in /var/spool/mail/root
>   [root@mplsa 1_935]# 
> 
>   The problem is HERE:
>   [root@mplsa 1_935]# ip route add 128.104.18.114/32 via 128.104.18.114 lsp 0x3
>   Error: either "to" is duplicate, or "lsp" is a garbage.
>   [root@mplsa 1_935]# 
> 
>   Why, I installed iproute-2.4.7-14mpls_1_935, and other version with lsp patch without succes?
> 
>   Can somebody say to me what is the problem or missconfiguration?
> 
>   Thanks
> 
> 
>   Alexandra Alvarado
> 
> 

-- 
James R. Leu
jl...@mi...