mpls-linux-general — Mailing list for general discussion about MPLS for Linux

[mpls-linux-general] LSP lost when reboot

[taufico j. <tau...@ya...>]

When I reboot my computers, LSP that I have been
created is lost. How to permanently set LSP so that
when I reboot the LSP in still there? . Where do I
have to locate the commands (in order to create LSP)
so it is permenently exist.



Send instant messages to your online friends http://asia.messenger.yahoo.com 

[mpls-linux-general] My MPLS test-bed

[taufico j. <tau...@ya...>]

my MPLS test bed


 A          B          C          D        E
==1.1---1.2==2.1---2.2==4.2---4.1==5.1--5.2==
           3.1-------------------3.2


linux pc= A,B,C,D, and E
note: B and C consists 3 NICs
      A,C and E consists 2 NICs


Hello...I already try the example from (how to set up
LSP) trough this web page
http://mpls-linux.sourceforge.net/simple.php . Thus
the set up was successful  between A and B (please
refer to my test bed above). I also tried to set up
LSP between  B and A ..and it also was succesful.
  
 My questions are:
  
  
  1) I got confius when I want to set up LSP between A
and C, also between B and D. How the set up will be?
How to set up the ip route between them ?
  
 2) This test-bed intended to transmit MPLS packet
from A to E. The packet has two choices, either go
through (A)1.1 --1.2--2.1--2.2--4.2--4.1--5.1--5.2(E)
or (A)1.1--1.2--3.1--3.2--5.1--5.2(E). How?
  
 3) From your example given :
  
 uml1
 ----
 [root@uml1 root]# cat /sys/mpls/version
 1.946
 [root@uml1 root]# mpls nhlfe add key 0
 Key: 0x00000002
 [root@uml1 root]# mpls nhlfe change key 0x2
instructions push gen 10000 nexthop eth1 ipv4
11.0.1.2
 [root@uml1 root]# ip route add 11.0.1.2/32 via
11.0.1.2 spec_nh 0x8847 0x2
 [root@uml1 root]# mpls nhlfe show
 NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
         push gen 10000 set eth1 ipv4 11.0.1.2  (0
bytes, 0 pkts, 0 dropped)
 [root@uml1 root]# ip route show
 11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x2
 192.168.2.0/24 dev eth0  scope link
 11.0.1.0/24 dev eth1  proto kernel  scope link  src
11.0.1.1
 127.0.0.0/8 dev lo  scope link
 [root@uml1 root]#
 
  
 3i) What is the meaning of 
  
    "add key 0"
    "key 0x2"
    "spec_nh 0x8847 0x2"
  
 From your example I know the packet is labeled with
10000. Is this label is fix ?  Can I use other label
value?
  
 Can somebody help me..my project is nearly success...

Send instant messages to your online friends http://asia.messenger.yahoo.com 

[mpls-linux-general] LSP set up...Instructions please

[taufico j. <tau...@ya...>]

Below is my test -bed
 
 
    A                       B                        
C                            D
===== 1.1------1.2 ===== 2.1------2.2====
4.2-----------4.1 ===== 5.1             
                               I                      
                                 I        I
                             
3.1--------------------------------------------------3.2
      I
                                                      
                                         I
                                                      
                                         I    E
                                                      
                                      5.2=====   
 
 
Hello...I already try the example from (how to set up
LSP) http://mpls-linux.sourceforge.net/simple.php .
Thus the set up was successful  between A and B
(please refer to my test bed above). I also tried to
set up LSP between  B and A ..and it also was
succesful.
 
My questions are:
 
 
 1) I got confius when I want to set up LSP between B
and C, also between B and D. How the set up willl
be.?How to set up the ip route between them ?
 
2) This test-bed intended to transmit MPLS packet from
A to E. The packet has two choices, either go through
(A)1.1 --1.2--2.1--2.2--4.2--4.1--5.1--5.2(E) or
(A)1.1--1.2--3.1--3.2--5.1--5.2(E). How?
 
3) From your example given :
 
uml1
----
[root@uml1 root]# cat /sys/mpls/version
1.946
[root@uml1 root]# mpls nhlfe add key 0
Key: 0x00000002
[root@uml1 root]# mpls nhlfe change key 0x2
instructions push gen 10000 nexthop eth1 ipv4 11.0.1.2
[root@uml1 root]# ip route add 11.0.1.2/32 via
11.0.1.2 spec_nh 0x8847 0x2
[root@uml1 root]# mpls nhlfe show
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
        push gen 10000 set eth1 ipv4 11.0.1.2  (0
bytes, 0 pkts, 0 dropped)
[root@uml1 root]# ip route show
11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x2
192.168.2.0/24 dev eth0  scope link
11.0.1.0/24 dev eth1  proto kernel  scope link  src
11.0.1.1
127.0.0.0/8 dev lo  scope link
[root@uml1 root]#
 
3i) What is the meaning of
 
   "add key 0"
   "key 0x2"
   "spec_nh 0x8847 0x2"
 
From your example I know the packet is labeled with
0x8847, is this label is fix ?  Can I use other label
value? and what is the range of label values?
 
Can somebody help me..my project is nearly success...
 
 
Please..please..please


	
	
		
__________________________________ 
Do you Yahoo!? 
New and Improved Yahoo! Mail - 1GB free storage! 
http://sg.whatsnew.mail.yahoo.com

[mpls-linux-general] why I can not capture the LDP Hello packet?

[Shan J. <sha...@gm...>]

I have installed the rpm packages successfully. My platform is FC2 and
the packages are :
kernel-2.6.9-1.6_FC2mpls_1_946.i686.rpm;
iproute-2.6.9-3mpls1_946.i386.rpm;
quagga-0.97.3-1.FC3mpls1_946.i386.rpm

My configurations are:
zebra.conf:
hostname NP1
password zebra
enable password zebra
!interface lo
interface eth0
!multicast
!
ip route 2.0.0.0/8 1.0.0.254
!
log file zebra.log

ripd.conf:
hostname NP1
password zebra
router rip
!
network eth0
!
log file ripd.log
!

ldpd.conf:
hostname NP1
password root
enable password root
!
mpls ldp
!
interface lo
!
interface eth0
 mpls ldp
!
line vty
!
log file ldpd.log


then I run ethereal and capture packets on eth0, I could get the rip
Request packet but none packet about LDP, I think I should get the LDP
hello packet if LDP is runing well, Then what's wrong about me ? Is my
configuration wrong?

I will appreciate about your kind help.

[mpls-linux-general] LSP set up..instructions please!

[taufico j. <tau...@ya...>]

Below is my test -bed
 
 
    A                       B                         C                            D
===== 1.1------1.2 ===== 2.1------2.2==== 4.2-----------4.1 ===== 5.1              
                               I                                                        I        I
                              3.1--------------------------------------------------3.2       I
                                                                                                I
                                                                                                I    E
                                                                                             5.2=====   
 
 
Hello...I already try the example from (how to set up LSP) http://mpls-linux.sourceforge.net/simple.php . Thus the set up was successful  between A and B (please refer to my test bed above). I also tried to set up LSP between  B and A ..and it also was succesful.
 
My questions are:
 
 
 1) I got confius when I want to set up LSP between B and C, also between B and D. How the set up willl be.?How to set up the ip route between them ?
 
2) This test-bed intended to transmit MPLS packet from A to E. The packet has two choices, either go through (A)1.1 --1.2--2.1--2.2--4.2--4.1--5.1--5.2(E) or (A)1.1--1.2--3.1--3.2--5.1--5.2(E). How?
 
3) From your example given :
 
uml1
----
[root@uml1 root]# cat /sys/mpls/version
1.946
[root@uml1 root]# mpls nhlfe add key 0
Key: 0x00000002
[root@uml1 root]# mpls nhlfe change key 0x2 instructions push gen 10000 nexthop eth1 ipv4 11.0.1.2
[root@uml1 root]# ip route add 11.0.1.2/32 via 11.0.1.2 spec_nh 0x8847 0x2
[root@uml1 root]# mpls nhlfe show
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
        push gen 10000 set eth1 ipv4 11.0.1.2  (0 bytes, 0 pkts, 0 dropped)
[root@uml1 root]# ip route show
11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x2
192.168.2.0/24 dev eth0  scope link
11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.1
127.0.0.0/8 dev lo  scope link
[root@uml1 root]#

 
3i) What is the meaning of 
 
   "add key 0"
   "key 0x2"
   "spec_nh 0x8847 0x2"
 
From your example I know the packet is labeled with 0x8847, is this label is fix ?  Can I use other label value? and what is the range of label values?
 
Can somebody help me..my project is nearly success...
 
 
Please..please..please
 
 

		
---------------------------------
Do you Yahoo!?
 New and Improved Yahoo! Mail - 1GB free storage!

Re: [mpls-linux-general] Upgrading RPMs ...done..now problem with ppp..

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

"please..please..please" read the examples at http://mpls-linux.sf.net
web page.  Many of your answers can be found there.

As for the ppp RPM, you only need it if you are going to run MPLS over
some PPP links (async or syn serial).  Otherwise you can skip installing
it.

On Mon, Aug 22, 2005 at 12:44:39PM +0800, taufico jose wrote:
> Hello thanks for the previous problems, i had solved them. Now i have upg=
rade all these files (below) and the process was succesful:
> =20
> kernel=20
> iptables=20
> quagga
> iproute
> =20
> But there are some problems and for easy reading i listed all the problem=
s below:
> =20
> 1) When i try to upgrade ppp rpm, there is dependencies problem. The outp=
ut said that one file is needed by ppp rpm. How do i get the file ??. Then =
i read through the notifications (doc) that comes with MPLS  1.946  said th=
at : if there are problems occur when upgarding the rpms file, just install=
 the kernel header that comes  with MPLS 1.946 package, which is glibc-kern=
headers....
> =20
> Then i installed this glibc-kernheader and it was succesful. But when i t=
ry to upgrade the ppp (rpm), the same problem occured. How do i solve this =
  problem ???  Where i can get the dependent file needed by ppp rpm???
> =20
> 2)=20
> When i have installed all the rpms (listed above).=20
> i) How do i know that my computer is MPLS enabled ???
> ii) What is the directory of MPLS ???
> iii) How do i enable or disable MPLS when boot time ???
> =20
> 3) When i checked my current running kernel with this command:
> =20
>      /usr/src/linux*
> =20
> the output showed was linux-2.6.5.bla..bla..Why the output is not linux-m=
pls..bla..bla since i had  booted in MPLS kernel.
> =20
> Then, when i browsed through the /usr/src directory, there is no MPLs fol=
der insteads redhat folder and previous kernel linux folder (linux 2.6.5..b=
la..bla..). Why ???
> =20
> Can somebody help me by giving me suggestion or explainations..please..pl=
ease..please
> =20
> =20
> =20
> =20
> =20
> =20
>=20
>=20
>=20
>=20
> 	=09
> ---------------------------------
> Meet your soulmate!
>  Yahoo! Asia presents Meetic - where millions of singles gather=20
--=20
James R. Leu
jl...@mi...

[mpls-linux-general] Upgrading RPMs ...done..now problem with ppp..

[taufico j. <tau...@ya...>]

Hello thanks for the previous problems, i had solved them. Now i have upgrade all these files (below) and the process was succesful:
 
kernel 
iptables 
quagga
iproute
 
But there are some problems and for easy reading i listed all the problems below:
 
1) When i try to upgrade ppp rpm, there is dependencies problem. The output said that one file is needed by ppp rpm. How do i get the file ??. Then i read through the notifications (doc) that comes with MPLS  1.946  said that : if there are problems occur when upgarding the rpms file, just install the kernel header that comes  with MPLS 1.946 package, which is glibc-kernheaders....
 
Then i installed this glibc-kernheader and it was succesful. But when i try to upgrade the ppp (rpm), the same problem occured. How do i solve this   problem ???  Where i can get the dependent file needed by ppp rpm???
 
2) 
When i have installed all the rpms (listed above). 
i) How do i know that my computer is MPLS enabled ???
ii) What is the directory of MPLS ???
iii) How do i enable or disable MPLS when boot time ???
 
3) When i checked my current running kernel with this command:
 
     /usr/src/linux*
 
the output showed was linux-2.6.5.bla..bla..Why the output is not linux-mpls..bla..bla since i had  booted in MPLS kernel.
 
Then, when i browsed through the /usr/src directory, there is no MPLs folder insteads redhat folder and previous kernel linux folder (linux 2.6.5..bla..bla..). Why ???
 
Can somebody help me by giving me suggestion or explainations..please..please..please
 
 
 
 
 
 




		
---------------------------------
Meet your soulmate!
 Yahoo! Asia presents Meetic - where millions of singles gather 

Re: [mpls-linux-general] Problem with mpls linux 1.946

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

You need to upgrade to to the MPLS enabled iproute RPM, not just
install it ....=20

    rpm -Uvh iproute-2.6.9-3mpls1_946.i386.rpm

as opposed to

    rpm -ivh iproute-2.6.9-3mpls1_946.i386.rpm

On Fri, Aug 19, 2005 at 10:49:37AM +0800, taufico jose wrote:
> My Project: Development of MPLS test-bed=20
>=20
>=20
>=20
> hello, i had installed FD2 in my computers (5 pcs).
> Then i also installed the kernel rpm that is
> kernel-2.6.9-9-1.6_FC2mpls_1_946a.i386.rpm which i got
> from Project Homepage of Mpls-Linux. The installation
> was succesful. But then, when i tried to installed
> iproute-2.6.9-3mpls1_946.i386.rpm there are conflicts
> happened. The outputs such below:
> {
> Preparing...              =20
> ########################################### [100%]
>         file /sbin/ip from install of
> iproute-2.6.9-3mpls1_946 conflicts with fi le from
> package iproute-2.4.7-14
>         file /sbin/rtmon from install of
> iproute-2.6.9-3mpls1_946 conflicts with  file from
> package iproute-2.4.7-14
>         file /sbin/tc from install of
> iproute-2.6.9-3mpls1_946 conflicts with fi le from
> package iproute-2.4.7-14
>         file /usr/sbin/nstat from install of
> iproute-2.6.9-3mpls1_946 conflicts with file from
> package ipr
>=20
> oute-2.4.7-14
>         file /usr/sbin/rtacct from install of
> iproute-2.6.9-3mpls1_946 conflicts  with file from
> package iproute-2.4.7-14
>         file /usr/sbin/rtstat from install of
> iproute-2.6.9-3mpls1_946 conflicts  with file from
> package iproute-2.4.7-14
>         file /usr/sbin/ss from install of
> iproute-2.6.9-3mpls1_946 conflicts wit h file from
> package iproute-2.4.7-14
>         file /usr/share/man/man8/ip.8.gz from install
> of iproute-2.6.9-3mpls1_94 6 conflicts with file from
> package iproute-2.4.7-14
>=20
> } What are these meant ?
>=20
> Then i just ignore it, and i tried to install
> ppp-2.4.2-6.4.FC3mpls1_946.i386.rpm but the outputs
> seem like below:
> {
> [root@localhost mpls-linux-1.946]# rpm -ivh
> ppp-2.4.2-6.4.FC3mpls1_946.i386.rpm
> error: Failed dependencies:
>         libpcap >=3D 14:0.8.3-6 is needed by
> ppp-2.4.2-6.4.FC3mpls1_946
> [root@localhost mpls-linux-1.946]#
> }..
>=20
> Can somebody out there explain to me or give some
> ideas or some instructions to implement MPLS-linux
> (1.946). The steps to install files from
> Mpls-linux-1.946 package. Please..please..and please.
>=20
>=20
>=20
>=20
> 	=09
> __________________________________=20
> Meet your soulmate!
> Yahoo! Asia presents Meetic - where millions of singles gather
> http://asia.yahoo.com/meetic
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

[mpls-linux-general] Problem with mpls linux 1.946

[taufico j. <tau...@ya...>]

My Project: Development of MPLS test-bed 



hello, i had installed FD2 in my computers (5 pcs).
Then i also installed the kernel rpm that is
kernel-2.6.9-9-1.6_FC2mpls_1_946a.i386.rpm which i got
from Project Homepage of Mpls-Linux. The installation
was succesful. But then, when i tried to installed
iproute-2.6.9-3mpls1_946.i386.rpm there are conflicts
happened. The outputs such below:
{
Preparing...               
########################################### [100%]
        file /sbin/ip from install of
iproute-2.6.9-3mpls1_946 conflicts with fi le from
package iproute-2.4.7-14
        file /sbin/rtmon from install of
iproute-2.6.9-3mpls1_946 conflicts with  file from
package iproute-2.4.7-14
        file /sbin/tc from install of
iproute-2.6.9-3mpls1_946 conflicts with fi le from
package iproute-2.4.7-14
        file /usr/sbin/nstat from install of
iproute-2.6.9-3mpls1_946 conflicts with file from
package ipr

oute-2.4.7-14
        file /usr/sbin/rtacct from install of
iproute-2.6.9-3mpls1_946 conflicts  with file from
package iproute-2.4.7-14
        file /usr/sbin/rtstat from install of
iproute-2.6.9-3mpls1_946 conflicts  with file from
package iproute-2.4.7-14
        file /usr/sbin/ss from install of
iproute-2.6.9-3mpls1_946 conflicts wit h file from
package iproute-2.4.7-14
        file /usr/share/man/man8/ip.8.gz from install
of iproute-2.6.9-3mpls1_94 6 conflicts with file from
package iproute-2.4.7-14

} What are these meant ?

Then i just ignore it, and i tried to install
ppp-2.4.2-6.4.FC3mpls1_946.i386.rpm but the outputs
seem like below:
{
[root@localhost mpls-linux-1.946]# rpm -ivh
ppp-2.4.2-6.4.FC3mpls1_946.i386.rpm
error: Failed dependencies:
        libpcap >= 14:0.8.3-6 is needed by
ppp-2.4.2-6.4.FC3mpls1_946
[root@localhost mpls-linux-1.946]#
}..

Can somebody out there explain to me or give some
ideas or some instructions to implement MPLS-linux
(1.946). The steps to install files from
Mpls-linux-1.946 package. Please..please..and please.




		
__________________________________ 
Meet your soulmate!
Yahoo! Asia presents Meetic - where millions of singles gather
http://asia.yahoo.com/meetic

[mpls-linux-general] MPLS test-bed....Steps

[taufico j. <tau...@ya...>]

Hello, basically my project refers to mpls-linux homepage ( 
http://mpls-linux.sourceforge.net/ ) that based on Fedora 
Core 2. What do you mean, when you reply (my previous e-
mail)  that i might to consider to use Fedora Core 3(FD3) 
instead fedora core 2. Actually i already installed Fedora 
Core 2 in my computers ( 5 pcs). It is not a problem if i have 
to install FD3, but i really want to know if that any reason. 
Where do i can get yum and apt-get? i already downloaded 
all files (mpls-linux 1.946) and which rpms that i need to 
install first?. Do you have any guide on this?. My project is 
only want to apply MPLS functionality in my test-bed, i hope 
it can be simple. Thanx


Send instant messages to your online friends http://asia.messenger.yahoo.com 

Re: [mpls-linux-general] how much of LDP is actually working?

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

Hasso,

That would be great.  Let me know if you find any conflicts that need
explanation.

Jim

On Fri, Aug 12, 2005 at 03:43:08PM +0300, Hasso Tepper wrote:
> Razvan Deaconescu wrote:
> > i have finally managed to get ospfd and ldpd working using quagga-mpls
> > from your development tree; the problem was a piece of code that had
> > to be removed (i just wrapped it inside a comment)
> >=20
> > line 2433:
> >=20
> >  else if (oi->state =3D=3D ISM_InterfaceDown)
> >    {
> >      zlog_warn ("Ignoring packet from [%s] received on interface that i=
s "
> >                 "down [%s]",
> >                 inet_ntoa (iph->ip_src), ifp->name);
> >      stream_free (ibuf);
> >      return 0;
> >    }
>=20
> - else if (oi->state =3D=3D ISM_InterfaceDown)
> + else if (oi->state =3D=3D ISM_Down)
> =20
> > ospfd can't run properly because it is informed (probably by the zebra
> > daemon) that the interface is down; however, if i do something to that
> > interface outside of ospfd (for example, i added a static route using
> > ip route) the interface comes up and ospfd starts running
> >=20
> > i don't know if this bug is a quagga bug; i haven't' dug into the code
> > yet (I'll probably do that soon)
> >=20
> > I've looked in the original quagga-0.98.0 version and saw that this
> > piece of code is absent; it makes sense to add it, but why did you do
> > it?
>=20
> Probably because quagga-mpls isn't exactly 0.98.0, but quagga_0_98_stable
> branch from CVS. This particular problem was regression introduced later
> in development process and is already fixed in Quagga.
>=20
> James, I volunteer to put together patch to update quagga-mpls to latest
> quagga_0_98_stable code. Would it be OK? I will release Quagga 0.98.5 in
> the beginning of the next week probably and would look it right after
> that.
>=20
>=20
> --=20
> Hasso Tepper
> Elion Enterprises Ltd.
> WAN administrator

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

[mpls-linux-general] how Label pushing is implemented in static mode?

[hamed h. <ham...@ya...>]

 I am trying to understand that how Cisco routers push
 a label on label in the static mode configuration of
 MPLS,I am trying to implement this protocol in static
 mode but I haven't understood that how should I
 implement the pushing labels algorithm please if
 anyone know something about it answers me 
 thanks

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [mpls-linux-general] how much of LDP is actually working?

[Hasso T. <ha...@es...>]

Razvan Deaconescu wrote:
> i have finally managed to get ospfd and ldpd working using quagga-mpls
> from your development tree; the problem was a piece of code that had
> to be removed (i just wrapped it inside a comment)
> 
> line 2433:
> 
>  else if (oi->state == ISM_InterfaceDown)
>    {
>      zlog_warn ("Ignoring packet from [%s] received on interface that is "
>                 "down [%s]",
>                 inet_ntoa (iph->ip_src), ifp->name);
>      stream_free (ibuf);
>      return 0;
>    }

- else if (oi->state == ISM_InterfaceDown)
+ else if (oi->state == ISM_Down)
 
> ospfd can't run properly because it is informed (probably by the zebra
> daemon) that the interface is down; however, if i do something to that
> interface outside of ospfd (for example, i added a static route using
> ip route) the interface comes up and ospfd starts running
> 
> i don't know if this bug is a quagga bug; i haven't' dug into the code
> yet (I'll probably do that soon)
> 
> I've looked in the original quagga-0.98.0 version and saw that this
> piece of code is absent; it makes sense to add it, but why did you do
> it?

Probably because quagga-mpls isn't exactly 0.98.0, but quagga_0_98_stable
branch from CVS. This particular problem was regression introduced later
in development process and is already fixed in Quagga.

James, I volunteer to put together patch to update quagga-mpls to latest
quagga_0_98_stable code. Would it be OK? I will release Quagga 0.98.5 in
the beginning of the next week probably and would look it right after
that.


-- 
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator

Re: [mpls-linux-general] how much of LDP is actually working?

[Razvan D. <raz...@gm...>]

On 8/10/05, James R. Leu <jl...@mi...> wrote:

> I will try and look at your data tonight and see if I can find anything.
> But the first thing is you need to get OSPF running.
>=20


i have finally managed to get ospfd and ldpd working using quagga-mpls
from your development tree; the problem was a piece of code that had
to be removed (i just wrapped it inside a comment)

line 2433:

 else if (oi->state =3D=3D ISM_InterfaceDown)
   {
     zlog_warn ("Ignoring packet from [%s] received on interface that is "
                "down [%s]",
                inet_ntoa (iph->ip_src), ifp->name);
     stream_free (ibuf);
     return 0;
   }

ospfd can't run properly because it is informed (probably by the zebra
daemon) that the interface is down; however, if i do something to that
interface outside of ospfd (for example, i added a static route using
ip route) the interface comes up and ospfd starts running

i don't know if this bug is a quagga bug; i haven't' dug into the code
yet (I'll probably do that soon)

I've looked in the original quagga-0.98.0 version and saw that this
piece of code is absent; it makes sense to add it, but why did you do
it?

i don't know if that piece of code was supposed to keep things on
track; removing it made LDP work, although "work" is not a very good
way to express the way it acts; i know it's a dynamic protocol but it
seems to be too dynamic; in less than 3 minutes it continuously
changed label values (I've been using 4 machines in a linear topology)
and a ping didn't work (it managed to reach the other end but got lost
on its way back); here is the output of two sequential commands on the
ldpd CLI:

ldpd_mpls2# show ldp database
  11.0.3.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.2.0/30  local binding:   label: gen 10000
  11.0.3.0/30  local binding:   label: gen 10001
  11.0.4.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.2.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.1.0/30  local binding:   label: gen 10002
  11.0.1.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.2.0/30  local binding:   label: gen 10102
  11.0.3.0/30  local binding:   label: gen 10103
  11.0.1.0/30  remote binding:  label: gen 10090 lsr: 11.0.1.2:0 ingress
  11.0.1.0/30  local binding:   label: gen 10105
  11.0.2.0/30  remote binding:  no outlabel lsr: 11.0.1.2:0
  11.0.3.0/30  remote binding:  no outlabel lsr: 11.0.1.2:0
ldpd_mpls2# show ld
ldpd_mpls2# show ldp da
ldpd_mpls2# show ldp database
  11.0.3.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.2.0/30  local binding:   label: gen 10000
  11.0.3.0/30  local binding:   label: gen 10001
  11.0.4.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.2.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0
  11.0.1.0/30  local binding:   label: gen 10002
  11.0.1.0/30  remote binding:  no outlabel lsr: 11.0.3.2:0

as you can see some labels start disappearing (a little later ldpd crashes =
:) )

somewhere between those those two commands i used the mpls command to
look at some of the kernel MPLS objects that ldpd created; here's the
output

root@MPLS-2:/home/mpls2# mpls ilm show
ILM entry label gen 10117 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts, 0 dropped)
ILM entry label gen 10115 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts, 0 dropped)
ILM entry label gen 10114 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts, 0 dropped)
ILM entry label gen 10002 labelspace 0 proto ipv4
        pop peek  (59928 bytes, 681 pkts, 0 dropped)
ILM entry label gen 10001 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts, 0 dropped)
ILM entry label gen 10000 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts, 0 dropped)
root@MPLS-2:/home/mpls2# mpls nhlfe show
NHLFE entry key 0x0000001f mtu 1496 propagate_ttl
        push gen 10106 set eth1 ipv4 11.0.2.1  (1024 bytes, 14 pkts, 0 drop=
ped)
NHLFE entry key 0x0000001e mtu 1496 propagate_ttl
        push gen 10102 set eth1 ipv4 11.0.2.1  (5150 bytes, 65 pkts, 0 drop=
ped)
NHLFE entry key 0x0000001d mtu 1496 propagate_ttl
        push gen 10098 set eth1 ipv4 11.0.2.1  (5150 bytes, 65 pkts, 0 drop=
ped)
NHLFE entry key 0x0000001c mtu 1496 propagate_ttl
        push gen 10094 set eth1 ipv4 11.0.2.1  (5150 bytes, 65 pkts, 0 drop=
ped)
NHLFE entry key 0x0000001b mtu 1496 propagate_ttl
        push gen 10090 set eth1 ipv4 11.0.2.1  (5150 bytes, 65 pkts, 0 drop=
ped)
NHLFE entry key 0x0000001a mtu 1496 propagate_ttl
        push gen 10086 set eth1 ipv4 11.0.2.1  (5062 bytes, 64 pkts, 0 drop=
ped)
NHLFE entry key 0x00000019 mtu 1496 propagate_ttl
        push gen 10082 set eth1 ipv4 11.0.2.1  (4998 bytes, 63 pkts, 0 drop=
ped)
NHLFE entry key 0x00000018 mtu 1496 propagate_ttl
        push gen 10078 set eth1 ipv4 11.0.2.1  (4718 bytes, 59 pkts, 0 drop=
ped)
NHLFE entry key 0x00000017 mtu 1496 propagate_ttl
        push gen 10074 set eth1 ipv4 11.0.2.1  (4884 bytes, 61 pkts, 0 drop=
ped)
NHLFE entry key 0x00000016 mtu 1496 propagate_ttl
        push gen 10070 set eth1 ipv4 11.0.2.1  (5094 bytes, 62 pkts, 0 drop=
ped)
NHLFE entry key 0x00000015 mtu 1496 propagate_ttl
        push gen 10066 set eth1 ipv4 11.0.2.1  (4902 bytes, 61 pkts, 0 drop=
ped)
NHLFE entry key 0x00000014 mtu 1496 propagate_ttl
        push gen 10064 set eth1 ipv4 11.0.2.1  (4990 bytes, 60 pkts, 0 drop=
ped)
NHLFE entry key 0x00000013 mtu 1496 propagate_ttl
        push gen 10060 set eth1 ipv4 11.0.2.1  (4864 bytes, 61 pkts, 0 drop=
ped)
NHLFE entry key 0x00000012 mtu 1496 propagate_ttl
        push gen 10056 set eth1 ipv4 11.0.2.1  (4846 bytes, 61 pkts, 0 drop=
ped)
NHLFE entry key 0x00000011 mtu 1496 propagate_ttl
        push gen 10052 set eth1 ipv4 11.0.2.1  (3960 bytes, 50 pkts, 0 drop=
ped)
NHLFE entry key 0x00000010 mtu 1496 propagate_ttl
        push gen 10050 set eth1 ipv4 11.0.2.1  (1650 bytes, 20 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000f mtu 1496 propagate_ttl
        push gen 10046 set eth1 ipv4 11.0.2.1  (1384 bytes, 17 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000e mtu 1496 propagate_ttl
        push gen 10044 set eth1 ipv4 11.0.2.1  (1496 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000d mtu 1496 propagate_ttl
        push gen 10040 set eth1 ipv4 11.0.2.1  (1066 bytes, 16 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000c mtu 1496 propagate_ttl
        push gen 10036 set eth1 ipv4 11.0.2.1  (1102 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000b mtu 1496 propagate_ttl
        push gen 10034 set eth1 ipv4 11.0.2.1  (1546 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x0000000a mtu 1496 propagate_ttl
        push gen 10030 set eth1 ipv4 11.0.2.1  (1308 bytes, 17 pkts, 0 drop=
ped)
NHLFE entry key 0x00000009 mtu 1496 propagate_ttl
        push gen 10026 set eth1 ipv4 11.0.2.1  (1104 bytes, 16 pkts, 0 drop=
ped)
NHLFE entry key 0x00000008 mtu 1496 propagate_ttl
        push gen 10024 set eth1 ipv4 11.0.2.1  (1192 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x00000007 mtu 1496 propagate_ttl
        push gen 10020 set eth1 ipv4 11.0.2.1  (1066 bytes, 16 pkts, 0 drop=
ped)
NHLFE entry key 0x00000006 mtu 1496 propagate_ttl
        push gen 10016 set eth1 ipv4 11.0.2.1  (1066 bytes, 16 pkts, 0 drop=
ped)
NHLFE entry key 0x00000005 mtu 1496 propagate_ttl
        push gen 10012 set eth1 ipv4 11.0.2.1  (1014 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x00000004 mtu 1496 propagate_ttl
        push gen 10008 set eth1 ipv4 11.0.2.1  (1026 bytes, 15 pkts, 0 drop=
ped)
NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
        push gen 10004 set eth1 ipv4 11.0.2.1  (1142 bytes, 16 pkts, 0 drop=
ped)
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
        push gen 10000 set eth1 ipv4 11.0.2.1  (1408 bytes, 14 pkts, 0 drop=
ped)
root@MPLS-2:/home/mpls2# mpls xc show
root@MPLS-2:/home/mpls2#=20

i don't know why the ldpd keeps creating nhlfe (which is the main
reason or effect why so many labels are generated)?

do you have any ideas why these things happen? and if you do, some
pointers about where to start looking for bugs the code would be
appreciated

Razvan

Re: [mpls-linux-general] how much of LDP is actually working?

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

> hi,
>=20
> i've managed to remove the errors that showed up at the configuration
> (it had to do with an outdated version of automake); i've recompiled
> my patched quagga-0.98.0 but the ouput is still the same (no
> outlabels); i've also recompiled quagga-mpls, but, just as before,
> ospf isn't working (the routers keep sending hello messages but
> without reply)

You will need OSPF to be working before you will get valid
data show in the out-labels.  If you see an entry in the database it
means that you've sent or received a label for that FEC (depending on
whether it is local or remote binding).  If the LDP speaker is not the
next hop for the FEC then I do not show the label sent for the remove
binding.  I should probably change this and just put (inactive) after
the entry.

> i've also put my topology figure at
> http://atlantis.cs.pub.ro/~razvand/ldpd-output.txt
> as i saw it was pretty messed up

I will try and look at your data tonight and see if I can find anything.
But the first thing is you need to get OSPF running.

> Razvan
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] how much of LDP is actually working?

[Razvan D. <raz...@gm...>]

On 8/10/05, Razvan Deaconescu <raz...@gm...> wrote:
> On 8/10/05, James R. Leu <jl...@mi...> wrote:
> >
> > I would say 95% of the protocol is implemented.  The parts that are
> > missing are related to Notification messages.  In addition I haven't
> > looked over 3036bis yet to see what other changes are needed.
> >
> > If you're serious about trying to help the first thing to understand
> > is that the quagga porting layer is modeled after juniper's use of LDP.
> > In other words don't expect label distribution for every route in the
> > routing table, only for those which are directly connected to a LDP spe=
aker.
> > Also I think there is a bug in the MPLS infrastructure for FTN bindings=
.
> >
> > Give me some output of show commands and an explanation of what you
> > would expect to see and we can decide where to focus a bug hunt.
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
> >
> >
>

hi,

i've managed to remove the errors that showed up at the configuration
(it had to do with an outdated version of automake); i've recompiled
my patched quagga-0.98.0 but the ouput is still the same (no
outlabels); i've also recompiled quagga-mpls, but, just as before,
ospf isn't working (the routers keep sending hello messages but
without reply)

i've also put my topology figure at
http://atlantis.cs.pub.ro/~razvand/ldpd-output.txt
as i saw it was pretty messed up

Razvan

Re: [mpls-linux-general] how much of LDP is actually working?

[Razvan D. <raz...@gm...>]

On 8/10/05, James R. Leu <jl...@mi...> wrote:
>=20
> I would say 95% of the protocol is implemented.  The parts that are
> missing are related to Notification messages.  In addition I haven't
> looked over 3036bis yet to see what other changes are needed.
>=20
> If you're serious about trying to help the first thing to understand
> is that the quagga porting layer is modeled after juniper's use of LDP.
> In other words don't expect label distribution for every route in the
> routing table, only for those which are directly connected to a LDP speak=
er.
> Also I think there is a bug in the MPLS infrastructure for FTN bindings.
>=20
> Give me some output of show commands and an explanation of what you
> would expect to see and we can decide where to focus a bug hunt.
>=20
> --
> James R. Leu
> jl...@mi...
>=20
>=20
>=20

i am pretty serious about getting involved;
i have managed to access your repository, compiled quagga-mpls but it
did'n work (as a matter of fact ospfd didn't work); i patched a fresh
quagga-0.98.0 with the quagga patch from the mpls-linux-1.946a package
and got much better results;
however, when configuring quagga-mpls, my patched version and EVEN the
original quagga-0.98.0 version some configuration error messages
showed up (when running autoreconf or ./update-autotools):

root@MPLS4:/usr/src/quagga-test/test/quagga-0.98.0# autoreconf
aclocal.m4: 13336: `automake requires `AM_CONFIG_HEADER', not
`AC_CONFIG_HEADER'configure.ac: 13336: required file
`./[config.h])].in' not found
zebra/Makefile.am:51: invalid variable `dist_examples_DATA'
ripd/Makefile.am:23: invalid variable `dist_examples_DATA'
ripngd/Makefile.am:23: invalid variable `dist_examples_DATA'
bgpd/Makefile.am:30: invalid variable `dist_examples_DATA'
ospfd/Makefile.am:37: invalid variable `dist_examples_DATA'
ospf6d/Makefile.am:30: invalid variable `dist_examples_DATA'
isisd/Makefile.am:31: invalid variable `dist_examples_DATA'
vtysh/Makefile.am:17: invalid variable `dist_examples_DATA'
vtysh/Makefile.am:11: invalid unused variable name: `nodist_vtysh_SOURCES'
doc/Makefile.am:21: invalid unused variable name: `figures_SOURCES'
autoreconf: automake failed with exit status: 1

i have sent a message to the quagga-users list;
is this normal? (does it happen to you - or am i missing some tool)

nevertheless, i compiled it and launched all the necessary daemons
(zebra, ospfd, ldpd)

this is the network topology i used; the link below contains various
show commands for the ldpd daemon


                                             +-------  SWITCH  ------------=
 +
                                          /                   |      =20
                     \
                                       /                      |      =20
                        \
                                    /                         |      =20
                           \
                                 /                            |      =20
                              \
           (....54)  E0   /                               | E0
(141.85.37.169)         \    E0  (...36)
                           /            E1(11.0.3.1)   |             =20
                             \     E1(11.0.1.2)
   ---------------mpls1-----------------------mpls2------------------------=
-----mpls3----------
    E1(11.0.4.1)     E2(11.0.3.2)                 E2(11.0.2.2)  =20
E2(11.0.2.1)  |
                                                                     =20
                                       |
                                                                     =20
                                       | E3(11.0.5.1)

E0, E1, E2 - stands for eth0, eth1, eth2

i used the switch for Internet access and for easy ssh access from one
machine to the other (i only have one monitor)

only the mpls1-E1, mpls-E1, mpls2-E2, mpls3-E2 are running ldpd
mpls3-E1 is also running ospfd (there's another router with the
11.0.1.1 address - but i was afraid to run ldpd on it because of a
crash :D )

this is the link with the output of the show commands for the ldpd
daemon (they use a bit of space and i didn't want to overfill this
message - it's pretty verbose the way it is)

http://atlantis.cs.pub.ro/~razvand/ldpd-output.txt

as you can see the problem is similar to that presented in the link
from the previous mail; there are NO OUTGOING LABELS

i am looking forward for comments and suggestions where to start
"digging" for bugs

Razvan

Re: [mpls-linux-general] how much of LDP is actually working?

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

On Tue, Aug 09, 2005 at 03:02:22PM +0300, Razvan Deaconescu wrote:
> Hi James,
>=20
> i have managed to acces your P4 development tree, compile and install
> the latest quagga-mpls suite (ldp included);
>=20
> however i ran in the same problems that are mentioned here
> http://sourceforge.net/mailarchive/message.php?msg_id=3D11547051

The have been significant changes since then.  I wouldn't
trust anything with regards to LDP before 2005.

> you have that demand unsolicited is well tested (and that is what i
> used); did you mean to say that it doesn't crash, or it really works
> (i mean label distribution, LSP generation, MPLS forwarding)?

I should remove that statement.  The internals of LDP have been well
tested on other platforms.  The quagga-mpls infrastructure is immature
and is the source of most of the problems.  The other source of
problems that is I overhauled the FEC handling code to accommodate
non-IPv4 FECs (martini FECs are what I had in mind when making the
changes).

> what i want to know is how much of LDP is actually working? this way i
> can find out whether i haven't made a mistake in my
> install/configuration; is the entire protocol implemented (some parts
> may need adjusting of course) or are the parts of the communication
> protocol that are still missing (in which case i will probably head on
> to the development team :-) )? if the former is true, where should i
> start with "getting my hands dirty": the ldp-portable-0.800 source
> code, or the quagga-zebra interraction with ldp?

I would say 95% of the protocol is implemented.  The parts that are
missing are related to Notification messages.  In addition I haven't
looked over 3036bis yet to see what other changes are needed.

If you're serious about trying to help the first thing to understand
is that the quagga porting layer is modeled after juniper's use of LDP.
In other words don't expect label distribution for every route in the
routing table, only for those which are directly connected to a LDP speaker.
Also I think there is a bug in the MPLS infrastructure for FTN bindings.

Give me some output of show commands and an explanation of what you
would expect to see and we can decide where to focus a bug hunt.

> regards,
> Razvan
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

[mpls-linux-general] how much of LDP is actually working?

[Razvan D. <raz...@gm...>]

Hi James,

i have managed to acces your P4 development tree, compile and install
the latest quagga-mpls suite (ldp included);

however i ran in the same problems that are mentioned here
http://sourceforge.net/mailarchive/message.php?msg_id=3D11547051

you have that demand unsolicited is well tested (and that is what i
used); did you mean to say that it doesn't crash, or it really works
(i mean label distribution, LSP generation, MPLS forwarding)?

what i want to know is how much of LDP is actually working? this way i
can find out whether i haven't made a mistake in my
install/configuration; is the entire protocol implemented (some parts
may need adjusting of course) or are the parts of the communication
protocol that are still missing (in which case i will probably head on
to the development team :-) )? if the former is true, where should i
start with "getting my hands dirty": the ldp-portable-0.800 source
code, or the quagga-zebra interraction with ldp?

regards,
Razvan

Re: [mpls-linux-general] Testing with Iperf

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

There have been many emails to the list about this.  Please search the
mailing list archive for my response.

On Mon, Aug 08, 2005 at 05:17:29PM +0200, Miquel Casanovas Puigvi wrote:
> Hello,,
>=20
> I have the next structure and run under mpls perfectly,
>=20
> prefix: 192.168.x.x
>=20
> host_1(LER) <----> host_2(LSR) <----> host_3(LSR) <----> host_4 (LER)
> on x.x=3D   0.1   0.2          3.2    3.3         2.3    2.4
>=20
>  I am testing the transfer speed with Iperf. I run server of iperf to
> host_4,, and in host_1 run the client, my results is the next:
>=20
> On MPLS:
>=20
> [root@uni ~]# iperf -c 192.168.2.4 -F prova.rar -f M -t 30
> ------------------------------------------------------------
> Client connecting to 192.168.2.4, TCP port 5001
> TCP window size: 0.02 MByte (default)
> ------------------------------------------------------------
> [  4] local 192.168.0.1 port 32772 connected with 192.168.2.4 port 5001
> [  4]  0.0-30.0 sec  29.4 MBytes  0.98 MBytes/sec
>=20
>=20
> And I disable mpls, the results is:
> On IP:
>=20
> [root@uni ~]# iperf -c 192.168.2.4 -F prova.rar -f M -t 30
> ------------------------------------------------------------
> Client connecting to 192.168.2.4, TCP port 5001
> TCP window size: 0.02 MByte (default)
> ------------------------------------------------------------
> [  4] local 192.168.0.1 port 32780 connected with 192.168.2.4 port 5001
> [  4]  0.0- 8.0 sec  89.1 MBytes  11.1 MBytes/sec
>=20
>=20
>=20
> It is normal???? I think that on mpls the packets more speed that IP,
> because the forwading is realise on layer 2 (OSI).
> What is it???? Something explanation?
>=20
>=20
> thank you;;
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

[mpls-linux-general] Testing with Iperf

[Miquel C. P. <u10...@co...>]

Hello,,

I have the next structure and run under mpls perfectly,

prefix: 192.168.x.x

host_1(LER) <----> host_2(LSR) <----> host_3(LSR) <----> host_4 (LER)
on x.x=   0.1   0.2          3.2    3.3         2.3    2.4

 I am testing the transfer speed with Iperf. I run server of iperf to
host_4,, and in host_1 run the client, my results is the next:

On MPLS:

[root@uni ~]# iperf -c 192.168.2.4 -F prova.rar -f M -t 30
------------------------------------------------------------
Client connecting to 192.168.2.4, TCP port 5001
TCP window size: 0.02 MByte (default)
------------------------------------------------------------
[  4] local 192.168.0.1 port 32772 connected with 192.168.2.4 port 5001
[  4]  0.0-30.0 sec  29.4 MBytes  0.98 MBytes/sec


And I disable mpls, the results is:
On IP:

[root@uni ~]# iperf -c 192.168.2.4 -F prova.rar -f M -t 30
------------------------------------------------------------
Client connecting to 192.168.2.4, TCP port 5001
TCP window size: 0.02 MByte (default)
------------------------------------------------------------
[  4] local 192.168.0.1 port 32780 connected with 192.168.2.4 port 5001
[  4]  0.0- 8.0 sec  89.1 MBytes  11.1 MBytes/sec



It is normal???? I think that on mpls the packets more speed that IP,
because the forwading is realise on layer 2 (OSI).
What is it???? Something explanation?


thank you;;

[mpls-linux-general] LDP configuration example - help

[Razvan D. <raz...@gm...>]

hi,

i have managed to configure LDP on a set of mpls enabled linux
machines, but i don't quite know how to get it to work properly

i have the following simple topology

   ip network --- LER (11.0.1.1) -------- (11.0.1.2) LSR (11.0.2.1)
-------- (11.0.2.2) LSR (11.0.3.1) -------- (11.0.3.2) LER --- ip
network

i have configured zebra, ospf and ldpd; the routers do assign some
labels, but all communication is handled the old way (ip packets) (in
other words, the mpls command reveals the existence of ilm structures
only, no nhlfe or xc so there's no way to create an MPLS only
conversation)

i am using the following configuration files (for the first LSR)
(11.0.1.2--11.0.2.1)

zebra: (i know there's no need for a dummy interface, but i kept it)

hostname Router
password zebra
enable password zebra
service advanced-vty
!
mpls static 0
!
interface dummy0
 description yet another dummy interface=20
  ip address 192.168.0.3/32
  ipv6 nd suppress-ra
!
interface eth0
  description ldp-enabled interface=20
  mpls labelspace 0
  ip address 11.0.2.1/30
  ipv6 nd suppress-ra
!
interface eth1
  description ldp-enabled interface=20
  mpls labelspace 0
  ip address 11.0.1.2/30
  ipv6 nd suppress-ra
!
interface lo
  description Loopback=20
!
interface sit0
  ipv6 nd suppress-ra
!
ip forwarding
ipv6 forwarding
!
line vty
 exec-timeout 0 0
!

ldpd:

hostname ldpd
password test
enable password test
!
interface eth0
  description ldp enabled interface
  mpls ip
!
interface eth1
  description ldp enabled interface=20
  mpls ip
!
interface lo
  description Loopback interface=20
!
interface sit0
!
mpls ldp
 egress connected
!
line vty
 exec-timeout 0 0
!

i know that a labelspace is used only for ilm entries, but how do i
actually add a route that uses the mpls labels that are obtained using
ldpd?

the "ldpd# show ldp database" command shows "local binding" labels but also
"remote binding: no outlabel";

can anyone tell me what am i doing wrong (or what am i not doing
although i should)?

Razvan

Re: [mpls-linux-general] How much effort to implement RFC 2547bis?

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

On Thu, Jun 23, 2005 at 12:12:34PM -0400, jorma two wrote:
> I was wondering what would be needed to implement RFC 2547bis on the=20
> mpls-linux platform. The project page indicates that "quagga has support=
=20
> for distributing labeling information, but it has
> not been tied to mpls-linux yet". I was wondering

It is significant work, mostly on the quagga side.  Specifically
how to configure VRFs.  After that then each of the protocols
involved in PE-CE routing need to be able to run multiple instannces
each tied to a seperate VRF.

> 1. is this still the case?
> 2. What exactly is needed
> 3. Roughly, how much effort would this require (developer-days)?
> 4. Is there anything else which would prevent one from implementing=20
> RFC2547bis on mpls-linux, once the "tying to mpls-linux" is accomplished?
>=20
> Thanks much
>=20
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's FREE=
!=20
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] mplsadm2 and quagga

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

To create an NHFLE via quagga you need to either create it via
a 'ip route' command or via 'label-map <ilm> swap' command.

Since it doesn't make sense (from a quagga perspective) to create
a NHLFE without attaching it to something, there does not exist a
CLI command for just creating a NHLFE.

Example:

simian# conf t
simian(config)# mpls static 0
simian(config-ls)# label-map gen 1000 swap gen 2000 nexthop eth1 192.168.4.1
simian(config-ls)# end
simian# show mpls forwarding
Insegments:
  Lbl Spc  Label Owner
    0       1000 STATIC
Total 1

Outsegments:
  Interface          Label Next Hop        Owner
  eth1                2000 192.168.4.1     STATIC    (inactive)
Total 1

Cross Connects:
  Lbl Spc  In Label Out Label Interface        Next Hop        Owner
    0          1000      2000 eth1             192.168.4.1     STATIC    (i=
nactive)
Total 1

simian# conf t
simian(config)# ip route 10.0.0.0/8 gen 3000 nexthop eth1 192.168.4.1
simian(config)# end
simian# sho mpls forwarding
Insegments:

Total 0

Outsegments:
  Interface          Label Next Hop        Owner
  eth1                3000 192.168.4.1     BGP    (inactive)
Total 1

Cross Connects:

Total 0

simian# sho ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

S   0.0.0.0/0 [1/0] via 192.168.4.1, eth1
K>* 0.0.0.0/0 via 192.168.4.1, eth1
S>  10.0.0.0/8 [1/0] via 192.168.4.1, eth1 (label 3000)
C>* 127.0.0.0/8 is directly connected, lo
C>* 192.168.4.0/24 is directly connected, eth1

On Mon, Jul 25, 2005 at 10:34:31AM +0200, vittorio_manetti wrote:
> Hi to all,
> =20
> I'm working to find some difference between mplsadm2 and quagga. I would =
like to know if the the following sequence of instructions produce the same=
 result :
>=20
> 1)  eler(config)#mpls static 0
>     eler(config-ls)#label-map gen 17 pop
>  =20
> 2)  #mplsadm2 -A -I 0 -o pop:gen:17
>  =20
>  =20
> In every case, I would like to know if a quagga command equivalent to the=
 following mplsadm2 command exists :
>=20
>   #mplsadm2 -A -O 0 -o push:gen:16
>  =20
> Thanks.
>=20
>=20
>=20
> ____________________________________________________________
> 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!
> Scaricalo su INTERNET GRATIS 6X http://www.libero.it
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op?k
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] RV: tc and mpls

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

When using the iptables only config do you have a route in the ipv4
table that will satisfy the destination?

Remember you're using an OUTPUT rule.  The packet needs to make
it through the IPv4 stack before it gets to the iptables OUTPUT rules.
Therefore there needs to be a route that satisfies the destination.
It does not need to a MPLS modified route.

I think you're on the right path.  Try adding a route to the destination
and that should give you the results you want.

On Mon, Jul 25, 2005 at 02:05:31PM +0200, Jorge Garc?a wrote:
> Hello everybody,
>=20
> I am trying to create an Edge router which packets that ingress the MPLS
> network are enqueued before. Apparently the traffic engineering that I ha=
ve
> done works correctly without MPLS. ALL configurations are the following
>=20
> Traffic Engineering
>=20
> iptables -t mangle -A FORWARD -p icmp -j MARK --set-mark 1
> tc qdisc add dev eth1 root handle 1:0 htb default 12
> tc class add dev eth1 parent 1:0 classid 1:1 htb rate 512kbit ceil 512kbit
> tc class add dev eth1 parent 1:1 classid 1:10 htb rate 256kbit ceil 256kb=
it
> tc class add dev eth1 parent 1:1 classid 1:20 htb rate 256kbit ceil 256kb=
it
> tc filter add dev eth1 parent 1:0 prio 1 protocol ip handle 1 fw flowid 1=
:10
>=20
> I have trayed to introduce MPLS with iptables=20
>=20
> iptables -A OUTPUT -d 10.0.15.0/24 -j spec_nh --spec_nh 0x8847:0x2
>=20
> Where the nhlfe 0x2 is
>=20
> [root@localhost ~]# mpls nhlfe show
> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
> 	push gen 100 set eth1 ipv4 192.168.1.1  (24906644 bytes, 49177 pkts,
> 0 dropped)
>=20
> If this is the configuration the packets are marked and classified, but t=
he
> destination is unreachable.=20
>=20
> If I introduce a route where I specify the nhlfe 2, in this case:
> Ip route add 10.0.15.0/24 via 192.168.1.1 spec_nh 0x8847
>=20
> Packets are not classified now.
>=20
>=20
> How a I can classify packets in queues and send it with MPLS ?
>=20
>=20
> Thanks for your attention.
>=20
> Jorge Garcia
> La Salle
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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