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

[mpls-linux-general] iptables traffic eng.

[Zordan A. <zor...@gm...>]

Hi, 
 
i've set up a little MPLS network under rh9. 
I use 4 pcs in the Core network and 2 Edge Routers to 
bind 2 different networks together: one with 192.168.0.0/24 
and the other 192.168.1.0/24.  
now i wan't to divide different classes of traffic. e.g.  
route ssh over one edge of the core net and everything else over another. 
 
i tried to use iptables with the following commands: 
iptables -t mangle -A FORWARD -p tcp --dport 22 -j MPLS --set-key 0x2 
iptables -t mangle -A OUTPUT -p tcp --dport 22 -j MPLS --set-key 0x2 
 
and 
iptables -t mangle -A FORWARD -d 192.168.1.0/24 -j MPLS --set-key 0x3 
iptables -t mangle -A OUTPUT -d 192.168.1.0/24 -j MPLS --set-key 0x3 
 
but every time i changed the FORWARD-Entries the LER alway ignored my
changes. 
The only thing that worked is to reboot them ... is this a bug or did i 
forget something ?? 
 
regards 
 
Zordan Arres 

-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz

Re: [mpls-linux-general] Problems Patching zebra with LDP

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

First off, I've made the conversion to quagga.  So the code in my
personal tree will not work with zebra.

Second, I have not updated the quagga-ldp patch to work with the 2.6
kernels.

Third, I'm in the midst of writting a proper mpls infrastructure for
quagga.  When I update the LDP patch it will be to interact with my
new mpls infrastructure.

On Sat, Mar 27, 2004 at 08:16:12PM +0100, Josef Perlinger wrote:
> hmm thx Bruno,=20
> but I'll  try to install Zebra + LDP with the kernel 2.6 next week with t=
he
> kernelheaders of 2.6 ,=20
> because I've only managed to compile a 2.6 kernel with mpls support.=20
> I got compilation Errors with 2.4 kernel and that's why it is no alternat=
ive
> for me...
>=20
> I'll keep you informed about my results with 2.6.
>=20
> josef
>=20
> -----Urspr?ngliche Nachricht-----
> Von: Bruno Jorge Marcelino [mailto:bj...@me...]=20
> Gesendet: Samstag, 27. M?rz 2004 15:52
> An: Josef Perlinger
> Cc: mpl...@li...
> Betreff: Re: [mpls-linux-general] Problems Patching zebra with LDP
>=20
>=20
> I had the same problem as you!
>=20
> I think the error RTA_LSP undeclared happens because you are using kernel
> 2.6 (maybe that value has differente name in mpls patch for 2.6)...
>=20
> When I tried to implement ZEBRA+LDP in 2.6 kernel, I also couldn't compil=
e.
> But when I implemented it with kernel 2.4, it complied fine and it worked
> OK!
>=20
> Bruno
>=20
> On Sat, 27 Mar 2004, Josef Perlinger wrote:
>=20
> > Hi to all,
> >
> > I'm sorry I'm flooding the mailing list a little bit, but i really=20
> > come not into the next step the zebra implementation of LDP:
> >
> > I want to use ZEBRA with the LDP Implemenatiotion of MPLS Linux
> >
> > I get also some "Hunks Failed" when I patch the zebra-0.94 files with=
=20
> > the ldp_zebra_diff
> >
> > when I configure and make them I get the following errors:
> >
> > source=3D'rt_netlink.c' object=3D'rt_netlink.o' libtool=3Dno \=20
> > depfile=3D'.deps/rt_netlink.Po' tmpdepfile=3D'.deps/rt_netlink.TPo' \
> > depmode=3Dgcc3 /bin/sh ../depcomp \
> > gcc -DHAVE_CONFIG_H -DSYSCONFDIR=3D\"/usr/local/etc/\" -DMULTIPATH_NUM=
=3D1 -I.
> > -I. -I.. -I.. -I.. -I../lib    -g -O2 -Wall -c `test -f 'rt_netlink.c' =
||
> > echo './'`rt_netlink.c
> > rt_netlink.c: In function `netlink_route_change':
> > rt_netlink.c:678: error: `RTA_LSP' undeclared (first use in this=20
> > function)
> > rt_netlink.c:678: error: (Each undeclared identifier is reported only=
=20
> > once
> > rt_netlink.c:678: error: for each function it appears in.)
> > rt_netlink.c: In function `netlink_route_multipath':
> > rt_netlink.c:1227: error: `RTA_LSP' undeclared (first use in this=20
> > function)
> > rt_netlink.c:1318: error: structure has no member named `rtnh_lsp'
> > rt_netlink.c:1348: error: structure has no member named `rtnh_lsp'
> > make[2]: *** [rt_netlink.o] Error 1
> > make[2]: Leaving directory `/root/zebra-0.94/zebra'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/root/zebra-0.94'
> > make: *** [all] Error 2
> > uml:~/zebra-0.94#
> >
> >
> > When I compile the zebra without mpls patching it the make works.
> >
> > Do you know what I'm doing wrong? or should i wait for the next=20
> > release of the ldp-implementation? When will it be released?
> >
> > I use Debian: sid, uml kernel: 2.6.4
> >
> >
> > regards josef
> >
> > Josef Perlinger
> >
> > Student FH-Sbg/TKS 2000
> > Tel.: +43 664 4024906
> > ICQ: 166227595
> > Email: jo...@pe...
> >
> >
> >
> > attached my Patching output:
> >
> > uml:~/zebra-0.94_mpls# patch -p1 < ../ldp-portable/zebra-ldp.diff=20
> > patching file bgpd/bgpd.c Hunk #2 FAILED at 181.
> > Hunk #3 succeeded at 1758 (offset 60 lines).
> > 1 out of 3 hunks FAILED -- saving rejects to file bgpd/bgpd.c.rej=20
> > patching file bgpd/bgpd.h patching file bgpd/bgp_vty.c Hunk #1=20
> > succeeded at 40 (offset 1 line).
> > Hunk #2 succeeded at 401 (offset 1 line).
> > Hunk #3 succeeded at 429 (offset 1 line).
> > patching file bgpd/bgp_zebra.c
> > patching file config.h.in
> > patching file configure.ac
> > Hunk #2 succeeded at 538 (offset 2 lines).
> > Hunk #3 succeeded at 566 (offset 2 lines).
> > Hunk #4 succeeded at 788 (offset 2 lines).
> > Hunk #5 succeeded at 810 (offset 2 lines).
> > patching file lib/command.c
> > Hunk #1 succeeded at 2153 (offset 73 lines).
> > Hunk #2 succeeded at 2217 (offset 73 lines).
> > patching file lib/command.h
> > patching file lib/if.c
> > patching file lib/if.h
> > patching file lib/linklist.h
> > patching file lib/log.c
> > patching file lib/log.h
> > patching file lib/memory.c
> > patching file lib/memory.h
> > patching file lib/table.c
> > patching file lib/table.h
> > patching file lib/thread.c
> > patching file lib/vty.c
> > Hunk #1 succeeded at 648 (offset 24 lines).
> > Hunk #2 succeeded at 1058 (offset 24 lines).
> > patching file lib/zclient.c
> > patching file lib/zclient.h
> > patching file lib/zebra.h
> > patching file Makefile.am
> > patching file mplsd/create-links
> > patching file mplsd/delete-links
> > patching file mplsd/impl_fib.c
> > patching file mplsd/impl_fib.h
> > patching file mplsd/impl_ifmgr.c
> > patching file mplsd/impl_ifmgr.h
> > patching file mplsd/impl_lock.c
> > patching file mplsd/impl_mm.c
> > patching file mplsd/impl_mpls.c
> > patching file mplsd/impl_mpls.h
> > patching file mplsd/impl_policy.c
> > patching file mplsd/impl_socket.c
> > patching file mplsd/impl_timer.c
> > patching file mplsd/impl_tree.c
> > patching file mplsd/l2cc_interface.c
> > patching file mplsd/l2cc_interface.h
> > patching file mplsd/ldp.c
> > patching file mplsd/ldp.h
> > patching file mplsd/ldp_interface.c
> > patching file mplsd/ldp_interface.h
> > patching file mplsd/ldp_remote_peer.c
> > patching file mplsd/ldp_remote_peer.h
> > patching file mplsd/ldp_vty.c
> > patching file mplsd/ldp_vty.h
> > patching file mplsd/Makefile.am
> > patching file mplsd/mpls.c
> > patching file mplsd/mplsd.conf.sample
> > patching file mplsd/mpls.h
> > patching file mplsd/mpls_handle_type.h patching file=20
> > mplsd/mpls_interface.c patching file mplsd/mpls_interface.h patching=20
> > file mplsd/mpls_main.c patching file mplsd/mpls_trace.h patching file=
=20
> > mplsd/mpls_vty.c patching file mplsd/mpls_vty.h patching file=20
> > mplsd/mpls_zebra.c patching file mplsd/mpls_zebra.h patching file=20
> > mplsd/rsvpte.c patching file mplsd/rsvpte.h patching file=20
> > mplsd/rsvpte_interface.c patching file mplsd/rsvpte_interface.h=20
> > patching file mplsd/rsvpte_vty.c patching file mplsd/rsvpte_vty.h=20
> > patching file mplsd/static.c patching file mplsd/static.h patching=20
> > file mplsd/static_tunnel.c patching file mplsd/static_tunnel.h=20
> > patching file mplsd/static_vty.c patching file mplsd/static_vty.h=20
> > patching file ospfd/ospfd.c Hunk #1 succeeded at 60 with fuzz 1=20
> > (offset 4 lines).
> > Hunk #2 succeeded at 68 (offset 4 lines).
> > Hunk #3 FAILED at 84.
> > 1 out of 3 hunks FAILED -- saving rejects to file ospfd/ospfd.c.rej=20
> > patching file ospfd/ospf_lsdb.c Hunk #1 FAILED at 284.
> > Hunk #2 FAILED at 293.
> > 2 out of 2 hunks FAILED -- saving rejects to file=20
> > ospfd/ospf_lsdb.c.rej patching file ospfd/ospf_lsdb.h Hunk #1 FAILED=20
> > at 79.
> > 1 out of 1 hunk FAILED -- saving rejects to file ospfd/ospf_lsdb.h.rej=
=20
> > patching file ospfd/ospf_vty.c Hunk #1 FAILED at 3046.
> > Hunk #2 succeeded at 3080 (offset 21 lines).
> > Hunk #3 succeeded at 3586 with fuzz 2 (offset -7 lines).
> > Hunk #4 FAILED at 3614.
> > Hunk #5 FAILED at 3642.
> > 3 out of 5 hunks FAILED -- saving rejects to file ospfd/ospf_vty.c.rej=
=20
> > patching file ospfd/ospf_zebra.c Hunk #2 succeeded at 167 (offset 3=20
> > lines).
> > Hunk #3 succeeded at 1153 (offset -17 lines).
> > patching file zebra/main.c
> > patching file zebra/Makefile.am
> > patching file zebra/redistribute.c
> > patching file zebra/rib.h
> > patching file zebra/router-id.c
> > patching file zebra/router-id.h
> > patching file zebra/rt_netlink.c
> > Hunk #1 succeeded at 613 (offset 7 lines).
> > Hunk #2 succeeded at 670 (offset 7 lines).
> > Hunk #3 succeeded at 1222 (offset 9 lines).
> > Hunk #4 succeeded at 1246 (offset 9 lines).
> > Hunk #5 succeeded at 1313 (offset 9 lines).
> > Hunk #6 succeeded at 1342 (offset 9 lines).
> > patching file zebra/zebra_rib.c
> > patching file zebra/zebra_vty.c
> > patching file zebra/zserv.c
> > patching file zebra/zserv.h
> > uml:~/zebra-0.94_mpls#
> >
> >
> > Josef Perlinger
> > Student FH-Sbg/TKS 2000
> > Tel.: +43 664 4024906
> > ICQ: 166227595
> > Email: jo...@pe...
> >
> >
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op?k
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

AW: [mpls-linux-general] Problems Patching zebra with LDP

[Josef P. <jo...@pe...>]

hmm thx Bruno,=20
but I'll  try to install Zebra + LDP with the kernel 2.6 next week with =
the
kernelheaders of 2.6 ,=20
because I've only managed to compile a 2.6 kernel with mpls support.=20
I got compilation Errors with 2.4 kernel and that's why it is no =
alternative
for me...

I'll keep you informed about my results with 2.6.

josef

-----Urspr=FCngliche Nachricht-----
Von: Bruno Jorge Marcelino [mailto:bj...@me...]=20
Gesendet: Samstag, 27. M=E4rz 2004 15:52
An: Josef Perlinger
Cc: mpl...@li...
Betreff: Re: [mpls-linux-general] Problems Patching zebra with LDP


I had the same problem as you!

I think the error RTA_LSP undeclared happens because you are using =
kernel
2.6 (maybe that value has differente name in mpls patch for 2.6)...

When I tried to implement ZEBRA+LDP in 2.6 kernel, I also couldn't =
compile.
But when I implemented it with kernel 2.4, it complied fine and it =
worked
OK!

Bruno

On Sat, 27 Mar 2004, Josef Perlinger wrote:

> Hi to all,
>
> I'm sorry I'm flooding the mailing list a little bit, but i really=20
> come not into the next step the zebra implementation of LDP:
>
> I want to use ZEBRA with the LDP Implemenatiotion of MPLS Linux
>
> I get also some "Hunks Failed" when I patch the zebra-0.94 files with=20
> the ldp_zebra_diff
>
> when I configure and make them I get the following errors:
>
> source=3D'rt_netlink.c' object=3D'rt_netlink.o' libtool=3Dno \=20
> depfile=3D'.deps/rt_netlink.Po' tmpdepfile=3D'.deps/rt_netlink.TPo' \
> depmode=3Dgcc3 /bin/sh ../depcomp \
> gcc -DHAVE_CONFIG_H -DSYSCONFDIR=3D\"/usr/local/etc/\" =
-DMULTIPATH_NUM=3D1 -I.
> -I. -I.. -I.. -I.. -I../lib    -g -O2 -Wall -c `test -f 'rt_netlink.c' =
||
> echo './'`rt_netlink.c
> rt_netlink.c: In function `netlink_route_change':
> rt_netlink.c:678: error: `RTA_LSP' undeclared (first use in this=20
> function)
> rt_netlink.c:678: error: (Each undeclared identifier is reported only=20
> once
> rt_netlink.c:678: error: for each function it appears in.)
> rt_netlink.c: In function `netlink_route_multipath':
> rt_netlink.c:1227: error: `RTA_LSP' undeclared (first use in this=20
> function)
> rt_netlink.c:1318: error: structure has no member named `rtnh_lsp'
> rt_netlink.c:1348: error: structure has no member named `rtnh_lsp'
> make[2]: *** [rt_netlink.o] Error 1
> make[2]: Leaving directory `/root/zebra-0.94/zebra'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/zebra-0.94'
> make: *** [all] Error 2
> uml:~/zebra-0.94#
>
>
> When I compile the zebra without mpls patching it the make works.
>
> Do you know what I'm doing wrong? or should i wait for the next=20
> release of the ldp-implementation? When will it be released?
>
> I use Debian: sid, uml kernel: 2.6.4
>
>
> regards josef
>
> Josef Perlinger
>
> Student FH-Sbg/TKS 2000
> Tel.: +43 664 4024906
> ICQ: 166227595
> Email: jo...@pe...
>
>
>
> attached my Patching output:
>
> uml:~/zebra-0.94_mpls# patch -p1 < ../ldp-portable/zebra-ldp.diff=20
> patching file bgpd/bgpd.c Hunk #2 FAILED at 181.
> Hunk #3 succeeded at 1758 (offset 60 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file bgpd/bgpd.c.rej=20
> patching file bgpd/bgpd.h patching file bgpd/bgp_vty.c Hunk #1=20
> succeeded at 40 (offset 1 line).
> Hunk #2 succeeded at 401 (offset 1 line).
> Hunk #3 succeeded at 429 (offset 1 line).
> patching file bgpd/bgp_zebra.c
> patching file config.h.in
> patching file configure.ac
> Hunk #2 succeeded at 538 (offset 2 lines).
> Hunk #3 succeeded at 566 (offset 2 lines).
> Hunk #4 succeeded at 788 (offset 2 lines).
> Hunk #5 succeeded at 810 (offset 2 lines).
> patching file lib/command.c
> Hunk #1 succeeded at 2153 (offset 73 lines).
> Hunk #2 succeeded at 2217 (offset 73 lines).
> patching file lib/command.h
> patching file lib/if.c
> patching file lib/if.h
> patching file lib/linklist.h
> patching file lib/log.c
> patching file lib/log.h
> patching file lib/memory.c
> patching file lib/memory.h
> patching file lib/table.c
> patching file lib/table.h
> patching file lib/thread.c
> patching file lib/vty.c
> Hunk #1 succeeded at 648 (offset 24 lines).
> Hunk #2 succeeded at 1058 (offset 24 lines).
> patching file lib/zclient.c
> patching file lib/zclient.h
> patching file lib/zebra.h
> patching file Makefile.am
> patching file mplsd/create-links
> patching file mplsd/delete-links
> patching file mplsd/impl_fib.c
> patching file mplsd/impl_fib.h
> patching file mplsd/impl_ifmgr.c
> patching file mplsd/impl_ifmgr.h
> patching file mplsd/impl_lock.c
> patching file mplsd/impl_mm.c
> patching file mplsd/impl_mpls.c
> patching file mplsd/impl_mpls.h
> patching file mplsd/impl_policy.c
> patching file mplsd/impl_socket.c
> patching file mplsd/impl_timer.c
> patching file mplsd/impl_tree.c
> patching file mplsd/l2cc_interface.c
> patching file mplsd/l2cc_interface.h
> patching file mplsd/ldp.c
> patching file mplsd/ldp.h
> patching file mplsd/ldp_interface.c
> patching file mplsd/ldp_interface.h
> patching file mplsd/ldp_remote_peer.c
> patching file mplsd/ldp_remote_peer.h
> patching file mplsd/ldp_vty.c
> patching file mplsd/ldp_vty.h
> patching file mplsd/Makefile.am
> patching file mplsd/mpls.c
> patching file mplsd/mplsd.conf.sample
> patching file mplsd/mpls.h
> patching file mplsd/mpls_handle_type.h patching file=20
> mplsd/mpls_interface.c patching file mplsd/mpls_interface.h patching=20
> file mplsd/mpls_main.c patching file mplsd/mpls_trace.h patching file=20
> mplsd/mpls_vty.c patching file mplsd/mpls_vty.h patching file=20
> mplsd/mpls_zebra.c patching file mplsd/mpls_zebra.h patching file=20
> mplsd/rsvpte.c patching file mplsd/rsvpte.h patching file=20
> mplsd/rsvpte_interface.c patching file mplsd/rsvpte_interface.h=20
> patching file mplsd/rsvpte_vty.c patching file mplsd/rsvpte_vty.h=20
> patching file mplsd/static.c patching file mplsd/static.h patching=20
> file mplsd/static_tunnel.c patching file mplsd/static_tunnel.h=20
> patching file mplsd/static_vty.c patching file mplsd/static_vty.h=20
> patching file ospfd/ospfd.c Hunk #1 succeeded at 60 with fuzz 1=20
> (offset 4 lines).
> Hunk #2 succeeded at 68 (offset 4 lines).
> Hunk #3 FAILED at 84.
> 1 out of 3 hunks FAILED -- saving rejects to file ospfd/ospfd.c.rej=20
> patching file ospfd/ospf_lsdb.c Hunk #1 FAILED at 284.
> Hunk #2 FAILED at 293.
> 2 out of 2 hunks FAILED -- saving rejects to file=20
> ospfd/ospf_lsdb.c.rej patching file ospfd/ospf_lsdb.h Hunk #1 FAILED=20
> at 79.
> 1 out of 1 hunk FAILED -- saving rejects to file ospfd/ospf_lsdb.h.rej =

> patching file ospfd/ospf_vty.c Hunk #1 FAILED at 3046.
> Hunk #2 succeeded at 3080 (offset 21 lines).
> Hunk #3 succeeded at 3586 with fuzz 2 (offset -7 lines).
> Hunk #4 FAILED at 3614.
> Hunk #5 FAILED at 3642.
> 3 out of 5 hunks FAILED -- saving rejects to file ospfd/ospf_vty.c.rej =

> patching file ospfd/ospf_zebra.c Hunk #2 succeeded at 167 (offset 3=20
> lines).
> Hunk #3 succeeded at 1153 (offset -17 lines).
> patching file zebra/main.c
> patching file zebra/Makefile.am
> patching file zebra/redistribute.c
> patching file zebra/rib.h
> patching file zebra/router-id.c
> patching file zebra/router-id.h
> patching file zebra/rt_netlink.c
> Hunk #1 succeeded at 613 (offset 7 lines).
> Hunk #2 succeeded at 670 (offset 7 lines).
> Hunk #3 succeeded at 1222 (offset 9 lines).
> Hunk #4 succeeded at 1246 (offset 9 lines).
> Hunk #5 succeeded at 1313 (offset 9 lines).
> Hunk #6 succeeded at 1342 (offset 9 lines).
> patching file zebra/zebra_rib.c
> patching file zebra/zebra_vty.c
> patching file zebra/zserv.c
> patching file zebra/zserv.h
> uml:~/zebra-0.94_mpls#
>
>
> Josef Perlinger
> Student FH-Sbg/TKS 2000
> Tel.: +43 664 4024906
> ICQ: 166227595
> Email: jo...@pe...
>
>
>

Re: [mpls-linux-general] Problems Patching zebra with LDP

[Bruno J. M. <bj...@me...>]

I had the same problem as you!

I think the error RTA_LSP undeclared happens because you are using kernel
2.6 (maybe that value has differente name in mpls patch for 2.6)...

When I tried to implement ZEBRA+LDP in 2.6 kernel, I also couldn't
compile. But when I implemented it with kernel 2.4, it complied fine and
it worked OK!

Bruno

On Sat, 27 Mar 2004, Josef Perlinger wrote:

> Hi to all,
>
> I'm sorry I'm flooding the mailing list a little bit, but i really come not
> into the next step the zebra implementation of LDP:
>
> I want to use ZEBRA with the LDP Implemenatiotion of MPLS Linux
>
> I get also some "Hunks Failed" when I patch the zebra-0.94 files with the
> ldp_zebra_diff
>
> when I configure and make them I get the following errors:
>
> source='rt_netlink.c' object='rt_netlink.o' libtool=no \
> depfile='.deps/rt_netlink.Po' tmpdepfile='.deps/rt_netlink.TPo' \
> depmode=gcc3 /bin/sh ../depcomp \
> gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/usr/local/etc/\" -DMULTIPATH_NUM=1 -I.
> -I. -I.. -I.. -I.. -I../lib    -g -O2 -Wall -c `test -f 'rt_netlink.c' ||
> echo './'`rt_netlink.c
> rt_netlink.c: In function `netlink_route_change':
> rt_netlink.c:678: error: `RTA_LSP' undeclared (first use in this function)
> rt_netlink.c:678: error: (Each undeclared identifier is reported only once
> rt_netlink.c:678: error: for each function it appears in.)
> rt_netlink.c: In function `netlink_route_multipath':
> rt_netlink.c:1227: error: `RTA_LSP' undeclared (first use in this function)
> rt_netlink.c:1318: error: structure has no member named `rtnh_lsp'
> rt_netlink.c:1348: error: structure has no member named `rtnh_lsp'
> make[2]: *** [rt_netlink.o] Error 1
> make[2]: Leaving directory `/root/zebra-0.94/zebra'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/zebra-0.94'
> make: *** [all] Error 2
> uml:~/zebra-0.94#
>
>
> When I compile the zebra without mpls patching it the make works.
>
> Do you know what I'm doing wrong? or should i wait for the next release of
> the ldp-implementation? When will it be released?
>
> I use Debian: sid, uml kernel: 2.6.4
>
>
> regards josef
>
> Josef Perlinger
>
> Student FH-Sbg/TKS 2000
> Tel.: +43 664 4024906
> ICQ: 166227595
> Email: jo...@pe...
>
>
>
> attached my Patching output:
>
> uml:~/zebra-0.94_mpls# patch -p1 < ../ldp-portable/zebra-ldp.diff
> patching file bgpd/bgpd.c
> Hunk #2 FAILED at 181.
> Hunk #3 succeeded at 1758 (offset 60 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file bgpd/bgpd.c.rej
> patching file bgpd/bgpd.h
> patching file bgpd/bgp_vty.c
> Hunk #1 succeeded at 40 (offset 1 line).
> Hunk #2 succeeded at 401 (offset 1 line).
> Hunk #3 succeeded at 429 (offset 1 line).
> patching file bgpd/bgp_zebra.c
> patching file config.h.in
> patching file configure.ac
> Hunk #2 succeeded at 538 (offset 2 lines).
> Hunk #3 succeeded at 566 (offset 2 lines).
> Hunk #4 succeeded at 788 (offset 2 lines).
> Hunk #5 succeeded at 810 (offset 2 lines).
> patching file lib/command.c
> Hunk #1 succeeded at 2153 (offset 73 lines).
> Hunk #2 succeeded at 2217 (offset 73 lines).
> patching file lib/command.h
> patching file lib/if.c
> patching file lib/if.h
> patching file lib/linklist.h
> patching file lib/log.c
> patching file lib/log.h
> patching file lib/memory.c
> patching file lib/memory.h
> patching file lib/table.c
> patching file lib/table.h
> patching file lib/thread.c
> patching file lib/vty.c
> Hunk #1 succeeded at 648 (offset 24 lines).
> Hunk #2 succeeded at 1058 (offset 24 lines).
> patching file lib/zclient.c
> patching file lib/zclient.h
> patching file lib/zebra.h
> patching file Makefile.am
> patching file mplsd/create-links
> patching file mplsd/delete-links
> patching file mplsd/impl_fib.c
> patching file mplsd/impl_fib.h
> patching file mplsd/impl_ifmgr.c
> patching file mplsd/impl_ifmgr.h
> patching file mplsd/impl_lock.c
> patching file mplsd/impl_mm.c
> patching file mplsd/impl_mpls.c
> patching file mplsd/impl_mpls.h
> patching file mplsd/impl_policy.c
> patching file mplsd/impl_socket.c
> patching file mplsd/impl_timer.c
> patching file mplsd/impl_tree.c
> patching file mplsd/l2cc_interface.c
> patching file mplsd/l2cc_interface.h
> patching file mplsd/ldp.c
> patching file mplsd/ldp.h
> patching file mplsd/ldp_interface.c
> patching file mplsd/ldp_interface.h
> patching file mplsd/ldp_remote_peer.c
> patching file mplsd/ldp_remote_peer.h
> patching file mplsd/ldp_vty.c
> patching file mplsd/ldp_vty.h
> patching file mplsd/Makefile.am
> patching file mplsd/mpls.c
> patching file mplsd/mplsd.conf.sample
> patching file mplsd/mpls.h
> patching file mplsd/mpls_handle_type.h
> patching file mplsd/mpls_interface.c
> patching file mplsd/mpls_interface.h
> patching file mplsd/mpls_main.c
> patching file mplsd/mpls_trace.h
> patching file mplsd/mpls_vty.c
> patching file mplsd/mpls_vty.h
> patching file mplsd/mpls_zebra.c
> patching file mplsd/mpls_zebra.h
> patching file mplsd/rsvpte.c
> patching file mplsd/rsvpte.h
> patching file mplsd/rsvpte_interface.c
> patching file mplsd/rsvpte_interface.h
> patching file mplsd/rsvpte_vty.c
> patching file mplsd/rsvpte_vty.h
> patching file mplsd/static.c
> patching file mplsd/static.h
> patching file mplsd/static_tunnel.c
> patching file mplsd/static_tunnel.h
> patching file mplsd/static_vty.c
> patching file mplsd/static_vty.h
> patching file ospfd/ospfd.c
> Hunk #1 succeeded at 60 with fuzz 1 (offset 4 lines).
> Hunk #2 succeeded at 68 (offset 4 lines).
> Hunk #3 FAILED at 84.
> 1 out of 3 hunks FAILED -- saving rejects to file ospfd/ospfd.c.rej
> patching file ospfd/ospf_lsdb.c
> Hunk #1 FAILED at 284.
> Hunk #2 FAILED at 293.
> 2 out of 2 hunks FAILED -- saving rejects to file ospfd/ospf_lsdb.c.rej
> patching file ospfd/ospf_lsdb.h
> Hunk #1 FAILED at 79.
> 1 out of 1 hunk FAILED -- saving rejects to file ospfd/ospf_lsdb.h.rej
> patching file ospfd/ospf_vty.c
> Hunk #1 FAILED at 3046.
> Hunk #2 succeeded at 3080 (offset 21 lines).
> Hunk #3 succeeded at 3586 with fuzz 2 (offset -7 lines).
> Hunk #4 FAILED at 3614.
> Hunk #5 FAILED at 3642.
> 3 out of 5 hunks FAILED -- saving rejects to file ospfd/ospf_vty.c.rej
> patching file ospfd/ospf_zebra.c
> Hunk #2 succeeded at 167 (offset 3 lines).
> Hunk #3 succeeded at 1153 (offset -17 lines).
> patching file zebra/main.c
> patching file zebra/Makefile.am
> patching file zebra/redistribute.c
> patching file zebra/rib.h
> patching file zebra/router-id.c
> patching file zebra/router-id.h
> patching file zebra/rt_netlink.c
> Hunk #1 succeeded at 613 (offset 7 lines).
> Hunk #2 succeeded at 670 (offset 7 lines).
> Hunk #3 succeeded at 1222 (offset 9 lines).
> Hunk #4 succeeded at 1246 (offset 9 lines).
> Hunk #5 succeeded at 1313 (offset 9 lines).
> Hunk #6 succeeded at 1342 (offset 9 lines).
> patching file zebra/zebra_rib.c
> patching file zebra/zebra_vty.c
> patching file zebra/zserv.c
> patching file zebra/zserv.h
> uml:~/zebra-0.94_mpls#
>
>
> Josef Perlinger
> Student FH-Sbg/TKS 2000
> Tel.: +43 664 4024906
> ICQ: 166227595
> Email: jo...@pe...
>
>
>

Re: [mpls-linux-general] Problems Patching zebra with LDP

[Ramon C. <cas...@in...>]

On Sat, 27 Mar 2004, Josef Perlinger wrote:

>
> I get also some "Hunks Failed" when I patch the zebra-0.94 files with the
> ldp_zebra_diff
>
> when I configure and make them I get the following errors:
>


Let me explain myself. If you compile a C program that has this line:
#include <linux/rtnetlink> in most default configurations gcc is going
to look at /usr/include/linux/rtnetlink.

Nowadays most distributions release a set of 'kernel headers' which are
stable enough, and put into /usr/include. These headers need not match you
current running kernel (All this is a little confusing for some people. In
fact, userspace applications should not include kernel header files but,
unfortunately, some userspace applications need to...

In your case, you may have on one hand your mpls patched kernel and on the
other one a set of kernel headers that have never heard of MPLS. Zebra
looks at them..

A fast workaround would be to modify zebra Makefile so it looks at the
MPLS enabled kernel headers first (something like -I/path/to/mpls/kernel)
do this at your own risk...


>
> When I compile the zebra without mpls patching it the make works.

Sure, because the kernel headers found in /usr/include are enough for
zebra..

Regards,
Ramon

Re: [mpls-linux-general] Problems Patching zebra with LDP

[Ramon C. <cas...@in...>]

On Sat, 27 Mar 2004, Josef Perlinger wrote:

> Hi to all,
>
>
> When I compile the zebra without mpls patching it the make works.
>
> Do you know what I'm doing wrong? or should i wait for the next release of
> the ldp-implementation? When will it be released?
>


I don't know a lot about zebra, but make sure that you compile it using
the patched (with mpls-linux) kernel headers. According to your error, the
zebra compilation does not see the RTA_LSP which exists only in MPLS
enabled kernels.

Regards,
R.

[mpls-linux-general] Problems Patching zebra with LDP

[Josef P. <jo...@pe...>]

Hi to all,

I'm sorry I'm flooding the mailing list a little bit, but i really come not
into the next step the zebra implementation of LDP:

I want to use ZEBRA with the LDP Implemenatiotion of MPLS Linux

I get also some "Hunks Failed" when I patch the zebra-0.94 files with the
ldp_zebra_diff

when I configure and make them I get the following errors:

source='rt_netlink.c' object='rt_netlink.o' libtool=no \
depfile='.deps/rt_netlink.Po' tmpdepfile='.deps/rt_netlink.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/usr/local/etc/\" -DMULTIPATH_NUM=1 -I.
-I. -I.. -I.. -I.. -I../lib    -g -O2 -Wall -c `test -f 'rt_netlink.c' ||
echo './'`rt_netlink.c
rt_netlink.c: In function `netlink_route_change':
rt_netlink.c:678: error: `RTA_LSP' undeclared (first use in this function)
rt_netlink.c:678: error: (Each undeclared identifier is reported only once
rt_netlink.c:678: error: for each function it appears in.)
rt_netlink.c: In function `netlink_route_multipath':
rt_netlink.c:1227: error: `RTA_LSP' undeclared (first use in this function)
rt_netlink.c:1318: error: structure has no member named `rtnh_lsp'
rt_netlink.c:1348: error: structure has no member named `rtnh_lsp'
make[2]: *** [rt_netlink.o] Error 1
make[2]: Leaving directory `/root/zebra-0.94/zebra'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/zebra-0.94'
make: *** [all] Error 2
uml:~/zebra-0.94# 


When I compile the zebra without mpls patching it the make works.

Do you know what I'm doing wrong? or should i wait for the next release of
the ldp-implementation? When will it be released?

I use Debian: sid, uml kernel: 2.6.4


regards josef

Josef Perlinger

Student FH-Sbg/TKS 2000
Tel.: +43 664 4024906
ICQ: 166227595
Email: jo...@pe...



attached my Patching output:

uml:~/zebra-0.94_mpls# patch -p1 < ../ldp-portable/zebra-ldp.diff 
patching file bgpd/bgpd.c
Hunk #2 FAILED at 181.
Hunk #3 succeeded at 1758 (offset 60 lines).
1 out of 3 hunks FAILED -- saving rejects to file bgpd/bgpd.c.rej
patching file bgpd/bgpd.h
patching file bgpd/bgp_vty.c
Hunk #1 succeeded at 40 (offset 1 line).
Hunk #2 succeeded at 401 (offset 1 line).
Hunk #3 succeeded at 429 (offset 1 line).
patching file bgpd/bgp_zebra.c
patching file config.h.in
patching file configure.ac
Hunk #2 succeeded at 538 (offset 2 lines).
Hunk #3 succeeded at 566 (offset 2 lines).
Hunk #4 succeeded at 788 (offset 2 lines).
Hunk #5 succeeded at 810 (offset 2 lines).
patching file lib/command.c
Hunk #1 succeeded at 2153 (offset 73 lines).
Hunk #2 succeeded at 2217 (offset 73 lines).
patching file lib/command.h
patching file lib/if.c
patching file lib/if.h
patching file lib/linklist.h
patching file lib/log.c
patching file lib/log.h
patching file lib/memory.c
patching file lib/memory.h
patching file lib/table.c
patching file lib/table.h
patching file lib/thread.c
patching file lib/vty.c
Hunk #1 succeeded at 648 (offset 24 lines).
Hunk #2 succeeded at 1058 (offset 24 lines).
patching file lib/zclient.c
patching file lib/zclient.h
patching file lib/zebra.h
patching file Makefile.am
patching file mplsd/create-links
patching file mplsd/delete-links
patching file mplsd/impl_fib.c
patching file mplsd/impl_fib.h
patching file mplsd/impl_ifmgr.c
patching file mplsd/impl_ifmgr.h
patching file mplsd/impl_lock.c
patching file mplsd/impl_mm.c
patching file mplsd/impl_mpls.c
patching file mplsd/impl_mpls.h
patching file mplsd/impl_policy.c
patching file mplsd/impl_socket.c
patching file mplsd/impl_timer.c
patching file mplsd/impl_tree.c
patching file mplsd/l2cc_interface.c
patching file mplsd/l2cc_interface.h
patching file mplsd/ldp.c
patching file mplsd/ldp.h
patching file mplsd/ldp_interface.c
patching file mplsd/ldp_interface.h
patching file mplsd/ldp_remote_peer.c
patching file mplsd/ldp_remote_peer.h
patching file mplsd/ldp_vty.c
patching file mplsd/ldp_vty.h
patching file mplsd/Makefile.am
patching file mplsd/mpls.c
patching file mplsd/mplsd.conf.sample
patching file mplsd/mpls.h
patching file mplsd/mpls_handle_type.h
patching file mplsd/mpls_interface.c
patching file mplsd/mpls_interface.h
patching file mplsd/mpls_main.c
patching file mplsd/mpls_trace.h
patching file mplsd/mpls_vty.c
patching file mplsd/mpls_vty.h
patching file mplsd/mpls_zebra.c
patching file mplsd/mpls_zebra.h
patching file mplsd/rsvpte.c
patching file mplsd/rsvpte.h
patching file mplsd/rsvpte_interface.c
patching file mplsd/rsvpte_interface.h
patching file mplsd/rsvpte_vty.c
patching file mplsd/rsvpte_vty.h
patching file mplsd/static.c
patching file mplsd/static.h
patching file mplsd/static_tunnel.c
patching file mplsd/static_tunnel.h
patching file mplsd/static_vty.c
patching file mplsd/static_vty.h
patching file ospfd/ospfd.c
Hunk #1 succeeded at 60 with fuzz 1 (offset 4 lines).
Hunk #2 succeeded at 68 (offset 4 lines).
Hunk #3 FAILED at 84.
1 out of 3 hunks FAILED -- saving rejects to file ospfd/ospfd.c.rej
patching file ospfd/ospf_lsdb.c
Hunk #1 FAILED at 284.
Hunk #2 FAILED at 293.
2 out of 2 hunks FAILED -- saving rejects to file ospfd/ospf_lsdb.c.rej
patching file ospfd/ospf_lsdb.h
Hunk #1 FAILED at 79.
1 out of 1 hunk FAILED -- saving rejects to file ospfd/ospf_lsdb.h.rej
patching file ospfd/ospf_vty.c
Hunk #1 FAILED at 3046.
Hunk #2 succeeded at 3080 (offset 21 lines).
Hunk #3 succeeded at 3586 with fuzz 2 (offset -7 lines).
Hunk #4 FAILED at 3614.
Hunk #5 FAILED at 3642.
3 out of 5 hunks FAILED -- saving rejects to file ospfd/ospf_vty.c.rej
patching file ospfd/ospf_zebra.c
Hunk #2 succeeded at 167 (offset 3 lines).
Hunk #3 succeeded at 1153 (offset -17 lines).
patching file zebra/main.c
patching file zebra/Makefile.am
patching file zebra/redistribute.c
patching file zebra/rib.h
patching file zebra/router-id.c
patching file zebra/router-id.h
patching file zebra/rt_netlink.c
Hunk #1 succeeded at 613 (offset 7 lines).
Hunk #2 succeeded at 670 (offset 7 lines).
Hunk #3 succeeded at 1222 (offset 9 lines).
Hunk #4 succeeded at 1246 (offset 9 lines).
Hunk #5 succeeded at 1313 (offset 9 lines).
Hunk #6 succeeded at 1342 (offset 9 lines).
patching file zebra/zebra_rib.c
patching file zebra/zebra_vty.c
patching file zebra/zserv.c
patching file zebra/zserv.h
uml:~/zebra-0.94_mpls# 


Josef Perlinger
Student FH-Sbg/TKS 2000
Tel.: +43 664 4024906
ICQ: 166227595
Email: jo...@pe...

Re: [mpls-linux-general] Ping Problem

[Ramon C. <cas...@in...>]

On Fri, 26 Mar 2004, James R. Leu wrote:

> I wonder if he found a bug.  It seems to be triggered when he issues
> an "ILM" add before setting the labelspace.  In the code we create the


I think that the case where the labelspace was changed without being reset
(something that I did not happen to test) was not considered.


What about:


static int
__mpls_set_labelspace (struct net_device *dev, int labelspace)
{
        struct mpls_interface *mpls_ptr = NULL;

        MPLS_ENTER;
        if (!dev->mpls_ptr) {
                if (labelspace != -1) {
                        mpls_ptr = mpls_create_if_info ();
                        if (unlikely(!mpls_ptr)) {
                                MPLS_DEBUG("Set labelspace for %s to %d
failed\n",
                                        dev->name, labelspace);
                                MPLS_EXIT;
                                return -ENOMEM;
                        }
                        /* Actual assignment happens here */
                        mpls_ptr->labelspace = labelspace;
                        dev->mpls_ptr = (void*)mpls_ptr;
                        MPLS_DEBUG("Set labelspace for %s to %d\n",
                                dev->name, labelspace);
                }
        } else {
                if (labelspace == -1) {
                        MPLS_DEBUG("Resetting labelspace for %s to %d\n",
                                dev->name,-1);
                        mpls_delete_if_info (dev->mpls_ptr);
                        dev->mpls_ptr = NULL;
                } else {
                        dev->mpls_ptr->labelspace = labelspace;
                }

        }
        MPLS_EXIT;
        return 0;
}


 (not comitted in p4 yet) although I am not convinced that this was the
cause of Josef's problems....

Comments?

R.

Re: [mpls-linux-general] Problems pinging vom Ingress to Egress

[Ramon C. <cas...@in...>]

Hi Josef,

May I get the output of these commands and dmesg? as James said, even if
the internal device structures don't exist , they should be created when
issuing a set command.

> The following comands I've entered
>
> UML1:
> mplsadm2 -A -O 0;
> mplsadm2 -O 0x2 -o push:gen:16:set:eth1:ipv4:11.0.1.2
> ip route add 11.0.1.2/32 via 11.0.1.2 spec_nh 0x8847 0x2
> mplsadm2 -A -I gen:17:0
> mplsadm2 -L eth1:0


We are mostly interested in the lines containg
mpls_build_opcode_set


Did you ifconfigged eth1 between theses commands?



James: (Hint) I think that this is missing:

__mpls_set_labelspace

        if ((labelspace != -1) && (dev->mpls_ptr)) {
                dev->mpls_ptr ->labelspace = labelspace;
        }


e.g. in the case that there was a previous labelspace set.
Anyway, I think __mpls_set_labelspace could use a rewrite


Regards,
Ramon

Re: [mpls-linux-general] MPLS+IPv6

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

On Fri, Mar 26, 2004 at 06:04:41PM +0000, Bruno Jorge Marcelino wrote:
> 
> Yes. I applied the mpls patch in the kernel and build it.

I will create a patch that adds debugging to the IPv6 stack to se can
see what is happening.

> On Fri, 26 Mar 2004, James R. Leu wrote:
> 
> > Did you build the kernel fro a patch?  It so, I can send you a patch that
> > adds some debugging.  Otherwise I will have to build a custom RPM for you.
> >
> > On Fri, Mar 26, 2004 at 03:47:52PM +0000, Bruno Jorge Marcelino wrote:
> > >
> > > I've checked dmesg and seems the packets aren't entering the MPLS stack...
> > >
> > > The only messages that I have are from (modified) mplsadm2 commands:
> > > 	mplsadm2 -d
> > > 	mplsadm2 -A -O 0 -o push.gen.56.set.eth1.ipv6.$NET::65
> > >
> > > MPLSADM mplsadm6.c:696:main: Out segment input: 0
> > > MPLSADM mplsadm6.c:692:main: Out instr input:
> > > push.gen.56.set.eth1.ipv6.fc97:86d5:b2ed::65
> > > Key: 0x00000002
> > > Out Segment add: Success
> > > MPLSADM mplsadm6.c:296:fill_instructions: Instruction: push
> > > MPLSADM mplsadm6.c:233:fill_label: Label type: gen
> > > MPLSADM mplsadm6.c:296:fill_instructions: Instruction: set
> > > MPLSADM mplsadm6.c:185:parse_nh_info: eth1
> > > MPLSADM mplsadm6.c:186:parse_nh_info: fc97:86d5:b2ed::65
> > > MPLSADM mplsadm6.c:208:parse_nh_info: Nexthop protocol: ipv6
> > > MPLSADM mplsadm6.c:600:fill_instructions: Length: 2
> > > Out Instr: Success
> > >
> > > 	output of dmesg:
> > >
> > > MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847
> > > MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
> > > MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE moi-2
> > > MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
> > > MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864
> > > MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
> > > MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
> > > MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
> > > MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
> > > MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
> > > MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(c1663bc0)
> > > MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
> > > MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> > > MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-00-PUSH
> > > MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> > > MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> > > MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-01-SET
> > > MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> > >
> > > routerPC5:/usr/src/mpls-linux/utils# cat /proc/net/mpls/out
> > > MOI Key:0x00000002 Instruction Set
> > > PUSH PUSH(gen 56)
> > > SET SET(eth1,0.0.0.0)
> > >
> > > I first used
> > > 	ip6tables -A OUTPUT -d $NET:2::/64 -j spec_nh --spec_nh 0x8847:0x2
> > > and then
> > > 	ip -f inet6 route add $NET:2::/64 dev eth1 spec_nh 0x8847 0x2
> > >
> > > and none of the above commands worked! The packets aren't using MPLS to leave the router...
> > >
> > > I have an IPv6 network with 5 PC's running debian testing/unstable, kernel
> > > 2.6.2+mpls-1.922.
> > >
> > > Can you help me resolve my problem/improving IPv6 support in
> > > MPLS and ldp-portable?
> > >
> > > I can make some changes in the code, but I you need to point me on what to do!
> > >
> > > Regarding the changes in mplsadm2, you can see the parsing of commands
> > > has changed from ":" to "." (because in IPv6, separator is now ":"). This
> > > conflicts with IPv4 addresses...
> > >
> > > Bruno
> > >
> > >
> > > On Wed, 24 Mar 2004, James R. Leu wrote:
> > >
> > > > On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> > > > > Hi there!
> > > > >
> > > > > I'm doing some research on MPLS and IPv6 for my master thesis...
> > > > >
> > > > > Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!
> > > >
> > > > I will be releasing 1.930 soon, with support for MPLS ICMP and better
> > > > internal locking and referencing.
> > > >
> > > > > I've changed mplsadm2 to work with IPv6 address, and by looking at
> > > > > debugging messages, I think that's all OK (no errors are found).
> > > >
> > > > Please send me a patch, I'd like to include support for IPv6.
> > > >
> > > > > Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> > > > > with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).
> > > >
> > > > This should be an easy to fix.
> > > >
> > > > > But I have a problem when binding FEC to LSP (with mpls patched
> > > > > ip6tables): it isn't working! The traffic is not leaving the router using
> > > > > mpls.
> > > > >
> > > > > Do you have any idea on the problem?
> > > >
> > > > Did you check the MPLS kernel debug?  (execute the command 'dmesg').
> > > > Did the packets ever enter the MPLS stack?  What command did you
> > > > use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
> > > > to test with (nor do I know how to set one up).
> > > >
> > > > Have you tried 'ip'?
> > > >
> > > > ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>
> > > >
> > > > > What's the status on porting ldp-portable to 2.6 kernel with IPv6?
> > > >
> > > > ldp-portable has the structures to handle IPv6, but no code has been written
> > > > to handle IPv6.  I would be glad to point you to the places I know that
> > > > would be affected by IPv6.
> > > >
> > > > --
> > > > James R. Leu
> > > > jl...@mi...
> > > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: IBM Linux Tutorials
> > > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > > GenToo technologies. Learn everything from fundamentals to system
> > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] MPLS+IPv6

[Bruno J. M. <bj...@me...>]

Yes. I applied the mpls patch in the kernel and build it.

On Fri, 26 Mar 2004, James R. Leu wrote:

> Did you build the kernel fro a patch?  It so, I can send you a patch that
> adds some debugging.  Otherwise I will have to build a custom RPM for you.
>
> On Fri, Mar 26, 2004 at 03:47:52PM +0000, Bruno Jorge Marcelino wrote:
> >
> > I've checked dmesg and seems the packets aren't entering the MPLS stack...
> >
> > The only messages that I have are from (modified) mplsadm2 commands:
> > 	mplsadm2 -d
> > 	mplsadm2 -A -O 0 -o push.gen.56.set.eth1.ipv6.$NET::65
> >
> > MPLSADM mplsadm6.c:696:main: Out segment input: 0
> > MPLSADM mplsadm6.c:692:main: Out instr input:
> > push.gen.56.set.eth1.ipv6.fc97:86d5:b2ed::65
> > Key: 0x00000002
> > Out Segment add: Success
> > MPLSADM mplsadm6.c:296:fill_instructions: Instruction: push
> > MPLSADM mplsadm6.c:233:fill_label: Label type: gen
> > MPLSADM mplsadm6.c:296:fill_instructions: Instruction: set
> > MPLSADM mplsadm6.c:185:parse_nh_info: eth1
> > MPLSADM mplsadm6.c:186:parse_nh_info: fc97:86d5:b2ed::65
> > MPLSADM mplsadm6.c:208:parse_nh_info: Nexthop protocol: ipv6
> > MPLSADM mplsadm6.c:600:fill_instructions: Length: 2
> > Out Instr: Success
> >
> > 	output of dmesg:
> >
> > MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847
> > MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
> > MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE moi-2
> > MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
> > MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864
> > MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
> > MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
> > MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
> > MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
> > MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
> > MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(c1663bc0)
> > MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
> > MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> > MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-00-PUSH
> > MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> > MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> > MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-01-SET
> > MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> >
> > routerPC5:/usr/src/mpls-linux/utils# cat /proc/net/mpls/out
> > MOI Key:0x00000002 Instruction Set
> > PUSH PUSH(gen 56)
> > SET SET(eth1,0.0.0.0)
> >
> > I first used
> > 	ip6tables -A OUTPUT -d $NET:2::/64 -j spec_nh --spec_nh 0x8847:0x2
> > and then
> > 	ip -f inet6 route add $NET:2::/64 dev eth1 spec_nh 0x8847 0x2
> >
> > and none of the above commands worked! The packets aren't using MPLS to leave the router...
> >
> > I have an IPv6 network with 5 PC's running debian testing/unstable, kernel
> > 2.6.2+mpls-1.922.
> >
> > Can you help me resolve my problem/improving IPv6 support in
> > MPLS and ldp-portable?
> >
> > I can make some changes in the code, but I you need to point me on what to do!
> >
> > Regarding the changes in mplsadm2, you can see the parsing of commands
> > has changed from ":" to "." (because in IPv6, separator is now ":"). This
> > conflicts with IPv4 addresses...
> >
> > Bruno
> >
> >
> > On Wed, 24 Mar 2004, James R. Leu wrote:
> >
> > > On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> > > > Hi there!
> > > >
> > > > I'm doing some research on MPLS and IPv6 for my master thesis...
> > > >
> > > > Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!
> > >
> > > I will be releasing 1.930 soon, with support for MPLS ICMP and better
> > > internal locking and referencing.
> > >
> > > > I've changed mplsadm2 to work with IPv6 address, and by looking at
> > > > debugging messages, I think that's all OK (no errors are found).
> > >
> > > Please send me a patch, I'd like to include support for IPv6.
> > >
> > > > Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> > > > with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).
> > >
> > > This should be an easy to fix.
> > >
> > > > But I have a problem when binding FEC to LSP (with mpls patched
> > > > ip6tables): it isn't working! The traffic is not leaving the router using
> > > > mpls.
> > > >
> > > > Do you have any idea on the problem?
> > >
> > > Did you check the MPLS kernel debug?  (execute the command 'dmesg').
> > > Did the packets ever enter the MPLS stack?  What command did you
> > > use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
> > > to test with (nor do I know how to set one up).
> > >
> > > Have you tried 'ip'?
> > >
> > > ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>
> > >
> > > > What's the status on porting ldp-portable to 2.6 kernel with IPv6?
> > >
> > > ldp-portable has the structures to handle IPv6, but no code has been written
> > > to handle IPv6.  I would be glad to point you to the places I know that
> > > would be affected by IPv6.
> > >
> > > --
> > > James R. Leu
> > > jl...@mi...
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
> jl...@mi...
>

Re: [mpls-linux-general] Ping Problem

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

I wonder if he found a bug.  It seems to be triggered when he issues
an "ILM" add before setting the labelspace.  In the code we create the
mpls_interface as part of the "ILM" add (if it doesn't already exist).
We also create the mpls_interface when we set a labelspace (if it doesn't
already exist). Maybe the mpls_interface that is create as part of a "ILM"
add is corrupt?

On Thu, Mar 25, 2004 at 10:01:23PM +0100, Ramon Casellas wrote:
> On Thu, 25 Mar 2004, Josef Perlinger wrote:
> 
> 
> MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on 
> if. w/o labelspace
> MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
> 
> 
> This usually means that you recived a packet on an interface that was not 
> "MPLS enabled", that is, the labelspace is -1. So the kernel network stack
> actually hands over the frame to the MPLS module, but it has not allocated 
> the required data structs for the incoming interface so it drops the 
> packet...
> 
> 
> Could you please try setting a labelspace (let it be 0) for the used 
> interfaces and try again? I *do* see that the is an IOCTL to set the 
> labelspace, but could you please check after that it has really been set?
> Maybe you spot a bug..
> 
> PS: I will add some code to mpls_input so we get the name of the interface 
> displayed...
> 
> 
> thanks,
> Ramon
> 
> 
> 
> 
> > Ping from UML1 to UML2
> 
> ...
> > MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace 
> > MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter
> > MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit
> ...
> > MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
> > MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
> > 00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
> > 5400004000400122a70b0001010b00010208007acc130100004063214800091d7b08090a0b0c
> > 0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
> > 3334353637}00
> > MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
> > if. w/o labelspace
> > MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
> 
> 
> 
> > Something isn't implemented in here
> 
> Most probably :)
> 
> R.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] MPLS+IPv6

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

Did you build the kernel fro a patch?  It so, I can send you a patch that
adds some debugging.  Otherwise I will have to build a custom RPM for you.

On Fri, Mar 26, 2004 at 03:47:52PM +0000, Bruno Jorge Marcelino wrote:
> 
> I've checked dmesg and seems the packets aren't entering the MPLS stack...
> 
> The only messages that I have are from (modified) mplsadm2 commands:
> 	mplsadm2 -d
> 	mplsadm2 -A -O 0 -o push.gen.56.set.eth1.ipv6.$NET::65
> 
> MPLSADM mplsadm6.c:696:main: Out segment input: 0
> MPLSADM mplsadm6.c:692:main: Out instr input:
> push.gen.56.set.eth1.ipv6.fc97:86d5:b2ed::65
> Key: 0x00000002
> Out Segment add: Success
> MPLSADM mplsadm6.c:296:fill_instructions: Instruction: push
> MPLSADM mplsadm6.c:233:fill_label: Label type: gen
> MPLSADM mplsadm6.c:296:fill_instructions: Instruction: set
> MPLSADM mplsadm6.c:185:parse_nh_info: eth1
> MPLSADM mplsadm6.c:186:parse_nh_info: fc97:86d5:b2ed::65
> MPLSADM mplsadm6.c:208:parse_nh_info: Nexthop protocol: ipv6
> MPLSADM mplsadm6.c:600:fill_instructions: Length: 2
> Out Instr: Success
> 
> 	output of dmesg:
> 
> MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847
> MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
> MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE moi-2
> MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
> MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864
> MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
> MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
> MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
> MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
> MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
> MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(c1663bc0)
> MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
> MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-00-PUSH
> MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
> MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-01-SET
> MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
> 
> routerPC5:/usr/src/mpls-linux/utils# cat /proc/net/mpls/out
> MOI Key:0x00000002 Instruction Set
> PUSH PUSH(gen 56)
> SET SET(eth1,0.0.0.0)
> 
> I first used
> 	ip6tables -A OUTPUT -d $NET:2::/64 -j spec_nh --spec_nh 0x8847:0x2
> and then
> 	ip -f inet6 route add $NET:2::/64 dev eth1 spec_nh 0x8847 0x2
> 
> and none of the above commands worked! The packets aren't using MPLS to leave the router...
> 
> I have an IPv6 network with 5 PC's running debian testing/unstable, kernel
> 2.6.2+mpls-1.922.
> 
> Can you help me resolve my problem/improving IPv6 support in
> MPLS and ldp-portable?
> 
> I can make some changes in the code, but I you need to point me on what to do!
> 
> Regarding the changes in mplsadm2, you can see the parsing of commands
> has changed from ":" to "." (because in IPv6, separator is now ":"). This
> conflicts with IPv4 addresses...
> 
> Bruno
> 
> 
> On Wed, 24 Mar 2004, James R. Leu wrote:
> 
> > On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> > > Hi there!
> > >
> > > I'm doing some research on MPLS and IPv6 for my master thesis...
> > >
> > > Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!
> >
> > I will be releasing 1.930 soon, with support for MPLS ICMP and better
> > internal locking and referencing.
> >
> > > I've changed mplsadm2 to work with IPv6 address, and by looking at
> > > debugging messages, I think that's all OK (no errors are found).
> >
> > Please send me a patch, I'd like to include support for IPv6.
> >
> > > Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> > > with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).
> >
> > This should be an easy to fix.
> >
> > > But I have a problem when binding FEC to LSP (with mpls patched
> > > ip6tables): it isn't working! The traffic is not leaving the router using
> > > mpls.
> > >
> > > Do you have any idea on the problem?
> >
> > Did you check the MPLS kernel debug?  (execute the command 'dmesg').
> > Did the packets ever enter the MPLS stack?  What command did you
> > use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
> > to test with (nor do I know how to set one up).
> >
> > Have you tried 'ip'?
> >
> > ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>
> >
> > > What's the status on porting ldp-portable to 2.6 kernel with IPv6?
> >
> > ldp-portable has the structures to handle IPv6, but no code has been written
> > to handle IPv6.  I would be glad to point you to the places I know that
> > would be affected by IPv6.
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] MPLS+IPv6

[Bruno J. M. <bj...@me...>]

I've checked dmesg and seems the packets aren't entering the MPLS stack...

The only messages that I have are from (modified) mplsadm2 commands:
	mplsadm2 -d
	mplsadm2 -A -O 0 -o push.gen.56.set.eth1.ipv6.$NET::65

MPLSADM mplsadm6.c:696:main: Out segment input: 0
MPLSADM mplsadm6.c:692:main: Out instr input:
push.gen.56.set.eth1.ipv6.fc97:86d5:b2ed::65
Key: 0x00000002
Out Segment add: Success
MPLSADM mplsadm6.c:296:fill_instructions: Instruction: push
MPLSADM mplsadm6.c:233:fill_label: Label type: gen
MPLSADM mplsadm6.c:296:fill_instructions: Instruction: set
MPLSADM mplsadm6.c:185:parse_nh_info: eth1
MPLSADM mplsadm6.c:186:parse_nh_info: fc97:86d5:b2ed::65
MPLSADM mplsadm6.c:208:parse_nh_info: Nexthop protocol: ipv6
MPLSADM mplsadm6.c:600:fill_instructions: Length: 2
Out Instr: Success

	output of dmesg:

MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847
MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE moi-2
MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864
MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(c1663bc0)
MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-00-PUSH
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-01-SET
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit

routerPC5:/usr/src/mpls-linux/utils# cat /proc/net/mpls/out
MOI Key:0x00000002 Instruction Set
PUSH PUSH(gen 56)
SET SET(eth1,0.0.0.0)

I first used
	ip6tables -A OUTPUT -d $NET:2::/64 -j spec_nh --spec_nh 0x8847:0x2
and then
	ip -f inet6 route add $NET:2::/64 dev eth1 spec_nh 0x8847 0x2

and none of the above commands worked! The packets aren't using MPLS to leave the router...

I have an IPv6 network with 5 PC's running debian testing/unstable, kernel
2.6.2+mpls-1.922.

Can you help me resolve my problem/improving IPv6 support in
MPLS and ldp-portable?

I can make some changes in the code, but I you need to point me on what to do!

Regarding the changes in mplsadm2, you can see the parsing of commands
has changed from ":" to "." (because in IPv6, separator is now ":"). This
conflicts with IPv4 addresses...

Bruno


On Wed, 24 Mar 2004, James R. Leu wrote:

> On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> > Hi there!
> >
> > I'm doing some research on MPLS and IPv6 for my master thesis...
> >
> > Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!
>
> I will be releasing 1.930 soon, with support for MPLS ICMP and better
> internal locking and referencing.
>
> > I've changed mplsadm2 to work with IPv6 address, and by looking at
> > debugging messages, I think that's all OK (no errors are found).
>
> Please send me a patch, I'd like to include support for IPv6.
>
> > Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> > with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).
>
> This should be an easy to fix.
>
> > But I have a problem when binding FEC to LSP (with mpls patched
> > ip6tables): it isn't working! The traffic is not leaving the router using
> > mpls.
> >
> > Do you have any idea on the problem?
>
> Did you check the MPLS kernel debug?  (execute the command 'dmesg').
> Did the packets ever enter the MPLS stack?  What command did you
> use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
> to test with (nor do I know how to set one up).
>
> Have you tried 'ip'?
>
> ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>
>
> > What's the status on porting ldp-portable to 2.6 kernel with IPv6?
>
> ldp-portable has the structures to handle IPv6, but no code has been written
> to handle IPv6.  I would be glad to point you to the places I know that
> would be affected by IPv6.
>
> --
> James R. Leu
> jl...@mi...
>

Re: AW: [mpls-linux-general] Ping Problem

[Ramon C. <cas...@in...>]

On Fri, 26 Mar 2004, Josef Perlinger wrote:

> Hello Ramon,
> --> yeah the ping was fine :-)
>
> My Commands:
>
> mplsadm2 -L eth1:0
> mplsadm2 -A -O 0
> mplsadm2 -O 0x2 -o push:gen:17:set:eth1:ipv4:11.0.1.1
> ip route add 11.0.1.1/32 via 11.0.1.1 spec_nh 0x8847 0x2
> mplsadm2 -A -I gen:16:0;
> mplsadm2 -L eth1:0
>

> Is this normal, that you have to enter the mplsadm2 -L eth1:0 command before
> all others?

Yes, at least, before any set command that uses the interface. What we
usually do is to set them at the beginning.

Glad it worked

Regards,
Ramon

Re: [mpls-linux-general] Regd routing daemons and OSPF

[Ramon C. <cas...@in...>]

On Thu, 25 Mar 2004, kavitha ganapa wrote:

>
> Hi All,
>
> We have OSPF daemon running on the MPLS network to find just the shortest
> path from one node to another. What if I want to find different set of
> paths than what OSPF finds. How do I go about it?


Hi Kavitha,

You could start taking a look at OSPF TE extensions (which basically add
opaque LSAs) to redistribute link state information like max bandwidth and
then use OSPFAPI (included in the software distribution) to perform the
path computation. This means hat you need to code in C, and that you will
reuse an OSPF library, but it should work. I plan to work on this soon, so
keep in touvh with the list :)

Regards,
Ramon

[mpls-linux-general] Regd routing daemons and OSPF

[kavitha g. <kg...@en...>]

Hi All,

We have OSPF daemon running on the MPLS network to find just the shortest 
path from one node to another. What if I want to find different set of 
paths than what OSPF finds. How do I go about it?

Thanks in advance,
GK

AW: [mpls-linux-general] Ping Problem

[Josef P. <jo...@pe...>]

Hello Ramon,

I've tried to setup the Labelspace explicit f=FCr the used interfaces as =
you
suggested with the command:
mplsadm2 -L eth1:0
--> SUCCESS... :-)=20

but it didn't really work because
the cat /proc/net/mpls/labelspaces  always returned me a -1 for my eth1
interface=20

---> Debug MSG  for eth1:0
MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace=20
MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter

--> for eth2:0 - a not mpls configured interface the labelspace set
worked....

MPLS DEBUG net/mpls/mpls_if.c:190:__mpls_set_labelspace: Set labelspace =
for
eth2 to 0
MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit


So I rebooted my 2 UMLs then and entered the command for setting =
labelspace
before all other mplsadm commands=20
--> yeah the ping was fine :-)

My Commands:

mplsadm2 -L eth1:0
mplsadm2 -A -O 0=20
mplsadm2 -O 0x2 -o push:gen:17:set:eth1:ipv4:11.0.1.1=20
ip route add 11.0.1.1/32 via 11.0.1.1 spec_nh 0x8847 0x2=20
mplsadm2 -A -I gen:16:0;=20
mplsadm2 -L eth1:0


Is this normal, that you have to enter the mplsadm2 -L eth1:0 command =
before
all others?


best regards

josef




-----Urspr=FCngliche Nachricht-----
Von: mpl...@li...
[mailto:mpl...@li...] Im Auftrag von =
Ramon
Casellas
Gesendet: Donnerstag, 25. M=E4rz 2004 22:01
An: Josef Perlinger
Cc: mpl...@li...
Betreff: Re: [mpls-linux-general] Ping Problem

On Thu, 25 Mar 2004, Josef Perlinger wrote:


MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv =
on
if. w/o labelspace MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv:
exit(DROP)


This usually means that you recived a packet on an interface that was =
not=20
"MPLS enabled", that is, the labelspace is -1. So the kernel network =
stack
actually hands over the frame to the MPLS module, but it has not =
allocated=20
the required data structs for the incoming interface so it drops the=20
packet...


Could you please try setting a labelspace (let it be 0) for the used=20
interfaces and try again? I *do* see that the is an IOCTL to set the=20
labelspace, but could you please check after that it has really been =
set?
Maybe you spot a bug..

PS: I will add some code to mpls_input so we get the name of the =
interface=20
displayed...


thanks,
Ramon




> Ping from UML1 to UML2

...
> MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace=20
> MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter
> MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit
...
> MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
> MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=3D30 =
tailroom=3D1418
>
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450=
000
>
5400004000400122a70b0001010b00010208007acc130100004063214800091d7b08090a0=
b0c
>
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303=
132
> 3334353637}00
> MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet =
recv on
> if. w/o labelspace
> MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)



> Something isn't implemented in here

Most probably :)

R.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
mpls-linux-general mailing list
mpl...@li...
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

Re: [mpls-linux-general] Ping Problem

[Ramon C. <cas...@in...>]

On Thu, 25 Mar 2004, Josef Perlinger wrote:


MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on 
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)


This usually means that you recived a packet on an interface that was not 
"MPLS enabled", that is, the labelspace is -1. So the kernel network stack
actually hands over the frame to the MPLS module, but it has not allocated 
the required data structs for the incoming interface so it drops the 
packet...


Could you please try setting a labelspace (let it be 0) for the used 
interfaces and try again? I *do* see that the is an IOCTL to set the 
labelspace, but could you please check after that it has really been set?
Maybe you spot a bug..

PS: I will add some code to mpls_input so we get the name of the interface 
displayed...


thanks,
Ramon




> Ping from UML1 to UML2

...
> MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace 
> MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter
> MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit
...
> MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
> MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
> 00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
> 5400004000400122a70b0001010b00010208007acc130100004063214800091d7b08090a0b0c
> 0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
> 3334353637}00
> MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
> if. w/o labelspace
> MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)



> Something isn't implemented in here

Most probably :)

R.

[mpls-linux-general] Ping Problem

[Josef P. <jo...@pe...>]

Ping from UML1 to UML2

dmesg1:

MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
MPLS DEBUG net/mpls/mpls_output.c:135:mpls_output2: enter
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode PUSH
MPLS DEBUG net/mpls/mpls_opcode.c:106:mpls_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:130:mpls_push: using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:134:mpls_push: done using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:181:mpls_push: exit
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode SET
MPLS DEBUG net/mpls/mpls_output.c:55:mpls_send: output device = eth1
MPLS DEBUG net/mpls/mpls_opcode.c:41:mpls_finish: enter
MPLS DEBUG net/mpls/mpls_opcode.c:54:mpls_finish: exit
MPLS mpls_skb_dump: from eth1 with len 88 (296)headroom=16 tailroom=24
3c343e4d61722032352031383a31333a{000101404500005400034000400122a40b000101#0b
00010208002d01130103004063214b000b684108090a0b0c0d0e0f101112131415161718191a
1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637}30
MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
MPLS DEBUG net/mpls/mpls_output.c:135:mpls_output2: enter
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode PUSH
MPLS DEBUG net/mpls/mpls_opcode.c:106:mpls_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:130:mpls_push: using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:134:mpls_push: done using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:181:mpls_push: exit
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode SET
MPLS DEBUG net/mpls/mpls_output.c:55:mpls_send: output device = eth1
MPLS DEBUG net/mpls/mpls_opcode.c:41:mpls_finish: enter
MPLS DEBUG net/mpls/mpls_opcode.c:54:mpls_finish: exit
MPLS mpls_skb_dump: from eth1 with len 88 (296)headroom=16 tailroom=24
3c343e4d61722032352031383a31333a{000101404500005400044000400122a30b000101#0b
00010208002c9c130104004063214c000b67a508090a0b0c0d0e0f101112131415161718191a
1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637}30
MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
MPLS DEBUG net/mpls/mpls_output.c:135:mpls_output2: enter
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode PUSH
MPLS DEBUG net/mpls/mpls_opcode.c:106:mpls_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:130:mpls_push: using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:134:mpls_push: done using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:181:mpls_push: exit
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode SET
MPLS DEBUG net/mpls/mpls_output.c:55:mpls_send: output device = eth1
MPLS DEBUG net/mpls/mpls_opcode.c:41:mpls_finish: enter
MPLS DEBUG net/mpls/mpls_opcode.c:54:mpls_finish: exit
MPLS mpls_skb_dump: from eth1 with len 88 (296)headroom=16 tailroom=24
3c343e4d61722032352031383a31333a{000101404500005400004000400122a70b000101#0b
0001020800e82916010000406321da0008ac8c08090a0b0c0d0e0f101112131415161718191a
1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637}30
MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
MPLS DEBUG net/mpls/mpls_output.c:135:mpls_output2: enter
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode PUSH
MPLS DEBUG net/mpls/mpls_opcode.c:106:mpls_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:130:mpls_push: using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:134:mpls_push: done using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:181:mpls_push: exit
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode SET
MPLS DEBUG net/mpls/mpls_output.c:55:mpls_send: output device = eth1
MPLS DEBUG net/mpls/mpls_opcode.c:41:mpls_finish: enter
MPLS DEBUG net/mpls/mpls_opcode.c:54:mpls_finish: exit
MPLS mpls_skb_dump: from eth1 with len 88 (296)headroom=16 tailroom=24
3c343e4d61722032352031383a31353a{000101404500005400014000400122a60b000101#0b
000102080081bd16010100406321db000a11f608090a0b0c0d0e0f101112131415161718191a
1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637}30
MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
MPLS DEBUG net/mpls/mpls_output.c:135:mpls_output2: enter
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode PUSH
MPLS DEBUG net/mpls/mpls_opcode.c:106:mpls_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:130:mpls_push: using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:134:mpls_push: done using tailroom
MPLS DEBUG net/mpls/mpls_opcode.c:181:mpls_push: exit
MPLS DEBUG net/mpls/mpls_output.c:148:mpls_output2: opcode SET
MPLS DEBUG net/mpls/mpls_output.c:55:mpls_send: output device = eth1
MPLS DEBUG net/mpls/mpls_opcode.c:41:mpls_finish: enter
MPLS DEBUG net/mpls/mpls_opcode.c:54:mpls_finish: exit
MPLS mpls_skb_dump: from eth1 with len 88 (296)headroom=16 tailroom=24
3c343e4d61722032352031383a31353a{000101404500005400024000400122a50b000101#0b
0001020800864016010200406321dc000a0c7208090a0b0c0d0e0f101112131415161718191a
1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637}30
MPLS DEBUG net/mpls/mpls_output.c:66:mpls_send: using hh
MPLS DEBUG net/mpls/mpls_output.c:79:mpls_send: mpls_send result 0
MPLS DEBUG net/mpls/mpls_output.c:182:mpls_output2: exit
Something isn't implemented in here

DMESG UML2:


MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847 
MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE
moi-2
MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864

MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(a18b19e0)
MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering
OP-00-PUSH
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering
OP-01-SET
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_ioctls.c:132:mpls_ioctl: IOCTL Add ILM 35850 
MPLS DEBUG net/mpls/mpls_in_info.c:463:mpls_add_in_label: enter
MPLS DEBUG net/mpls/mpls_in_info.c:293:mpls_destroy_in_instrs: enter
MPLS DEBUG net/mpls/mpls_utils.c:557:mpls_instrs_unregister: enter
MPLS DEBUG net/mpls/mpls_utils.c:563:mpls_instrs_unregister: exit
MPLS DEBUG net/mpls/mpls_in_info.c:296:mpls_destroy_in_instrs: exit
MPLS DEBUG net/mpls/mpls_in_info.c:322:mpls_set_in_instrs: built: 2 for MII
mii-gen:16:0-65537
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering
OP-00-POP
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering
OP-01-PEEK
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_in_info.c:557:mpls_add_in_label: exit
MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace 
MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter
MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400004000400122a70b0001010b00010208007acc130100004063214800091d7b08090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400014000400122a60b0001010b0001020800e0681301010040632149000ab6dc08090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400024000400122a50b0001010b0001020800547d130102004063214a000b41c608090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400034000400122a40b0001010b00010208002d01130103004063214b000b684108090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400044000400122a30b0001010b00010208002c9c130104004063214c000b67a508090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400004000400122a70b0001010b0001020800e82916010000406321da0008ac8c08090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400014000400122a60b0001010b000102080081bd16010100406321db000a11f608090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
5400024000400122a50b0001010b0001020800864016010200406321dc000a0c7208090a0b0c
0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
3334353637}00
MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)
Something isn't implemented in here

Josef Perlinger
Student FH-Sbg/TKS 2000
Tel.: +43 664 4024906
ICQ: 166227595
Email: jo...@pe...

Re: [mpls-linux-general] Problems pinging vom Ingress to Egress

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

It looks like it's configured correctly.  After trying to send a few
ping packets do a 'dmesg' on each and send the output to the list.

On Thu, Mar 25, 2004 at 06:30:34PM +0100, Josef Perlinger wrote:
> Hi to all,
> 
> I've tried jLeu's uml testbed and wanted to come into it with the first
> simple example of an mpls LSP.
> 
> UML1:eth1 ----- eth1:UML2
> ip: 11.0.1.1	ip: 11.0.1.2
> 
> before entering the MPLS Commands the ipv4 ping from UML1 to UML2 and vice
> versa works normally.
> 
> If I setup the LSP only in one Direction for example from uml1 to uml2 (I
> don't enter the ip route add . command on uml2 ) everthing works fine.
> But I also want to have the ping replies encapsulated..
> 
> After set up the route to the back lsp in uml2  I can't ping the other uml
> and vice versa...
> 
> 
> The following comands I've entered
> 
> UML1:
> mplsadm2 -A -O 0;
> mplsadm2 -O 0x2 -o push:gen:16:set:eth1:ipv4:11.0.1.2
> ip route add 11.0.1.2/32 via 11.0.1.2 spec_nh 0x8847 0x2
> mplsadm2 -A -I gen:17:0
> mplsadm2 -L eth1:0
> 
> 
> 
> UML2:
> mplsadm2 -A -O 0
> mplsadm2 -O 0x2 -o push:gen:17:set:eth1:ipv4:11.0.1.1
> ip route add 11.0.1.1/32 via 11.0.1.1 spec_nh 0x8847 0x2
> mplsadm2 -A -I gen:16:0;
> mplsadm2 -L eth1:0
> 
> -----------
> ip route show UML1:
> 11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x00000002 
> 11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.1 
> 10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.14.2.105 
> 
> 
> ip route show UML2:
> 11.0.1.1 via 11.0.1.1 dev eth1 spec_nh 0x8847 0x00000002 
> 11.0.2.0/24 dev eth2  proto kernel  scope link  src 11.0.2.2 
> 11.0.3.0/24 dev eth3  proto kernel  scope link  src 11.0.3.2 
> 11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.2 
> 10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.14.2.205 
> 
> 
> Perhaps anyone can find out what I'm doing wrong?
> 
> thx, in advance
> josef
> 
> Josef Perlinger
> Student FH-Sbg/TKS 2000
> Tel.: +43 664 4024906
> ICQ: 166227595
> Email: jo...@pe...
> 
> 

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

[mpls-linux-general] Problems pinging vom Ingress to Egress

[Josef P. <jo...@pe...>]

Hi to all,

I've tried jLeu's uml testbed and wanted to come into it with the first
simple example of an mpls LSP.

UML1:eth1 ----- eth1:UML2
ip: 11.0.1.1	ip: 11.0.1.2

before entering the MPLS Commands the ipv4 ping from UML1 to UML2 and vice
versa works normally.

If I setup the LSP only in one Direction for example from uml1 to uml2 (I
don't enter the ip route add . command on uml2 ) everthing works fine.
But I also want to have the ping replies encapsulated..

After set up the route to the back lsp in uml2  I can't ping the other uml
and vice versa...


The following comands I've entered

UML1:
mplsadm2 -A -O 0;
mplsadm2 -O 0x2 -o push:gen:16:set:eth1:ipv4:11.0.1.2
ip route add 11.0.1.2/32 via 11.0.1.2 spec_nh 0x8847 0x2
mplsadm2 -A -I gen:17:0
mplsadm2 -L eth1:0



UML2:
mplsadm2 -A -O 0
mplsadm2 -O 0x2 -o push:gen:17:set:eth1:ipv4:11.0.1.1
ip route add 11.0.1.1/32 via 11.0.1.1 spec_nh 0x8847 0x2
mplsadm2 -A -I gen:16:0;
mplsadm2 -L eth1:0

-----------
ip route show UML1:
11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x00000002 
11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.1 
10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.14.2.105 


ip route show UML2:
11.0.1.1 via 11.0.1.1 dev eth1 spec_nh 0x8847 0x00000002 
11.0.2.0/24 dev eth2  proto kernel  scope link  src 11.0.2.2 
11.0.3.0/24 dev eth3  proto kernel  scope link  src 11.0.3.2 
11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.2 
10.0.0.0/8 dev eth0  proto kernel  scope link  src 10.14.2.205 


Perhaps anyone can find out what I'm doing wrong?

thx, in advance
josef

Josef Perlinger
Student FH-Sbg/TKS 2000
Tel.: +43 664 4024906
ICQ: 166227595
Email: jo...@pe...

Re: [mpls-linux-general] MPLS+IPv6

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

On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> Hi there!
> 
> I'm doing some research on MPLS and IPv6 for my master thesis...
> 
> Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!

I will be releasing 1.930 soon, with support for MPLS ICMP and better
internal locking and referencing.

> I've changed mplsadm2 to work with IPv6 address, and by looking at
> debugging messages, I think that's all OK (no errors are found).

Please send me a patch, I'd like to include support for IPv6.

> Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).

This should be an easy to fix.

> But I have a problem when binding FEC to LSP (with mpls patched
> ip6tables): it isn't working! The traffic is not leaving the router using
> mpls.
> 
> Do you have any idea on the problem?

Did you check the MPLS kernel debug?  (execute the command 'dmesg').
Did the packets ever enter the MPLS stack?  What command did you
use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
to test with (nor do I know how to set one up).

Have you tried 'ip'?

ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>

> What's the status on porting ldp-portable to 2.6 kernel with IPv6?

ldp-portable has the structures to handle IPv6, but no code has been written
to handle IPv6.  I would be glad to point you to the places I know that
would be affected by IPv6.

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

[mpls-linux-general] MPLS+IPv6

[Bruno J. M. <bj...@me...>]

Hi there!

I'm doing some research on MPLS and IPv6 for my master thesis...

Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!

I've changed mplsadm2 to work with IPv6 address, and by looking at
debugging messages, I think that's all OK (no errors are found).

Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).

But I have a problem when binding FEC to LSP (with mpls patched
ip6tables): it isn't working! The traffic is not leaving the router using
mpls.

Do you have any idea on the problem?


What's the status on porting ldp-portable to 2.6 kernel with IPv6?

Thank's in advanced,
Bruno Marcelino

Re: [mpls-linux-general] Problems with LDP

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

There are a couple of problems with your setup:
-ECMP - the LDP RFC say that ECMP is not specified, and is up to each
 implementation as to how to deal with it, my implementation chooses not
 to deal with it and thus will not work right in the presence of ECMP
-there are many bug in the version of ldp-portable you are using.  I have
 a lot of fixes in my development tree, but I have not released them yet.

On Tue, Mar 23, 2004 at 10:19:03AM -0800, priya Srinivasan wrote:
> haii
> 
>     I have this problem with lsp setup. I have a
> simple network setup as shown below.
> 
>           ---- LSR1 ----
>          |              |
> Host1 --- LER1          LER2--- Host2
>          |              |
>           ---- LSR2 ----
> 
> I have a IP to FEC binding in LER2 and the routing
> table and mpls_out contents are as below (which is
> fine and as expected)
> 
> root@localhost LER2]# ip route sh
> 10.0.4.0/24 dev eth1  scope link
> 10.0.1.0/24 via 10.0.3.1 dev eth2 lsp 0x3  proto zebra
> metric 20 equalize
> 10.0.3.0/24 dev eth2  scope link
> 10.0.12.0/24 dev eth0  scope link
> 127.0.0.0/8 dev lo  scope link
> 
> [root@localhost LER2]# cat /proc/net/mpls_out
> 0x00000003 68500/5753838/0 2 PUSH(gen 10002)
> SET(eth2,10.0.3.1)
> 0x00000004 447/36612/0 1 PUSH(gen 10005)
> SET(eth2,10.0.3.1)
> 0x00000008 15/738/0 1 PUSH(gen 10020)
> SET(eth2,10.0.3.1)
> 
> BUT, I donot have a similar IP--FEC binding at LER1.
> The ip route show and the cat /proc/net/mpls_out
> commands show the following output (which packets take
> which LSPs-- 0x1a or 0x1b in mpls_out below)
> 
> [root@localhost LER1]# ip route sh
> 10.0.4.0/24 via 10.0.2.2 dev eth2  proto zebra  metric
> 20 equalize
> 10.0.1.0/24 dev eth1  scope link
> 10.0.2.0/24 dev eth2  scope link
> 10.0.3.0/24 via 10.0.1.2 dev eth1  proto zebra  metric
> 20 equalize
> 10.0.12.0/24 via 10.0.1.2 dev eth1  proto zebra 
> metric 30 equalize
> 10.0.11.0/24 dev eth0  scope link
> 127.0.0.0/8 dev lo  scope link
> 
> [root@localhost LER1]# cat /proc/net/mpls_out
> 0x0000001a 2845/238980/0 2 PUSH(gen 10109)
> SET(eth1,10.0.1.2)
> 0x0000001b 0/0/0 1 PUSH(gen 10111) SET(eth1,10.0.1.2)
> 
> 
> What could be the problem? The FEC binding at LER2 was
> automatic but not at the LER1. I just enabled the
> interfaces for LER1, LSR1 , LSR2, LER2 on the mpls
> network using "mpls ldp". 
>     Also please let me know if there is any
> documentation that could explain as to how the ldp for
> mpls-linux sets up labels for all the networks in the
> LSRs and LERs.
>     Thanks in advance
> Praveen
> 
> 
> 
> Do you Yahoo!?
> Yahoo! Finance Tax Center - File online. File on time.
-- 
James R. Leu
jl...@mi...