mpls-linux-devel — Mailig list for discussing the development of MPLS on Linux

Re: [mpls-linux-devel] LDP query

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

Hello,

Basically MPLS LDP (quagga-mpls + ldp-portable) is only ready for
people who are willing to help debug.  So far I think there are three
people besides me who have had some level of success using it.  All of them
downloaded the code from my development tree and compiled it themselves.

Until I get more feed back from people about them being able to successfully
use MPLS LDP, I will not release a new version.

On Thu, Dec 14, 2006 at 09:09:45AM +0530, Neha Singh wrote:
> Hello,
>=20
> Thank you for your response.
>=20
> I also want to know if the user version of MPLS LDP is available just like
> the user version for the MPLS Forwarding Plane. If it is available please
> provide me the link for the same.
>=20
> Regards
>=20
> Neha Singh.
>=20
>=20
>=20
> On 12/13/06, James R. Leu <jl...@mi...> wrote:
> >
> >A quick search of the archives will show that the version of
> >LDP in the current quagga-mpls release is not designed for users (it
> >was a development release).
> >
> >If you are interested in work with LDP and are willing to help
> >in the debugging process, please download the lastest quagga-mpls from
> >my development tree (see http://mpls-linux.sf.net for more info)
> >
> >Make sure to search the archive before posting to the mailing list.
> >
> >On Wed, Dec 13, 2006 at 02:25:35PM +0530, Neha Singh wrote:
> >> Hello,
> >>
> >> We have downloaded and installed mpls (1.950) with all other utilities
> >give
> >> in the sourceforge site.
> >>
> >> The mpls forwarding engine works fine. we tested the same using "mpls"
> >> command suite provided in iproute2 for mpls 1.950.
> >>
> >> Now we are trying to atuomate this using  LDP
> >>
> >> When we start ldpd it runs as shown below :-
> >>
> >> quagga   11410 11319  0 13:39 pts/1    00:00:00 /usr/sbin/ldpd -f
> >> /etc/quagga/ldpd.conf
> >>
> >>
> >> when we give the following command:-
> >>
> >> VPLS22> en
> >> Password:
> >> VPLS22# con
> >> VPLS22# configure t
> >> VPLS22# configure terminal
> >> VPLS22(config)# mpl
> >> VPLS22(config)# mpls ld
> >> VPLS22(config)# mpls ldp
> >> VPLS22(config-ldp)#
> >>
> >>
> >> The LDPD daemon/process used to crash abruptly. Upon debugging we found
> >that
> >> "creation of ldp hello socket fails with bind error :  bind failed : :
> >> Permission denied".
> >>
> >>
> >> As you can see the user id with which the ldpd runs is quagga ...
> >>
> >>
> >> We had tried the old version of ldp which runs with root as userid . it
> >> starts with no problem and also exchanges the labels. but has problems
> >in
> >> communicating with kernel.
> >>
> >> Hence we downloaded the latest LDPD and mpls package (1.950) as given =
in
> >> sourceforge website.
> >>
> >> However when we run the ldpd it fails with the error stated above.
> >>
> >> Please suggest us what is to be done to over come this problem. and get
> >ldp
> >> going :-)
> >>
> >>
> >> Thank you
> >
> >>
> >-------------------------------------------------------------------------
> >> Take Surveys. Earn Cash. Influence the Future of IT
> >> Join SourceForge.net's Techsay panel and you'll get the chance to share
> >your
> >> opinions on IT & business topics through brief surveys - and earn cash
> >>
> >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> >> _______________________________________________
> >> mpls-linux-devel mailing list
> >> mpl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> >
> >
> >--
> >James R. Leu
> >jl...@mi...
> >
> >
> >

> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


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

Re: [mpls-linux-devel] LDP query

[Neha S. <neh...@gm...>]

Hello,

Thank you for your response.

I also want to know if the user version of MPLS LDP is available just like
the user version for the MPLS Forwarding Plane. If it is available please
provide me the link for the same.

Regards

Neha Singh.



On 12/13/06, James R. Leu <jl...@mi...> wrote:
>
> A quick search of the archives will show that the version of
> LDP in the current quagga-mpls release is not designed for users (it
> was a development release).
>
> If you are interested in work with LDP and are willing to help
> in the debugging process, please download the lastest quagga-mpls from
> my development tree (see http://mpls-linux.sf.net for more info)
>
> Make sure to search the archive before posting to the mailing list.
>
> On Wed, Dec 13, 2006 at 02:25:35PM +0530, Neha Singh wrote:
> > Hello,
> >
> > We have downloaded and installed mpls (1.950) with all other utilities
> give
> > in the sourceforge site.
> >
> > The mpls forwarding engine works fine. we tested the same using "mpls"
> > command suite provided in iproute2 for mpls 1.950.
> >
> > Now we are trying to atuomate this using  LDP
> >
> > When we start ldpd it runs as shown below :-
> >
> > quagga   11410 11319  0 13:39 pts/1    00:00:00 /usr/sbin/ldpd -f
> > /etc/quagga/ldpd.conf
> >
> >
> > when we give the following command:-
> >
> > VPLS22> en
> > Password:
> > VPLS22# con
> > VPLS22# configure t
> > VPLS22# configure terminal
> > VPLS22(config)# mpl
> > VPLS22(config)# mpls ld
> > VPLS22(config)# mpls ldp
> > VPLS22(config-ldp)#
> >
> >
> > The LDPD daemon/process used to crash abruptly. Upon debugging we found
> that
> > "creation of ldp hello socket fails with bind error :  bind failed : :
> > Permission denied".
> >
> >
> > As you can see the user id with which the ldpd runs is quagga ...
> >
> >
> > We had tried the old version of ldp which runs with root as userid . it
> > starts with no problem and also exchanges the labels. but has problems
> in
> > communicating with kernel.
> >
> > Hence we downloaded the latest LDPD and mpls package (1.950) as given in
> > sourceforge website.
> >
> > However when we run the ldpd it fails with the error stated above.
> >
> > Please suggest us what is to be done to over come this problem. and get
> ldp
> > going :-)
> >
> >
> > Thank you
>
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>
>
> --
> James R. Leu
> jl...@mi...
>
>
>

Re: [mpls-linux-devel] LDP query

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

A quick search of the archives will show that the version of
LDP in the current quagga-mpls release is not designed for users (it
was a development release).

If you are interested in work with LDP and are willing to help
in the debugging process, please download the lastest quagga-mpls from
my development tree (see http://mpls-linux.sf.net for more info)

Make sure to search the archive before posting to the mailing list.

On Wed, Dec 13, 2006 at 02:25:35PM +0530, Neha Singh wrote:
> Hello,
>=20
> We have downloaded and installed mpls (1.950) with all other utilities gi=
ve
> in the sourceforge site.
>=20
> The mpls forwarding engine works fine. we tested the same using "mpls"
> command suite provided in iproute2 for mpls 1.950.
>=20
> Now we are trying to atuomate this using  LDP
>=20
> When we start ldpd it runs as shown below :-
>=20
> quagga   11410 11319  0 13:39 pts/1    00:00:00 /usr/sbin/ldpd -f
> /etc/quagga/ldpd.conf
>=20
>=20
> when we give the following command:-
>=20
> VPLS22> en
> Password:
> VPLS22# con
> VPLS22# configure t
> VPLS22# configure terminal
> VPLS22(config)# mpl
> VPLS22(config)# mpls ld
> VPLS22(config)# mpls ldp
> VPLS22(config-ldp)#
>=20
>=20
> The LDPD daemon/process used to crash abruptly. Upon debugging we found t=
hat
> "creation of ldp hello socket fails with bind error :  bind failed : :
> Permission denied".
>=20
>=20
> As you can see the user id with which the ldpd runs is quagga ...
>=20
>=20
> We had tried the old version of ldp which runs with root as userid . it
> starts with no problem and also exchanges the labels. but has problems in
> communicating with kernel.
>=20
> Hence we downloaded the latest LDPD and mpls package (1.950) as given in
> sourceforge website.
>=20
> However when we run the ldpd it fails with the error stated above.
>=20
> Please suggest us what is to be done to over come this problem. and get l=
dp
> going :-)
>=20
>=20
> Thank you

> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


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

[mpls-linux-devel] LDP query

[Neha S. <neh...@gm...>]

Hello,

We have downloaded and installed mpls (1.950) with all other utilities give
in the sourceforge site.

The mpls forwarding engine works fine. we tested the same using "mpls"
command suite provided in iproute2 for mpls 1.950.

Now we are trying to atuomate this using  LDP

When we start ldpd it runs as shown below :-

quagga   11410 11319  0 13:39 pts/1    00:00:00 /usr/sbin/ldpd -f
/etc/quagga/ldpd.conf


when we give the following command:-

VPLS22> en
Password:
VPLS22# con
VPLS22# configure t
VPLS22# configure terminal
VPLS22(config)# mpl
VPLS22(config)# mpls ld
VPLS22(config)# mpls ldp
VPLS22(config-ldp)#


The LDPD daemon/process used to crash abruptly. Upon debugging we found that
"creation of ldp hello socket fails with bind error :  bind failed : :
Permission denied".


As you can see the user id with which the ldpd runs is quagga ...


We had tried the old version of ldp which runs with root as userid . it
starts with no problem and also exchanges the labels. but has problems in
communicating with kernel.

Hence we downloaded the latest LDPD and mpls package (1.950) as given in
sourceforge website.

However when we run the ldpd it fails with the error stated above.

Please suggest us what is to be done to over come this problem. and get ldp
going :-)


Thank you

Re: [mpls-linux-devel] LDP Configuation

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

Hello,

You'll have to fogive me, I do not remember what problem we're
working on.  Please provide a ascii drawing or your network,
your full quagga config (from vtysh), and the output of:

    sh ip route
    sho ldp
    show ldp discovery
    show ldp neigh
    show ldp data
    show mpls forward

All from vtysh.  In addition do a:

    ip route show
    mpls labelspace show
    mpls ilm show
    mpls nhlfe show

from the command line.

On Mon, Dec 04, 2006 at 05:41:18PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi once again:
>=20
> >From your Perforce's repository I downloaded glibc-kernheaders-mpls and =
built the .rpm to install it:
>=20
>         [root@l12p07 ~]# rpm -q glibc-kernheaders
>         glibc-kernheaders-3.0-5.2_mpls0.1162999872
>=20
> I have checked the file mpls.h in /usr/include/linux and /usr/src/kernels=
/2.6.15-1.1831_FC4mpls_1.950-i686/include/linux before compiling quagga-mpl=
s with ldp-portable, and it's the same as the file in glibc-kernheaders-mpl=
s.
>=20
> I have also looked into the configure.ac file in quagga-mpls to make sure=
 that the link to mpls.h was correct and it seems to be ok.
>=20
>       if grep MPLS_LINUX_VERSION /usr/include/linux/mpls.h >/dev/null 2>&=
1; then
>       AC_DEFINE(HAVE_MPLS,1,Enable MPLS)
>       AC_DEFINE(LINUX_MPLS,1,Linux MPLS)
>       MPLS_METHOD=3D"mpls_netlink.o"
>       AC_MSG_RESULT(MPLS Linux)
>=20
> Besides, I'm able to test static MPLS (without quagga) creating LSPs and =
TUNNELS succesfully even in the computer I use to build quagga.
>=20
> I don't know where to look at, any help would be very useful,
> thanks for your time,
>=20
> Gonzalo



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

Re: [mpls-linux-devel] LDP Configuation

[<gsr...@al...>]

Hi once again:

>From your Perforce's repository I downloaded glibc-kernheaders-mpls and =
built the .rpm to install it:

        [root@l12p07 ~]# rpm -q glibc-kernheaders
        glibc-kernheaders-3.0-5.2_mpls0.1162999872

I have checked the file mpls.h in /usr/include/linux and =
/usr/src/kernels/2.6.15-1.1831_FC4mpls_1.950-i686/include/linux before =
compiling quagga-mpls with ldp-portable, and it's the same as the file =
in glibc-kernheaders-mpls.

I have also looked into the configure.ac file in quagga-mpls to make =
sure that the link to mpls.h was correct and it seems to be ok.

      if grep MPLS_LINUX_VERSION /usr/include/linux/mpls.h >/dev/null =
2>&1; then
      AC_DEFINE(HAVE_MPLS,1,Enable MPLS)
      AC_DEFINE(LINUX_MPLS,1,Linux MPLS)
      MPLS_METHOD=3D"mpls_netlink.o"
      AC_MSG_RESULT(MPLS Linux)

Besides, I'm able to test static MPLS (without quagga) creating LSPs and =
TUNNELS succesfully even in the computer I use to build quagga.

I don't know where to look at, any help would be very useful,
thanks for your time,

Gonzalo

Re: [mpls-linux-devel] LDP Configuation

[<gsr...@al...>]

Hi, again:

This is the scenario I use:


      13.0.0.0/24   .1   .1             .2   .1   11.0.0.0/24
               -------PE1-----------------PE2-------
                  eth2   eth1         eth0   eth1
                            10.0.0.0/24  =20

I've compiled the latest quagga-mpls and ldp-portable from your =
repository:
      =20
        [root@l12p07 ~]# rpm -qa | grep quagga
        quagga-contrib-0.99.5-2006120101_mpls_0.1164964523
        quagga-0.99.5-2006120101_mpls_0.1164964523
        quagga-debuginfo-0.99.5-2006120101_mpls_0.1164964523
        quagga-devel-0.99.5-2006120101_mpls_0.1164964523

I tried what you suggested and this is what happens (on PE2), after =
launching zebra, ospfd and ldpd:


        [root@l12p07 Scripts_Ord2]# vtysh

        Hello, this is Quagga (version 0.99.5).
        Copyright 1996-2005 Kunihiro Ishiguro, et al.

        PE2# con t
        PE2(config)# mpls static 0
        PE2(config-ls)# label-map gen 160 swap gen 170 nexthop eth1 =
10.0.0.1
        Warning: closing connection to zebra because of an I/O error!
        PE2(config-ls)#

This is what dmesg prints at this time:

[root@l12p07 ~]# dmesg | grep mpls
Linux version 2.6.15-1.1831_FC4mpls_1.950 (root@localhost.localdomain) =
(gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 Fri Oct 13 17:52:43 =
CEST 2006
MPLS DEBUG net/mpls/mpls_sysfs.c:130:mpls_sysfs_init: enter
MPLS DEBUG net/mpls/mpls_sysfs.c:139:mpls_sysfs_init: exit
MPLS DEBUG net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit

Then I tried with another ip address that doesn't belong to the =
scenario:

Hello, this is Quagga (version 0.99.5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

PE2# con t
PE2(config)# mpls static 0
PE2(config-ls)# label-map gen 160 swap gen 170 nexthop eth1 172.29.17.60
PE2(config-ls)# end
PE2# show mpls forwarding
Insegments:
  Lbl Spc  Label Owner
    0        160 static
Total 1

Outsegments:
  Interface          Label Next Hop        Owner
  eth1                 170 172.29.17.60    static (inactive)
Total 1

Cross Connects:
  Lbl Spc  In Label Out Label Interface        Next Hop        Owner
    0           160       170 eth1             172.29.17.60    static =
(inactive)Total 1

PE2#

But the output of dmesg is always the same, although MPLS debug is =
running. This lines are the same that appear as I boot the system and =
load mpls4 and mpls modules. Furthermore, at any time NHLFEs and ILMs =
are empty:

[root@l12p07 Scripts_Ord2]# dmesg | grep mpls
Linux version 2.6.15-1.1831_FC4mpls_1.950 (root@localhost.localdomain) =
(gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 Fri Oct 13 17:52:43 =
CEST 2006
MPLS DEBUG net/mpls/mpls_sysfs.c:130:mpls_sysfs_init: enter
MPLS DEBUG net/mpls/mpls_sysfs.c:139:mpls_sysfs_init: exit
MPLS DEBUG net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit

I expect your answer.
Thanks in advance,

Gonzalo

Re: [mpls-linux-devel] LDP Configuation

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

It looks like you've got a working MPLS kernel.  Try building a LSP
via the quagga interface, in vtysh try:

monkey1(config)# mpls static 0
monkey1(config-ls)# label-map gen 160 swap gen 170 nexthop eth2 192.168.4.2
monkey1(config-ls)# end
monkey1# show mpls forwarding
Insegments:
  Lbl Spc  Label Owner
    0        160 static (inactive)
Total 1

Outsegments:
  Interface          Label Next Hop        Owner
  eth2                 170 192.168.4.2     static (inactive)
Total 1

Cross Connects:
  Lbl Spc  In Label Out Label Interface        Next Hop        Owner
    0           160       170 eth2             192.168.4.2     static (inac=
tive)Total 1

monkey1#


Make sure you're seeing the MPLS debug in 'dmesg'

BTW your should update your quagga-mpls and ldp-portable tree, I have submi=
tted
lots of changes since you built your RPM.

On Mon, Nov 27, 2006 at 10:56:37AM +0100, Sienes Rodr?guez Gonzalo wrote:
>=20
> Hi, James:
>=20
> This is what I get with "dmesg" related to mpls as soon as system boots. I
> have also loaded the "mpls4" module that at the same time loads "mpls"
> module:
>=20
> [root@PE1 ~]# lsmod | grep mpls
> mpls4                   6081  0
> mpls                   78465  2 mpls4
>=20
> Linux version 2.6.15-1.1831_FC4mpls_1.950 (jleu@jleu-laptop) (gcc version
> 4.0.2 20051125 (Red Hat 4.0.2-8)) #1 Sun Feb 26 15:00:23 CST 2006
>=20
> MPLS: version 1.950
> MPLS: protocol driver interface - <jl...@mi...>
> MPLS DEBUG net/mpls/mpls_sysfs.c:130:mpls_sysfs_init: enter MPLS DEBUG
> net/mpls/mpls_sysfs.c:139:mpls_sysfs_init: exit
> MPLS: IPv4 over MPLS support
> MPLS DEBUG net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter MPLS DEBUG
> net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit
>=20
> These are the new lines output by dmesg when I type:
>=20
> [root@PE1 ~]# mpls ilm show
> [root@PE1 ~]# mpls nhlfe show
>=20
> MPLS DEBUG net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry 0
> MPLS DEBUG net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 0
> MPLS DEBUG net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: entry=
 0
> MPLS DEBUG net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry 0
>=20
> The next I tried was to create a NHLFE entry and an ILM entry:
>=20
> [root@PE1 ~]# mpls nhlfe add key 0
> NHLFE entry key 0x00000002 mtu 0 propagate_ttl
>          (0 bytes, 0 pkts)
>=20
> [root@PE1 ~]# mpls ilm add label gen 100 labelspace 0
>=20
> [root@PE1 ~]# mpls nhlfe show
> NHLFE entry key 0x00000002 mtu 0 propagate_ttl
>          (0 bytes, 0 pkts)
>=20
> [root@PE1 ~]# mpls ilm show
> ILM entry label gen 100 labelspace 0 proto ipv4
>         pop peek  (0 bytes, 0 pkts)
>=20
> ...and their respective lines in dmesg output:
>=20
> MPLS DEBUG net/mpls/mpls_netlink.c:298:genl_mpls_nhlfe_new: enter MPLS DE=
BUG
> net/mpls/mpls_nhlfe.c:394:mpls_add_out_label: enter MPLS DEBUG
> net/mpls/mpls_nhlfe.c:130:nhlfe_dst_alloc: enter MPLS DEBUG
> net/mpls/mpls_nhlfe.c:151:nhlfe_dst_alloc: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:275:mpls_nhlfe_event: enter MPLS DEBUG
> net/mpls/mpls_netlink.c:235:mpls_fill_nhlfe: enter MPLS DEBUG
> net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
> net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:259:mpls_fill_nhlfe: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:289:mpls_nhlfe_event: exit MPLS DEBUG
> net/mpls/mpls_nhlfe.c:451:mpls_add_out_label: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:335:genl_mpls_nhlfe_new: Exit: 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:115:genl_mpls_ilm_new: enter MPLS DEBUG
> net/mpls/mpls_ilm.c:522:mpls_add_in_label: enter MPLS DEBUG
> net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter MPLS DEBUG
> net/mpls/mpls_ilm.c:109:ilm_dst_gc: enter MPLS DEBUG
> net/mpls/mpls_ilm.c:110:ilm_dst_gc: exit MPLS DEBUG
> net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:91:mpls_ilm_event: enter MPLS DEBUG
> net/mpls/mpls_netlink.c:53:mpls_fill_ilm: enter MPLS DEBUG
> net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
> net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:76:mpls_fill_ilm: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:106:mpls_ilm_event: exit MPLS DEBUG
> net/mpls/mpls_ilm.c:582:mpls_add_in_label: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:145:genl_mpls_ilm_new: Exit: 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: entry 0 MPLS DEB=
UG
> net/mpls/mpls_netlink.c:397:genl_mpls_nhlfe_dump: Dump: entry 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:235:mpls_fill_nhlfe: enter MPLS DEBUG
> net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
> net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:259:mpls_fill_nhlfe: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry 1 MPLS DEBUG
> net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: entry 1 MPLS DEB=
UG
> net/mpls/mpls_netlink.c:397:genl_mpls_nhlfe_dump: Dump: entry 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry 1 MPLS DEBUG
> net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:207:genl_mpls_ilm_dump: Dump: entry 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:53:mpls_fill_ilm: enter MPLS DEBUG
> net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
> net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:76:mpls_fill_ilm: exit MPLS DEBUG
> net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 1 MPLS DEBUG
> net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry 1 MPLS DEBUG
> net/mpls/mpls_netlink.c:207:genl_mpls_ilm_dump: Dump: entry 0 MPLS DEBUG
> net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 1
>=20
> I hope you'll have a look at it and you could tell me something about.
>=20
> If it helps here are the RPMs installed related to MPLS:
>=20
> [root@l12p07 ~]# rpm -qa | grep mpls iproute-2.6.11-1_mpls_90.1162552079
>                                      //In this version of iproute I have
>                                      //only modified the usage of
>                                      //mpls_tunnel command
> iptables-1.3.0-2_mpls_1.950d
> kernel-2.6.15-1.1831_FC4mpls_1.950
> glibc-kernheaders-3.0-5.2_mpls0.1162999872
> quagga-0.99.4-2006111701_mpls_0.1163780539
> quagga-contrib-0.99.4-2006111701_mpls_0.1163780539
> quagga-debuginfo-0.99.4-2006111701_mpls_0.1163780539
> quagga-devel-0.99.4-2006111701_mpls_0.1163780539
> kernel-devel-2.6.15-1.1831_FC4mpls_1.950
>=20
>=20
> Thanks for your time,
> regards:
>=20
> Gonzalo
>=20



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

[mpls-linux-devel] Dynamic LSP configuration

[Julien B. <jul...@gm...>]

Hi,

As I read this post :
http://sourceforge.net/mailarchive/forum.php?thread_id=31043747&forum_id=36583I
notice that I may help.
I am currently a student in computer science and the topic of my master
thesis is "more or less" the dynamic LSP configuration. I read the
ldp-portable FAQ file which says :

Does ldp-portable support CR-LDP?
---------------------------------
Short answer no.  Long answer is that the underlying packet encode/decode
for CR-LDP related TLVs is there and the 'MIB' like interface for
creating the TE related config is there but the upper layers do not use
them.
=======================================================

I don't what the status of this part of the code but I'm available (not at
full time) to help (testing / releasing / maybe coding / whatever you need).

As I downloaded the whole repository from perforce (2.4 GB, so painful) and
I don't even know what is the difference between all the versions of quagga
or even which one I need to dynamically create/modify/re-route LSPs!! If I
need to code something for CR-LDP, you would be so kind to let me know where
can I start ??  I read a little the developer's guide (
http://perso.enst.fr/~casellas/mpls-linux/index.html<http://perso.enst.fr/%7Ecasellas/mpls-linux/index.html>)
and it doesn't say much about LDP.

By the way, I managed to install every programs contained in the tarballs
(ebtables, iproute2, iptables, quagga 0.96.4) with a kernel 2.6.15.7.
I have to install and test everything on a testbed but it is unavailable
right now. Meanwhile,  I use Netkit (base on user-mode-linux) to test a
create a virtual testbed and test everything.

Let me know if I can do something.

Julien

-- 
--------------------------------------------
Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be>
M.Sc. student in Computer Science, University of Namur
FUNDP, Belgium
Traineeship

Re: [mpls-linux-devel] LDP Configuation

[<gsr...@al...>]

Hi, James:

This is what I get with "dmesg" related to mpls as soon as system boots. =
I
have also loaded the "mpls4" module that at the same time loads "mpls"
module:

[root@PE1 ~]# lsmod | grep mpls
mpls4                   6081  0
mpls                   78465  2 mpls4

Linux version 2.6.15-1.1831_FC4mpls_1.950 (jleu@jleu-laptop) (gcc =
version
4.0.2 20051125 (Red Hat 4.0.2-8)) #1 Sun Feb 26 15:00:23 CST 2006

MPLS: version 1.950
MPLS: protocol driver interface - <jl...@mi...>
MPLS DEBUG net/mpls/mpls_sysfs.c:130:mpls_sysfs_init: enter MPLS DEBUG
net/mpls/mpls_sysfs.c:139:mpls_sysfs_init: exit
MPLS: IPv4 over MPLS support
MPLS DEBUG net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter MPLS DEBUG
net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit

These are the new lines output by dmesg when I type:

[root@PE1 ~]# mpls ilm show
[root@PE1 ~]# mpls nhlfe show

MPLS DEBUG net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry =
0
MPLS DEBUG net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 0
MPLS DEBUG net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: =
entry 0
MPLS DEBUG net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry =
0

The next I tried was to create a NHLFE entry and an ILM entry:

[root@PE1 ~]# mpls nhlfe add key 0
NHLFE entry key 0x00000002 mtu 0 propagate_ttl
         (0 bytes, 0 pkts)

[root@PE1 ~]# mpls ilm add label gen 100 labelspace 0

[root@PE1 ~]# mpls nhlfe show
NHLFE entry key 0x00000002 mtu 0 propagate_ttl
         (0 bytes, 0 pkts)

[root@PE1 ~]# mpls ilm show
ILM entry label gen 100 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts)

...and their respective lines in dmesg output:

MPLS DEBUG net/mpls/mpls_netlink.c:298:genl_mpls_nhlfe_new: enter MPLS =
DEBUG
net/mpls/mpls_nhlfe.c:394:mpls_add_out_label: enter MPLS DEBUG
net/mpls/mpls_nhlfe.c:130:nhlfe_dst_alloc: enter MPLS DEBUG
net/mpls/mpls_nhlfe.c:151:nhlfe_dst_alloc: exit MPLS DEBUG
net/mpls/mpls_netlink.c:275:mpls_nhlfe_event: enter MPLS DEBUG
net/mpls/mpls_netlink.c:235:mpls_fill_nhlfe: enter MPLS DEBUG
net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
net/mpls/mpls_netlink.c:259:mpls_fill_nhlfe: exit MPLS DEBUG
net/mpls/mpls_netlink.c:289:mpls_nhlfe_event: exit MPLS DEBUG
net/mpls/mpls_nhlfe.c:451:mpls_add_out_label: exit MPLS DEBUG
net/mpls/mpls_netlink.c:335:genl_mpls_nhlfe_new: Exit: 0 MPLS DEBUG
net/mpls/mpls_netlink.c:115:genl_mpls_ilm_new: enter MPLS DEBUG
net/mpls/mpls_ilm.c:522:mpls_add_in_label: enter MPLS DEBUG
net/mpls/mpls_ilm.c:126:mpls_ilm_dst_alloc: enter MPLS DEBUG
net/mpls/mpls_ilm.c:109:ilm_dst_gc: enter MPLS DEBUG
net/mpls/mpls_ilm.c:110:ilm_dst_gc: exit MPLS DEBUG
net/mpls/mpls_ilm.c:156:mpls_ilm_dst_alloc: exit MPLS DEBUG
net/mpls/mpls_netlink.c:91:mpls_ilm_event: enter MPLS DEBUG
net/mpls/mpls_netlink.c:53:mpls_fill_ilm: enter MPLS DEBUG
net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
net/mpls/mpls_netlink.c:76:mpls_fill_ilm: exit MPLS DEBUG
net/mpls/mpls_netlink.c:106:mpls_ilm_event: exit MPLS DEBUG
net/mpls/mpls_ilm.c:582:mpls_add_in_label: exit MPLS DEBUG
net/mpls/mpls_netlink.c:145:genl_mpls_ilm_new: Exit: 0 MPLS DEBUG
net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: entry 0 MPLS =
DEBUG
net/mpls/mpls_netlink.c:397:genl_mpls_nhlfe_dump: Dump: entry 0 MPLS =
DEBUG
net/mpls/mpls_netlink.c:235:mpls_fill_nhlfe: enter MPLS DEBUG
net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
net/mpls/mpls_netlink.c:259:mpls_fill_nhlfe: exit MPLS DEBUG
net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry 1 MPLS =
DEBUG
net/mpls/mpls_netlink.c:394:genl_mpls_nhlfe_dump: Enter: entry 1 MPLS =
DEBUG
net/mpls/mpls_netlink.c:397:genl_mpls_nhlfe_dump: Dump: entry 0 MPLS =
DEBUG
net/mpls/mpls_netlink.c:411:genl_mpls_nhlfe_dump: Exit: entry 1 MPLS =
DEBUG
net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry 0 MPLS =
DEBUG
net/mpls/mpls_netlink.c:207:genl_mpls_ilm_dump: Dump: entry 0 MPLS DEBUG
net/mpls/mpls_netlink.c:53:mpls_fill_ilm: enter MPLS DEBUG
net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter MPLS DEBUG
net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit MPLS DEBUG
net/mpls/mpls_netlink.c:76:mpls_fill_ilm: exit MPLS DEBUG
net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 1 MPLS DEBUG
net/mpls/mpls_netlink.c:204:genl_mpls_ilm_dump: Enter: entry 1 MPLS =
DEBUG
net/mpls/mpls_netlink.c:207:genl_mpls_ilm_dump: Dump: entry 0 MPLS DEBUG
net/mpls/mpls_netlink.c:221:genl_mpls_ilm_dump: Exit: entry 1

I hope you'll have a look at it and you could tell me something about.

If it helps here are the RPMs installed related to MPLS:

[root@l12p07 ~]# rpm -qa | grep mpls iproute-2.6.11-1_mpls_90.1162552079
                                     //In this version of iproute I have
                                     //only modified the usage of
                                     //mpls_tunnel command
iptables-1.3.0-2_mpls_1.950d
kernel-2.6.15-1.1831_FC4mpls_1.950
glibc-kernheaders-3.0-5.2_mpls0.1162999872
quagga-0.99.4-2006111701_mpls_0.1163780539
quagga-contrib-0.99.4-2006111701_mpls_0.1163780539
quagga-debuginfo-0.99.4-2006111701_mpls_0.1163780539
quagga-devel-0.99.4-2006111701_mpls_0.1163780539
kernel-devel-2.6.15-1.1831_FC4mpls_1.950


Thanks for your time,
regards:

Gonzalo

Re: [mpls-linux-devel] LDP Configuation

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

It looks like something is wrong with the communications with the
kernel.

=46rom the command line can you try creating and deleting ILM and NHLFE
then show me the results of a:

mpls ilm show
mpls nhlfe show
dmesg | grep -i MPLS

On Thu, Nov 23, 2006 at 06:59:23PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi!
>=20
> Thanks for your information.
>=20
> >Make sure you have the mpls4 module loaded into the kernel
> >otherwise all attempts by LDP to install a ILM or NHLFE will fail, causi=
ng
> >the LDP sessions to fail.
>=20
> I have this module loaded into the kernel ever since system boots. I deci=
ded to make the file "mpls.modules" to have mpls4, mpls and mpls_tunnel alw=
ays loaded to perform LSPs and tunnels experiments.=20
>=20
> >You can also check what is happening at the kernel level by looking
> >at the output of 'dmesg'.  It will probably show all sorts of MPLS relat=
ed
> >debug.
>=20
> When I type "dmesg" this is the output:
>=20
> MPLS DEBUG net/mpls/mpls_tunnel.c:279:mpls_tunnel_ioctl: enter
> MPLS DEBUG net/mpls/mpls_tunnel.c:298:mpls_tunnel_ioctl: enter
>=20
> This two lines repeated lots of times, nothing else related to MPLS.
> In those mpls_tunnel.c lines there're calls to MPLS_ENTER, that is define=
d in mpls.h as follows: #define MPLS_ENTER MPLS_DEBUG("enter\n"). Anyway, I=
 suppose this module (I mean mpls_tunnel) has nothing to do with the config=
 I tried for LDPD to open only simple LSPs.
>=20
> >Finally, after a failed attempt by LDP, make sure you manually clean
> >up the ILMs and NHLFEs.
>=20
> I've tested ILMs and NHLFEs before and after running ZEBRA, OSPFD and LDP=
D and typing the additional commands by vtysh, and they kept empty.
>=20
> So, do you know where I could look at, any clue...?
>=20
> Thanks in advance,
>=20
> Gonzalo.
>=20



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

Re: [mpls-linux-devel] LDP Configuation

[<gsr...@al...>]

Hi!

Thanks for your information.

>Make sure you have the mpls4 module loaded into the kernel
>otherwise all attempts by LDP to install a ILM or NHLFE will fail, =
causing
>the LDP sessions to fail.

I have this module loaded into the kernel ever since system boots. I =
decided to make the file "mpls.modules" to have mpls4, mpls and =
mpls_tunnel always loaded to perform LSPs and tunnels experiments.=20

>You can also check what is happening at the kernel level by looking
>at the output of 'dmesg'.  It will probably show all sorts of MPLS =
related
>debug.

When I type "dmesg" this is the output:

MPLS DEBUG net/mpls/mpls_tunnel.c:279:mpls_tunnel_ioctl: enter
MPLS DEBUG net/mpls/mpls_tunnel.c:298:mpls_tunnel_ioctl: enter

This two lines repeated lots of times, nothing else related to MPLS.
In those mpls_tunnel.c lines there're calls to MPLS_ENTER, that is =
defined in mpls.h as follows: #define MPLS_ENTER MPLS_DEBUG("enter\n"). =
Anyway, I suppose this module (I mean mpls_tunnel) has nothing to do =
with the config I tried for LDPD to open only simple LSPs.

>Finally, after a failed attempt by LDP, make sure you manually clean
>up the ILMs and NHLFEs.

I've tested ILMs and NHLFEs before and after running ZEBRA, OSPFD and =
LDPD and typing the additional commands by vtysh, and they kept empty.

So, do you know where I could look at, any clue...?

Thanks in advance,

Gonzalo.

Re: [mpls-linux-devel] LDP Configuation

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

Make sure you have the mpls4 module loaded into the kernel
otherwise all attempts by LDP to install a ILM or NHLFE will fail, causing
the LDP sessions to fail.

You can also check what is happening at the kernel level by looking
at the output of 'dmesg'.  It will probably show all sorts of MPLS related
debug.

Finally, after a failed attempt by LDP, make sure you manually clean
up the ILMs and NHLFEs.

On Wed, Nov 22, 2006 at 03:18:59PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi!
>=20
> Thanks for your information.
>=20
> I decided to test the new configuration in the following scenario, only w=
ith
> two routers to realized what LDP really does. =20
>=20
>       13.0.0.0/24   .1   .1             .2   .1   14.0.0.0/24
>                -------PE1-----------------PE3-------
>                   eth2   eth1         eth0   eth2
>                             12.0.0.0/24  =20
>=20
> These are the .conf files I use for PE1:
>=20
> ZEBRA
> ------------------------------------------------------------------
> !
> hostname PE1
> password root
> log file /var/log/quagga/zebra.log
> debug zebra events
> debug zebra kernel
> !
> !
> interface lo
> !
> !
> interface eth1
> !
> interface eth2
> !
> !
>=20
> OSPFD
> ------------------------------------------------------------------
> !
> hostname PE1
> password root
> log file /var/log/quagga/ospfd.log
> !
> !
> !
> interface eth1
>  description 12.0.0.1 netmask 255.255.255.0 broadcast 12.0.0.255 ! interf=
ace
> eth2  description 13.0.0.1 netmask 255.255.255.0 broadcast 13.0.0.255 !
> interface lo ! router ospf  ospf router-id 0.0.0.1  network 12.0.0.0/24 a=
rea
> 0  network 13.0.0.0/24 area 0 ! line vty !
>=20
> LDPD
> ------------------------------------------------------------------
> !
> hostname PE1
> password root
> log file /var/log/quagga/ldpd.log
> !
> interface eth1
>  mpls ip
> !
> interface eth2
> !
> interface lo
> !
> !
> line vty
> !
>=20
> VTYSH
> ------------------------------------------------------------------
> !
> service integrated-vtysh-config
> hostname PE1
> !
>=20
> As you suggested, after running all those daemons (zebra -d, ospfd -d,
> ldpd-d) I type "vtysh" to finally set the proper LDPD commands: "mpls ldp=
",
> and in each interface of 12.0.0.0/24 subnet, "mpls ip" and "mpls labelspa=
ce
> 0".
>=20
> I got some problems with mpls labelspace, cause sometimes when I type the
> command occurs an I/O error and the daemon zebra is killed. In the end, w=
hen
> it works, I capture the traffic and this is what happens:
>=20
> 1.Both PEs pass the stage of discovering with HELLO messages.
>=20
> 2.I can see INITIALIZATION messages in both ways, but the ones from 12.2 =
to
> 12.1 have a TCP checksum error. However, the LDP message seems to be
> correct. With correct LSRs identifiers and these session parameters:
>=20
>         -Downstream unsolicited mode.
>         -Loop detection disabled.
>         -MPLS labelspace 0.
>=20
> 3.The KEEPALIVEs in the way PE1 also travel with checksum error as well as
> all types of LDP messages but HELLOs. The ADDRESS messages are set with t=
he
> correct values of neighbor address.
>=20
> 4.The LABEL MAPPING messages carry the value of a label inside, which is =
the
> same for both ways, 10000.
>=20
> 5.The problem is that after distributing the labels, 12.1 sends to 12.2 a
> NOTIFICATION message with the status: fatal error, session rejected and t=
hen
> the process starts again, now exchanging different values of labels (alwa=
ys
> the same in both ways) 10001, 10002 and so on.
>=20
> This is what I get in PE1 and the same in PE2 with other addresses:
>=20
> PE1# sh ldp neig
> Peer LDP Ident: 14.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>         TCP connection: 0.0.0.0.646 - 12.0.0.2.45099
>         State: OPERATIONAL; Msgs sent/recv: 489/1459; UNSOLICITED
>         Up time: 02:00:24
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           12.0.0.2        14.0.0.1
>=20
> I try to do: ping -c3 14.0.0.1 from PE1, but the ICMP packets don't carry
> any LDP label. Besides, MPLS NHLFE and MPLS ILM tables are empty.
>=20
> Is this the expected behavior?
>=20
> Thanks in advance,
>=20
> Gonzalo
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

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

Re: [mpls-linux-devel] LDP Configuation

[<gsr...@al...>]

Hi!

Thanks for your information.

I decided to test the new configuration in the following scenario, only =
with
two routers to realized what LDP really does. =20

      13.0.0.0/24   .1   .1             .2   .1   14.0.0.0/24
               -------PE1-----------------PE3-------
                  eth2   eth1         eth0   eth2
                            12.0.0.0/24  =20

These are the .conf files I use for PE1:

ZEBRA
------------------------------------------------------------------
!
hostname PE1
password root
log file /var/log/quagga/zebra.log
debug zebra events
debug zebra kernel
!
!
interface lo
!
!
interface eth1
!
interface eth2
!
!

OSPFD
------------------------------------------------------------------
!
hostname PE1
password root
log file /var/log/quagga/ospfd.log
!
!
!
interface eth1
 description 12.0.0.1 netmask 255.255.255.0 broadcast 12.0.0.255 ! =
interface
eth2  description 13.0.0.1 netmask 255.255.255.0 broadcast 13.0.0.255 !
interface lo ! router ospf  ospf router-id 0.0.0.1  network 12.0.0.0/24 =
area
0  network 13.0.0.0/24 area 0 ! line vty !

LDPD
------------------------------------------------------------------
!
hostname PE1
password root
log file /var/log/quagga/ldpd.log
!
interface eth1
 mpls ip
!
interface eth2
!
interface lo
!
!
line vty
!

VTYSH
------------------------------------------------------------------
!
service integrated-vtysh-config
hostname PE1
!

As you suggested, after running all those daemons (zebra -d, ospfd -d,
ldpd-d) I type "vtysh" to finally set the proper LDPD commands: "mpls =
ldp",
and in each interface of 12.0.0.0/24 subnet, "mpls ip" and "mpls =
labelspace
0".

I got some problems with mpls labelspace, cause sometimes when I type =
the
command occurs an I/O error and the daemon zebra is killed. In the end, =
when
it works, I capture the traffic and this is what happens:

1.Both PEs pass the stage of discovering with HELLO messages.

2.I can see INITIALIZATION messages in both ways, but the ones from 12.2 =
to
12.1 have a TCP checksum error. However, the LDP message seems to be
correct. With correct LSRs identifiers and these session parameters:

        -Downstream unsolicited mode.
        -Loop detection disabled.
        -MPLS labelspace 0.

3.The KEEPALIVEs in the way PE1 also travel with checksum error as well =
as
all types of LDP messages but HELLOs. The ADDRESS messages are set with =
the
correct values of neighbor address.

4.The LABEL MAPPING messages carry the value of a label inside, which is =
the
same for both ways, 10000.

5.The problem is that after distributing the labels, 12.1 sends to 12.2 =
a
NOTIFICATION message with the status: fatal error, session rejected and =
then
the process starts again, now exchanging different values of labels =
(always
the same in both ways) 10001, 10002 and so on.

This is what I get in PE1 and the same in PE2 with other addresses:

PE1# sh ldp neig
Peer LDP Ident: 14.0.0.1:0; Local LDP Ident: 13.0.0.1:0
        TCP connection: 0.0.0.0.646 - 12.0.0.2.45099
        State: OPERATIONAL; Msgs sent/recv: 489/1459; UNSOLICITED
        Up time: 02:00:24
        LDP discovery sources:
          eth1
        Addresses bound to peer:
          12.0.0.2        14.0.0.1

I try to do: ping -c3 14.0.0.1 from PE1, but the ICMP packets don't =
carry
any LDP label. Besides, MPLS NHLFE and MPLS ILM tables are empty.

Is this the expected behavior?

Thanks in advance,

Gonzalo

Re: [mpls-linux-devel] LDPD configuration

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

First, my testing/bug fixing has only been for LDP operating in:
- Downstream Unsolicited
- Order control mode
- Liberal label retention

The above configuration is the default config, therefor there is
no need to issue any command under 'mpls ldp' or 'mpls ip'.  If you do
decide to test out the various configuration options below 'mpls ldp' and
'mpls ip' please send me bug reports ... or success reports :-)

As far as why your sessions will not establish.  To start off, you should
be using vtysh instead of connecting to each daemon independently.  Once
inside vtysh, you can configure all of the protocols.  Here is what I do:

monkey2# conf t
monkey2(config)# mpls ldp
monkey2(config-ldp)# exit
monkey2(config)# int eth1
monkey2(config-if)# mpls labelspace 0
Labelspace: 0
monkey2(config-if)# mpls ip
monkey2(config-if-ldp)# end
monkey2# sho ldp discovery

Local LSR Identifier: 192.168.3.2

Interface Discovery Sources:
        eth1: xmit/recv
            LDP Id: 192.168.3.1:0

Targeted Discovery Sources:
        No configured peers

monkey2# show ldp neighbor
Peer LDP Ident: 192.168.3.1:0; Local LDP Ident: 192.168.3.2:0
        TCP connection: 0.0.0.0.646 - 9.67.0.24.0
        State: OPERATIONAL; Msgs sent/recv: 13/34; UNSOLICITED
        Up time: 00:00:56
        LDP discovery sources:
          eth1
        Addresses bound to peer:
          192.168.2.1   192.168.3.1     192.168.1.183   192.168.5.1



monkey2#

In the above output the information about the TCP connection is invalid.
I need to fix this.  When using the standard config, the TCP connection
will be setup using the IP addresses of the directly connected interfaces.

Good luck!

On Tue, Nov 21, 2006 at 05:19:34PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi!
>=20
> After testing static configurations of LSPs and tunnels, now I'm trying to
> automate the process. I've compiled and succesfully installed quagga-mpls
> and ldp-portable from your p4 repository including the links created with
> "create-links" file within the ldpd directory. Now, I'm able to run ospf =
but
> I have some problems with ldp.
>=20
> This is the scenario I use to test it:
>=20
> 13.0.0.0/24   .1   .1          .2   .1          .2   .1   14.0.0.0/24
>          -------PE1--------------PE2--------------PE3-------
>             eth2   eth0      eth1   eth0      eth1   eth2
>                     10.0.0.0/24      11.0.0.0/24
>=20
> And the .conf files in PE2:
>=20
> ZEBRA.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/17 10:18:06
> !
> hostname PE2
> password root
> !
> log file /var/log/quagga/zebra.log
> !
> interface eth0
> !
> interface eth1
> !
> interface lo
> !
> line vty
> !
>=20
> OSPFD.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/09 17:15:53
> !
> hostname l12p07
> password root
> !
> log file /var/log/quagga/ospfd.log
> !
> interface eth0
>  description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255=20
> !=20
> interface eth1 =20
>  description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255=20
> !
> interface lo=20
> !=20
> !=20
> router ospf =20
>  ospf router-id 0.0.0.2
>  network 10.0.0.0/24 area 0 =20
>  network 11.0.0.0/24 area 0=20
> !=20
> !
> line vty=20
> !
>=20
> LDPD.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/17 18:25:07
> !
> hostname ldpd
> password root
> !
> log file /var/log/quagga/ldpd.log
> !
> !mpls ldp
> ! address-mode lsr-id
> ! lsp-control-mode ordered
> ! lsr-id 2.0.0.0
> !
> interface eth0
>  mpls ip
> !  distribution-mode du
> !
> interface eth1
>  mpls ip
> !  distribution-mode du
> !
> interface lo
> !
> line vty
> !
>=20
> Within "ldpd.conf" I have to comment(!) many lines and execute them via
> command line, otherwise the daemon would not start. Also, I did realize t=
hat
> after doing this, they don't appear on the "running config" of ldpd. The
> only command that show up is "mpls ldp".
>=20
> I'd like to configure a LSP from PE1 to PE3, so on PE3 I also put the
> command "egress connected".
>=20
> I capture ldp HELLOs discovering the neighbors and KEEPALIVEs. The HELLO
> packets carry the LSR-Id set on the command line but the KEEPALIVEs from =
PE2
> to PE1 and PE3, always contained a bad TCP CheckSum. Furthermore I don't =
see
> any message regarding sesion activation.
>=20
> Any information about these problems could be very useful.
>=20
> Thanks in advance,
>=20
> regards
>=20
> Gonzalo.


> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


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

[mpls-linux-devel] LDPD configuration

[<gsr...@al...>]

Hi!

After testing static configurations of LSPs and tunnels, now I'm trying =
to
automate the process. I've compiled and succesfully installed =
quagga-mpls
and ldp-portable from your p4 repository including the links created =
with
"create-links" file within the ldpd directory. Now, I'm able to run ospf =
but
I have some problems with ldp.

This is the scenario I use to test it:

13.0.0.0/24   .1   .1          .2   .1          .2   .1   14.0.0.0/24
         -------PE1--------------PE2--------------PE3-------
            eth2   eth0      eth1   eth0      eth1   eth2
                    10.0.0.0/24      11.0.0.0/24

And the .conf files in PE2:

ZEBRA.CONF
------------------------------------------------------------------
!
! Zebra configuration saved from vty
!   2006/11/17 10:18:06
!
hostname PE2
password root
!
log file /var/log/quagga/zebra.log
!
interface eth0
!
interface eth1
!
interface lo
!
line vty
!

OSPFD.CONF
------------------------------------------------------------------
!
! Zebra configuration saved from vty
!   2006/11/09 17:15:53
!
hostname l12p07
password root
!
log file /var/log/quagga/ospfd.log
!
interface eth0
 description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255=20
!=20
interface eth1 =20
 description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255=20
!
interface lo=20
!=20
!=20
router ospf =20
 ospf router-id 0.0.0.2
 network 10.0.0.0/24 area 0 =20
 network 11.0.0.0/24 area 0=20
!=20
!
line vty=20
!

LDPD.CONF
------------------------------------------------------------------
!
! Zebra configuration saved from vty
!   2006/11/17 18:25:07
!
hostname ldpd
password root
!
log file /var/log/quagga/ldpd.log
!
!mpls ldp
! address-mode lsr-id
! lsp-control-mode ordered
! lsr-id 2.0.0.0
!
interface eth0
 mpls ip
!  distribution-mode du
!
interface eth1
 mpls ip
!  distribution-mode du
!
interface lo
!
line vty
!

Within "ldpd.conf" I have to comment(!) many lines and execute them via
command line, otherwise the daemon would not start. Also, I did realize =
that
after doing this, they don't appear on the "running config" of ldpd. The
only command that show up is "mpls ldp".

I'd like to configure a LSP from PE1 to PE3, so on PE3 I also put the
command "egress connected".

I capture ldp HELLOs discovering the neighbors and KEEPALIVEs. The HELLO
packets carry the LSR-Id set on the command line but the KEEPALIVEs from =
PE2
to PE1 and PE3, always contained a bad TCP CheckSum. Furthermore I don't =
see
any message regarding sesion activation.

Any information about these problems could be very useful.

Thanks in advance,

regards

Gonzalo.

Re: [mpls-linux-devel] Hi

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

Your best way to get quagga-mpls with LDP support is to download the
RPMs.  Only developers should try to download ldp-portable and quagga-0.99.4
and compile a version for themselves.

I do not support mpls-linux on the 2.4 kernel.  You will need to upgrade
to a 2.6 kernel.  Again the easiest way to run a MPLS enabled kernel is
to download the RPM.  Only developers should try to compile their own
MPLS enabled kernel.

At this time the released version of quagga-mpls with LDP support
is not ready for users (intended for developers).  If you are a developer
and want to help with the effort, you will want to get the latest version
of quagga-mpls and ldp-portable from my development tree.  Otherwise you
will have to wait until the next release.

On Fri, Nov 17, 2006 at 12:20:31PM +0530, vasudha prasad wrote:
> Hi!
>=20
>=20
> I have downloaded ldp-portable-0.80 and quagga 96.4(I am using linux=20
> 2.4.18with
> mpls-1.1. patched). I have patched and compiled quagga and able to
> communicate with ldpd daemon. Now where should I add basic
> configurations like liberal label retension mode, Independent to test ldp=
d.
> Could u give the commad.
>=20
> Thanks in advance
>=20
> warm regards
>=20
> vasudha

> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


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

[mpls-linux-devel] Hi

[vasudha p. <pra...@gm...>]

Hi!


I have downloaded ldp-portable-0.80 and quagga 96.4(I am using linux 2.4.18with
mpls-1.1. patched). I have patched and compiled quagga and able to
communicate with ldpd daemon. Now where should I add basic
configurations like liberal label retension mode, Independent to test ldpd.
Could u give the commad.

Thanks in advance

warm regards

vasudha

[mpls-linux-devel] mpls tunnel command

[<gsr...@al...>]

Hi!

I'm trying to configure tunnels and I got some problems. I've loaded the =
mpls_tunnel besides mpls and mpls4 modules, and when I put on the =
command line : mpls tunnel add dev mpls1 key 0x2, it says that 'add' is =
an unknow option and reports me to the mpls command usage. When I put =
only mpls tunnel, the result is: Segmentation Fault. I've read through =
the mail lists, and someone who got the same problem, solved it loading =
mpls_tunnel module (he said), but as I told you it's what I do, and it =
doesn't work. Any idea?

However, I'm able to create LSPs so if I couldn't work with mpls tunnel =
command I'll try to make tunnels using a label stack.

(I'm wroking with the linux kernel, iproute2 and iptables 1.950 from =
Source Forge.)

Thanks for your help!

Re: [mpls-linux-devel] Status of MPLS for linux

[Bartek K. <mr...@gn...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 18 Oct 2006, James R. Leu wrote:
> Hello,
> I am the only developer of the mpls-linux project.

That's too bad.
Unfortunately I'm not in a position to help you out there.

> Being that that kernel side has been stable, I have not felt the need
> to work on it.  I try to track the main line kernel in my development tree,
> but I must admit my development tree is still stuck at 2.6.17.4.

The changes to get the release (1.950) version working are minimal.
The only changes of note were that AF_MPLS needs another value, since
the one it uses is now taken, 
and the function subsys_remove_file seems to have been removed from
the kernel.

> I welcome the participation and code contribution of others, if
> nothing else but to give feed back that they have tried the software
> in my development tree and give me a "it works for me" response.
> Another role which I would greatly appreciate would be a release
> manager.  I have spent a lot of time building structure to allow for
> building all of the RPMs that make up mpls-linux right from the
> development tree.  I just do not have to time to do development and
> make new releases.

ItWorksForMe =)
The kernel-patch at least.
In the simplest possible way with static hand-configured labels.
I haven't tested your dev-tree tho, just ver 1.950.

I'm going to be testing quagga with MPLS next.
What setup do you recommend for testing?
Currently I have two vmware-guests connected using two interfaces:
(Tried UML but it didn't behave)
       [internet]
        _____|____
       /  (eth0)  \
   [G1]            [G2]
       \__(eth1)__/

It seems to be a bit simple, and it doesn't have any other hardware.
I'm going to see if I can't borrow a cisco from work and connect that
one too.

/B
- -- 
* GPG-Key: http://evil.gnarf.org/mrbk.pgp

A: Because we read from top to bottom, left to right.
Q: Why should i start my reply below the quoted text?
- -- http://www.i-hate-computers.demon.co.uk/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFNieSckvkFeO3ANARAk7jAKCbck7Er1N3twuIED6HBy6Sv79ZuQCglZch
dtUoHdnqYqaTKaSIzgZbCcE=
=hcqs
-----END PGP SIGNATURE-----

Re: [mpls-linux-devel] Status of MPLS for linux

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

Hello,

I am the only developer of the mpls-linux project.  I have chosen to
spend my development time stabilizing LDP.  This work has been making
significant process, all be it slowly.  The latest developments have not
been published in terms or releases, but can be retrieved via my
development tree.

After I have stabilized LDP, I plan to turn my attention to the RSVP-TE
work which was submitted by a group of developers.  The group of
developers have not been responding to my emails, and they did not publish
a license with their work, so I'm at a bit of a cross roads for what to
do with the code.

Being that that kernel side has been stable, I have not felt the need
to work on it.  I try to track the main line kernel in my development tree,
but I must admit my development tree is still stuck at 2.6.17.4.

I welcome the participation and code contribution of others, if nothing
else but to give feed back that they have tried the software in my developm=
ent
tree and give me a "it works for me" response.  Another role which I would
greatly appreciate would be a release manager.  I have spent a lot of time
building structure to allow for building all of the RPMs that make up
mpls-linux right from the development tree.  I just do not have to time
to do development and make new releases.

On Wed, Oct 18, 2006 at 08:44:19AM +0200, Bartek Kania wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hi!
>=20
> I have a couple of questions about the status of the project.
> Looking at the project homepage I get the impression that it is
> stalled. The ldp-portable and mpls-linux tarballs are a couple years
> old.
>=20
> I have tested the kernel MPLS patch from mpls-linux 1.950 and it
> needed some modifications to work with a 2.6.18-kernel.
> Most of the mods were trivial, but one was a bit above my head (it
> seems sysfs usage has changed a bit). Other than that the patches seem
> to work...
>=20
> Are there plans to get this integrated in the linux kernel?
> Is it ready for that yet?
>=20
> I haven't yet tested the LDP and quagga parts.
> Am I right in assuming that all routing (LDP / RSVP-TE) is done via
> quagga?
> Is there any ongoing work to get this integrated into the quagga tree?
>=20
> /B
> - --=20
> * GPG-Key: http://evil.gnarf.org/mrbk.pgp
>=20
> A: Because we read from top to bottom, left to right.
> Q: Why should i start my reply below the quoted text?
> - -- http://www.i-hate-computers.demon.co.uk/
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>=20
> iD8DBQFFNc1HckvkFeO3ANARAhbeAKCaOYlIo+EnaxaXy8qLxFa0KpznigCgpJsT
> m0TgXjwrw0/vZMUAgXCDnL8=3D
> =3Djnov
> -----END PGP SIGNATURE-----
>=20
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job ea=
sier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

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

[mpls-linux-devel] Status of MPLS for linux

[Bartek K. <mr...@gn...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I have a couple of questions about the status of the project.
Looking at the project homepage I get the impression that it is
stalled. The ldp-portable and mpls-linux tarballs are a couple years
old.

I have tested the kernel MPLS patch from mpls-linux 1.950 and it
needed some modifications to work with a 2.6.18-kernel.
Most of the mods were trivial, but one was a bit above my head (it
seems sysfs usage has changed a bit). Other than that the patches seem
to work...

Are there plans to get this integrated in the linux kernel?
Is it ready for that yet?

I haven't yet tested the LDP and quagga parts.
Am I right in assuming that all routing (LDP / RSVP-TE) is done via
quagga?
Is there any ongoing work to get this integrated into the quagga tree?

/B
- -- 
* GPG-Key: http://evil.gnarf.org/mrbk.pgp

A: Because we read from top to bottom, left to right.
Q: Why should i start my reply below the quoted text?
- -- http://www.i-hate-computers.demon.co.uk/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFNc1HckvkFeO3ANARAhbeAKCaOYlIo+EnaxaXy8qLxFa0KpznigCgpJsT
m0TgXjwrw0/vZMUAgXCDnL8=
=jnov
-----END PGP SIGNATURE-----

Re: [mpls-linux-devel] ldp-portable update

[Steve B. \(Accipiter\) <ba...@ac...>]

James,

I took your latest ldp-portable and quagga-mpls, as of now(10/16/2006), from
your perforce depot and rebuilt quagga and ldpd successfully.

I am able to run zebra, ospfd, and the ldpd with your latest changes. I am
using the 2.6.14-1.1644_FC4mpls_1.950b kernel.

I have previously successfully used ospfd/quagga with AND without your MPLS
before.

I want to use LDP or RSVP-TE to detect a link outage and do an automatic
reroute of its traffic over a different link by dynamically rerouting an LSP
or by dynamically putting traffic on a different LSP carried on a good
alternate link(Link Protection). Does your latest LDP provide this
capability? I notice that in my LDP log file, I get a message "LDP:
Interface[eth0] state update" when I pull/replace the eth0 cable, so it must
detect link out. Do you know what mechanism it uses to detect link out and
how quickly (in milliseconds) it can detect link out?

I can't figure out how to use your LDP for this.  I have looked at the help
information in the mpls program and the help information for all of the
telnet CLIs for the zebra, ospfd, and ldpd daemons. I've also read all of
the README type text files under the various directories. Some of them are
confusing as it appears they have information for items no longer used, as
one example, mplsd.

On your http://mpls-linux.sourceforge.net/ welcome web page change of
7-14-2006, you stated "there exists a new RSVP-TE implementation for quagga,
we're working on integrating it with mpls-linux". Which RSVP-TE
implementation is this? Will it provide the link protection capabilities I
am looking for?

I am willing to help test, fix, and program LDP and/or RSVP-TE if you would
like.

Also, I have tried Adrian Popa's method for link protection. It works quite
well but I would like to use LDP or RSVP-TE for this as I am hoping to get
quicker link failure detection and traffic reroute times. What would you
expect reroute times using LDP or RSVP-TE for link protection?

Thanks in advance and thanks for producing and maintaining mpls-linux.

Steve Bachor


----- Original Message ----- 
From: "James R. Leu" <jl...@mi...>
To: <mpl...@li...>
Sent: Monday, October 02, 2006 10:07 PM
Subject: [mpls-linux-devel] ldp-portable update
Just a quick note to anyone who is working with LDP portable and

quagga-mpls from my development tree, you will want to update your

ldp-portable and quagga-mpls trees.

I have been doing some significant bug hunting that fixes many

of the outstanding issues with quagga-mpls and it's use of ldp-portable.

-- 

James R. Leu

jl...@mi...



> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


--------------------------------------------------------------------------------


> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> 

Re: [mpls-linux-devel] quagga-mpls

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

What Linux distro are you working on?
What versions of the automake package are you using?
Did you install the glibc-kernheaders from the MPLS linux package?
Have you tried building quagga-0.99.4 from http://quagga.net?
Did you modify and run the 'create-links' script in quagga-mpls/ldpd?

My testing environment is Fedora Core 5.  I'm using version 1.9.6
of automake.  There is a script at the top of the quagga-mpls tree that
shows how I go about building my RPMs.  The SPEC file for the RPM is includ=
ed
in the redhat directory.  So you should have everything you need to underst=
and
how my build process works. (really all you need to look at is the first
5 lines of the make-rpm-jleu script)

You can find the glibc-kernheaders in the glibc-kernheaders-mpls
directory at the top of the depot.

On Mon, Oct 16, 2006 at 11:10:54AM +0200, Sienes Rodr?guez Gonzalo wrote:
>=20
> Hi!
>=20
> I've been working with quagga and ldp portable from Source Forge but now =
I'm trying to test your Quagga-MPLS and LDP-Portable from your P4 repositor=
y. I got some problems during installation.
>=20
> To generate configure file from configure.ac I use AUTOCONF, but this is =
what I get:
>=20
> 'is already registered with AC_CONFIG_FILES
> autoconf /status.m4:848: AC_CONFIG_FILES is expanded from...
> configure.ac:1389: the top level
> autom4te:/usr/bin/m4 failed with exit status 1
>=20
> If I use automake to create Makefile.in (then executinc ./configure shoul=
d create Makefile's of each component)I got the same.
> I upgraded M4 and the problem persist, any idea?
>=20
> Anything about how you installed it would be very useful, thanks!
>=20
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job ea=
sier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

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

[mpls-linux-devel] quagga-mpls

[<gsr...@al...>]

Hi!

I've been working with quagga and ldp portable from Source Forge but now =
I'm trying to test your Quagga-MPLS and LDP-Portable from your P4 =
repository. I got some problems during installation.

To generate configure file from configure.ac I use AUTOCONF, but this is =
what I get:

'is already registered with AC_CONFIG_FILES
autoconf /status.m4:848: AC_CONFIG_FILES is expanded from...
configure.ac:1389: the top level
autom4te:/usr/bin/m4 failed with exit status 1

If I use automake to create Makefile.in (then executinc ./configure =
should create Makefile's of each component)I got the same.
I upgraded M4 and the problem persist, any idea?

Anything about how you installed it would be very useful, thanks!