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

[mpls-linux-general] LDP portable

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

Bones;

I use quagga-mpls;

In packet ldp-portable I see that there is a folder RSVP. What mpls-linux
use the protocol RSVP/RSVP-TE ?? And can use LDP/LDP-CR signally?

And finally, there is any utility or command for monitiring the LSP? or
for know when my LSP failed?

I will know this questions for create a backup of LSP. Any idea??

thank you!!!

[mpls-linux-general] LDP deamon

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

Hello,

I have to mini-LAN with 5 computers with FC3_MPLS and quagga_mpls installed.

The first I execute zebra deamon, and ripd.

My traffic of packets run correctly on mpls, but I configure the LSP
manually.

After I run ldp deamon.

How use Label Dynamic protocol? I run the deamon ldpd on every computer
and the deamon ldp find the others computers. The deamon assign
incoming_labels (insegments) automatic. But the outsegments labels and
forwards I create manually?

When I create on outsegments in Ingress LER and type the next line :

ip route 192.168.4.0/16 gen 20 nexthop eth4 192.168.0.2 -- > my deamons
zebra and ldpd will close (failed).

How chosse LSP on LDP?

Sorry for my English

atent. Miquel Casanovas

RE: [mpls-linux-general] Mpls qos and segfault

[<ram...@wi...>]

Hi

I have chosen both MPLS support and MPLS IP supportand spec_nh also.

Regards
Ramesh.s

-----Original Message-----
From: Vincent Untz [mailto:vin...@im...]=20
Sent: Thursday, May 05, 2005 1:27 PM
To: Ramesh Selvaraj (WT01 - TELECOM SOLUTIONS)
Cc: mpl...@li...
Subject: Re: [mpls-linux-general] Mpls qos and segfault

Hi,

Le jeudi 05 mai 2005 =E0 08:47 +0530, ram...@wi... a =
=E9crit :
> i got segmentation fault while using mpls tool.
> i added labelspace as follows
>=20
> mpls labelspace add dev eth0 labelspace 0
>=20
> mpls labelspace show
>=20
> shows the labelspaces. after that the following ilm command gives=20
> segfault.
>=20
> mpls ilm add label gen 1000 labelspace 0
>=20
> dmesg says
>=20
>=20
> MPLS DEBUG net/mpls/mpls_ilm.c:146:mpls_ilm_dst_alloc: *Unable to find =

> protocol driver for 'AF_INET'* MPLS DEBUG
> net/mpls/mpls_ilm.c:157:mpls_ilm_dst_alloc: exit Unable to handle=20
> kernel NULL pointer dereference at virtual address 00000000  printing =
eip:
> c0322e34
> *pde =3D 00000000
> Oops: 0000 [#1]
> ..............
> ..................
>=20
> now what is the problem, how to rectify that error *Unable to find=20
> protocol driver for 'AF_INET'

Did you compile the MPLS IP support in the kernel? Or just the MPLS =
support?

IIRC, you need to activate MPLS support and then MPLS IP support when =
you configure the kernel (it's not done by default).

Vincent

--
Les gens heureux ne sont pas press=E9s.

Re: [mpls-linux-general] Mpls qos and segfault

[Vincent U. <vin...@im...>]

Hi,

Le jeudi 05 mai 2005 =C3=A0 08:47 +0530, ram...@wi... a =C3=A9=
crit :
> i got segmentation fault while using mpls tool.
> i added labelspace as follows
>=20
> mpls labelspace add dev eth0 labelspace 0
>=20
> mpls labelspace show=20
>=20
> shows the labelspaces. after that the following ilm command gives
> segfault.
>=20
> mpls ilm add label gen 1000 labelspace 0
>=20
> dmesg says=20
>=20
>=20
> MPLS DEBUG net/mpls/mpls_ilm.c:146:mpls_ilm_dst_alloc: *Unable to find
> protocol driver for 'AF_INET'* MPLS DEBUG
> net/mpls/mpls_ilm.c:157:mpls_ilm_dst_alloc: exit Unable to handle kernel
> NULL pointer dereference at virtual address 00000000  printing eip:
> c0322e34
> *pde =3D 00000000
> Oops: 0000 [#1]
> ..............
> ..................
>=20
> now what is the problem, how to rectify that error *Unable to find
> protocol driver for 'AF_INET'

Did you compile the MPLS IP support in the kernel? Or just the MPLS
support?

IIRC, you need to activate MPLS support and then MPLS IP support when
you configure the kernel (it's not done by default).

Vincent

--=20
Les gens heureux ne sont pas press=C3=A9s.

[mpls-linux-general] RTNETLINK answers: Invalid argument

[Jiun-Shian H. <as...@sy...>]

Hi,
    I build iproute2 tools (1.946a) by armeb-linux-uclibc 
(from http://buildroot.uclibc.org,  XScale big endian).

but when I run "mpls nhlfe add key 0" I got error

RTNETLINK answers: Invalid argument


and "mpls nhlfe show" got strange error

NHLFE entry key 0x00000000 mtu 1702127664 
         (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000000 mtu 1819213824 
         (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000000 mtu 1685417325 propagate_ttl 
         (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000000 mtu 1953853036 propagate_ttl 
         (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000000 mtu 1735550256 
         (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000000 mtu 1936290864 
         (0 bytes, 0 pkts, 0 dropped)


"mpls labelspace add dev eth0 labelspace 0" got error

RTNETLINK answers: Cannot assign requested address


But other tools like iptables, ip work well.
I ever built tools with arm (little-endian) and it works find.
Could anyone kind give me some hints ?

Best regards,
H.

[mpls-linux-general] Mpls qos and segfault

[<ram...@wi...>]

Hi,

I have two questions:

1)---------

I downloaded kernel-2.6.9 and mpls-linux. I patched the kernel for mpls
support and iproute2 which gives mpls and tc. Now I booted with mpls
support. I want to know whether this iproute2 supports mpls Qos.

2)---------

i got segmentation fault while using mpls tool.
i added labelspace as follows

mpls labelspace add dev eth0 labelspace 0

mpls labelspace show=20

shows the labelspaces. after that the following ilm command gives
segfault.

mpls ilm add label gen 1000 labelspace 0

dmesg says=20


MPLS DEBUG net/mpls/mpls_ilm.c:146:mpls_ilm_dst_alloc: *Unable to find
protocol driver for 'AF_INET'* MPLS DEBUG
net/mpls/mpls_ilm.c:157:mpls_ilm_dst_alloc: exit Unable to handle kernel
NULL pointer dereference at virtual address 00000000  printing eip:
c0322e34
*pde =3D 00000000
Oops: 0000 [#1]
..............
..................

now what is the problem, how to rectify that error *Unable to find
protocol driver for 'AF_INET'

Thanks in advance

regards
Ramesh.s

Re: [mpls-linux-general] Possible Iptables --spec_nh bug

[Josdeyvi R. <jr...@uo...>]

Hi,
Since you will sync the iptables, could you please give a look at the out=
put
of iptables-save (same example, see bellow)?

What means 0x8847:208x? Wrong format, no?

Will you produce a new RPM too?

Thank you,

Josdeyvi


[root@localhost ~]# iptables-save -c
# Generated by iptables-save v1.2.11 on Tue May  3 20:17:08 2005
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [1730:1091850]
:RH-Firewall-1-INPUT - [0:0]
[1722:1389930] -A INPUT -j RH-Firewall-1-INPUT
[0:0] -A FORWARD -j RH-Firewall-1-INPUT
[0:0] -A OUTPUT -d 10.0.1.2 -j spec_nh --spec_nh 0x8847:208x
[1016:1027145] -A RH-Firewall-1-INPUT -i lo -j ACCEPT
[0:0] -A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type any
-j ACCEPT
[0:0] -A RH-Firewall-1-INPUT -p ipv6-crypt -j ACCEPT
[0:0] -A RH-Firewall-1-INPUT -p ipv6-auth -j ACCEPT
[11:1127] -A RH-Firewall-1-INPUT -d 224.0.0.251 -p udp -m
udp --dport 5353 -j ACCEPT
[0:0] -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
[694:361580] -A RH-Firewall-1-INPUT -m state --state
RELATED,ESTABLISHED -j ACCEPT
[1:78] -A RH-Firewall-1-INPUT -j REJECT --reject-with
icmp-host-prohibited
COMMIT
# Completed on Tue May  3 20:17:08 2005

----- Original Message -----=20
From: "Ramon Casellas" <cas...@in...>
To: "jrussi" <jr...@uo...>
Cc: "mpls-linux-general" <mpl...@li...>
Sent: Monday, May 02, 2005 3:02 PM
Subject: Re: [mpls-linux-general] Possible Iptables --spec_nh bug


On Mon, 2 May 2005, jrussi wrote:

> Leu,
>
> You see the output from iptables -L below? Shouldn't it be
> "set spec_nh 0x8847" instead of "set spec_nh 0x4788"?

possibly there is a missing htons in the iptables patch. I'll sync the
source code tomorrow

Regards,
R.


>
> Please confirm.
> Thank you.
> Josdeyvi
>
> [root@localhost ~]# mpls nhlfe add key 0
> [root@localhost ~]# mpls nhlfe change key 0x2 instructions
> push gen 10000 nexthop eth0 ipv4 10.0.1.2
> [root@localhost ~]# iptables -A OUTPUT -d 10.0.1.2 -j
> spec_nh --spec_nh 0x8847:0x2
>
> [root@localhost ~]# iptables -L Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> RH-Firewall-1-INPUT  all  --  anywhere             anywhere
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> RH-Firewall-1-INPUT  all  --  anywhere             anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> spec_nh    all  --  anywhere             10.0.1.2
>  set spec_nh 0x4788:0x00000002
>
>
>

_________________________________________________________________________=
_
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - =C9 gr=E1tis!
http://antipopup.uol.com.br/

>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events=
, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>

// -------------------------------------------------------------------
// Ramon Casellas - GET/ENST/INFRES/RHD/A508 - cas...@in...
// Tel: +33 (0)1 45 81 75 88                 Fax: +33 (0)1 45 81 71 58
// 37/39 rue Dareau 75014 Paris   --    http://perso.enst.fr/~casellas

[mpls-linux-general] LDP / RSVP-TE

[Bertrand L. <ble...@in...>]

HI,

I think that LDP under Linux is a little bit worse.
Can RSVP-TE replace LDP under Linux ?
If yes, does anybody know an implementation of RSVP-TE under linux ?


Thanks

Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [mpls-linux-general] Possible Iptables --spec_nh bug

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

On Mon, 2 May 2005, jrussi wrote:

> Leu,
>
> You see the output from iptables -L below? Shouldn't it be
> "set spec_nh 0x8847" instead of "set spec_nh 0x4788"?

possibly there is a missing htons in the iptables patch. I'll sync the
source code tomorrow

Regards,
R.


>
> Please confirm.
> Thank you.
> Josdeyvi
>
> [root@localhost ~]# mpls nhlfe add key 0
> [root@localhost ~]# mpls nhlfe change key 0x2 instructions
> push gen 10000 nexthop eth0 ipv4 10.0.1.2
> [root@localhost ~]# iptables -A OUTPUT -d 10.0.1.2 -j
> spec_nh --spec_nh 0x8847:0x2
>
> [root@localhost ~]# iptables -L Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> RH-Firewall-1-INPUT  all  --  anywhere             anywhere
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> RH-Firewall-1-INPUT  all  --  anywhere             anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> spec_nh    all  --  anywhere             10.0.1.2
>  set spec_nh 0x4788:0x00000002
>
>
>

__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - =C9 gr=E1tis!
http://antipopup.uol.com.br/

>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, =
4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>

// -------------------------------------------------------------------
// Ramon Casellas - GET/ENST/INFRES/RHD/A508 - cas...@in...
// Tel: +33 (0)1 45 81 75 88                 Fax: +33 (0)1 45 81 71 58
// 37/39 rue Dareau 75014 Paris   --    http://perso.enst.fr/~casellas

[mpls-linux-general] Tunnel MPLS, crash mtu

[<jul...@aq...>]

Hello,


We create an interface mpls1 to stack 2 labels.

the ping is ok.

but when the size if the ping is near 1469, the computer crash.

We think that it try to send something bigger than the MTU of eth0.

We try to change the mtu of mpls1 but it don't work.


Is it possible to change the mtu of mpls1 ?


the consequence if that is that an transfert (iperf or ssh ) crash.

thank for your help.


-- 
Julien CAYSSOL
INSA de LYON                  -=-      Département Telecom Services et Usages
http://www.aqwz.com/                                    Tèl : +33 664 973 067

[mpls-linux-general] Possible Iptables --spec_nh bug

[jrussi <jr...@uo...>]

Leu,

You see the output from iptables -L below? Shouldn't it be
"set spec_nh 0x8847" instead of "set spec_nh 0x4788"?

Please confirm. 
Thank you.
Josdeyvi

[root@localhost ~]# mpls nhlfe add key 0
[root@localhost ~]# mpls nhlfe change key 0x2 instructions
push gen 10000 nexthop eth0 ipv4 10.0.1.2
[root@localhost ~]# iptables -A OUTPUT -d 10.0.1.2 -j
spec_nh --spec_nh 0x8847:0x2

[root@localhost ~]# iptables -L Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
spec_nh    all  --  anywhere             10.0.1.2          
 set spec_nh 0x4788:0x00000002


=0A =0A__________________________________________________________________=
________=0AAcabe com aquelas janelinhas que pulam na sua tela.=0AAntiPop-=
up UOL - =C9 gr=E1tis!=0Ahttp://antipopup.uol.com.br/=0A

Re: [mpls-linux-general] mpls configuration with specific portnumber

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

On Mon, 2 May 2005, Claus Holst wrote:

>
> We are missing some detailed examples that explains how to make a
> configuration that allocates a certain amount of bandwidth for one type
> of data (data on a given port number). Any suggestions where to find
> such examples or how it is done?

Hi all,

This could be done either statically or dynamically, and it combines MPLS
forwarding + traffic conditioning and schedulling. I 've just played a bit
with 1 hop paths, considering the LSP as a virtual interface (e.g mpls0)
and then playing with tc to do the bandwidth management. For multihop
paths, I'm still unsure about how to do it properly.

Imho, the right way to do that is to dynamically stablish the LSP with
resource reservation and then map tht traffic to that LSP.
Resource reservation is still tricksy. It is something that we've had in
mind for a while, but it takes a bit of work. On one hand, a working
signalling protocol, like RSVP in atlantis. We did a few tests for 2.4
kernels (iirc rsvp uses the old userspace-kernelspace interface) and then
a mechanism to actually perform the bandwidth management as requested with
the resource reservation using some kind of schedulling like CBQ. I think
that the first step would be to work on the RSVP daemon, clean it up a bit
and use the new interface. Nevertheless the big question is how to
automate the bandwidth management, how to set up the cbq classes and how
to map labelled traffic to the classes. It's been a while since I've been
working on this, maybe someone more knowledgeable can give you more
concrete indications.

Best regards,
Ramon


>
> Regards
> Claus and Jesper
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>

// -------------------------------------------------------------------
// Ramon Casellas - GET/ENST/INFRES/RHD/A508 - cas...@in...
// Tel: +33 (0)1 45 81 75 88                 Fax: +33 (0)1 45 81 71 58
// 37/39 rue Dareau 75014 Paris   --    http://perso.enst.fr/~casellas

[mpls-linux-general] mpls configuration with specific portnumber

[Claus H. <200...@ei...>]

Hello,

We have executed the following commands on two computers. One acting as 
a server and one as a client.
The purpose of the configuration is to make sure that only UDP traffic 
from port 80 will be labeled.
This is not happening though. Instead all traffic on all ports are 
labeled, when transfering a file from the server to the client.
The server computer does a lot of harddrive processing/accessing during 
the transfer and the client computer "hangs" (like it's using all the 
ressources for the transfer)

Server computer (130.225.185.241):
    mpls nhlfe add key 0
    mpls nhlfe change key 0x2 instructions push gen 10000 nexthop eth0 
ipv4 130.225.185.243
    # iptables -A OUTPUT -d 130.225.185.243 -p udp --sport 80 -j spec_nh 
--spec_nh 0x8847:0x2

Client computer (130.225.185.243):
    mpls labelspace add dev eth1 labelspace 0
    mpls ilm add label gen 10000 labelspace 0

We are missing some detailed examples that explains how to make a 
configuration that allocates a certain amount of bandwidth for one type 
of data (data on a given port number). Any suggestions where to find 
such examples or how it is done?

Regards
Claus and Jesper

Re: [mpls-linux-general] Mapping traffic to a LSP using iptables

[Claus H. <200...@ei...>]

After installing the kernel RPM from FC2 the problem is gone. It seems 
as if my own patching and compilation of the kernel wasn't correct.

Thank you for the fast responses!

/ Claus

Claus Holst wrote:

>The RPM lists the /lib/iptables/libipt_spec_nh.so file. I have always
>executed the commands when logged in as root.
>
>On Tue, Apr 26, 2005 at 06:09:58PM +0200, Claus Holst wrote:
>  
>
>>I cannot get to the machines at the moment, but what should I be looking 
>>for in the output?
>>    
>>
>
>In particular you are looking to make sure the RPM lists the file:
>
>    /lib/iptables/libipt_spec_nh.so
>
>and that the file exists on the system.  If is does then is must be
>something about how it's being called (not being run as root etc) and
>we will have to do some tracing to see what is happening.
>
>In the future please use 'wide' reply (ie reply to the list and to me).
>Thanks
>
>  
>
>>James R. Leu wrote:
>>
>>    
>>
>>>Do a 'rpm -ql iptables' and send the output to the list.
>>>
>>>On Tue, Apr 26, 2005 at 05:44:32PM +0200, Claus Holst wrote:
>>>
>>>
>>>      
>>>
>>>>I downloaded the RPM from 
>>>>http://prdownloads.sourceforge.net/mpls-linux/iptables-1.2.11-3.1.FC3mpls1_946.i386.rpm?download
>>>>
>>>>/Claus
>>>>
>>>>James R. Leu wrote:
>>>>
>>>>  
>>>>
>>>>        
>>>>
>>>>>Did you download the iptables RPM from http://mpls-linux.sf.net/
>>>>>or patch/compile iptables by hand?
>>>>>
>>>>>On Tue, Apr 26, 2005 at 02:41:18PM +0200, Claus Holst wrote:
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>After executing the following commands:
>>>>>>
>>>>>>mpls nhlfe add key 0
>>>>>>mpls nhlfe change key 0x2 instructions push gen 10000 nexthop eth0 ipv4 
>>>>>>130.225.185.243
>>>>>>iptables -A OUTPUT -d 130.225.185.241 -j spec_nh --spec_nh 0x8847:0x2
>>>>>>
>>>>>>I get the following error:
>>>>>>
>>>>>>iptables: No chain/target/match by that name
>>>>>>
>>>>>>I guess it is the target that is wrong?
>>>>>>
>>>>>>Regards,
>>>>>>Claus
>>>>>>
>>>>>>
>>>>>>
>>>>>>-------------------------------------------------------
>>>>>>SF email is sponsored by - The IT Product Guide
>>>>>>Read honest & candid reviews on hundreds of IT Products from real users.
>>>>>>Discover which products truly live up to the hype. Start reading now.
>>>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>>>_______________________________________________
>>>>>>mpls-linux-general mailing list
>>>>>>mpl...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>>>>>>
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>          
>>>>>
>>>>-- 
>>>>No virus found in this outgoing message.
>>>>Checked by AVG Anti-Virus.
>>>>Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2005
>>>>  
>>>>
>>>>        
>>>>
>>-- 
>>No virus found in this outgoing message.
>>Checked by AVG Anti-Virus.
>>Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2005
>>    
>>
>
>  
>

[mpls-linux-general] Unable to find protocol driver for 'AF_INET' segfault

[rameshv <ram...@wi...>]

Hi,

i got segmentation fault while using mpls tool.
i added labelspace as follows

mpls labelspace add dev eth0 labelspace 0

mpls labelspace show 

shows the labelspaces. after that the following ilm command gives segfault.

mpls ilm add label gen 1000 labelspace 0

dmesg says 


MPLS DEBUG net/mpls/mpls_ilm.c:146:mpls_ilm_dst_alloc: *Unable to find 
protocol driver for 'AF_INET'*
MPLS DEBUG net/mpls/mpls_ilm.c:157:mpls_ilm_dst_alloc: exit
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c0322e34
*pde = 00000000
Oops: 0000 [#1]
..............
..................

now what is the problem, how to rectify that error *Unable to find 
protocol driver for 'AF_INET'


*regards
Ramesh.s*
*

Re: [mpls-linux-general] LDP :(

[Bertrand L. <ble...@in...>]

Hi,

After some searchs, it apperas to be a bugg in glibc :
http://lists.debian.org/debian-glibc/2004/08/msg00102.html

i'm trying to resolve it !


Selon "James R. Leu" <jl...@mi...>:

> If you want to debug further, I would add a fprintf to the functions in
> impl_mm.c.  It will make ldpd very chatty, but it will help debug a
> "double free" which is kind of what it is looking like.
>
> On Thu, Apr 28, 2005 at 04:03:33PM +0200, Bertrand Lemaitre wrote:
> > I have the following :
> >
> > (gdb) where
> > #0  0xb7eae03e in malloc_consolidate (av=0xb7f5e480) at malloc.c:4391
> > #1  0xb7eaf02d in _int_malloc (av=0xb7f5e480, bytes=24) at malloc.c:3849
> > #2  0xb7eb05a1 in *__GI___libc_malloc (bytes=4096) at malloc.c:3308
> > #3  0xb7fce60b in zmalloc (type=115, size=4096) at memory.c:56
> > #4  0x0804a915 in mpls_malloc (size=4096) at impl_mm.c:12
> > #5  0x080525c1 in ldp_buf_create (size=4096) at ldp_buf.c:31
> > #6  0x0805c99c in ldp_if_create (g=0x809a050) at ldp_if.c:60
> > #7  0x08054cde in ldp_cfg_if_set (handle=0x809a050, i=0x80987c8, flag=3)
> >     at ldp_cfg.c:860
> > #8  0x0804c77a in ldp_interface_create (li=0x8098738) at ldp_interface.c:51
> > #9  0x0804c412 in ldp_new () at ldp.c:116
> > #10 0x0804c962 in mpls_ldp (self=0x80819e0, vty=0x8099818, argc=0,
> >     argv=0xbffff868) at ldp_vty.c:50
> > #11 0xb7fd3ae4 in cmd_execute_command_real (vline=0x8099fe0, vty=0x8099818,
> >     cmd=0x0) at command.c:2053
> > #12 0xb7fd3bd0 in cmd_execute_command (vline=0x8099fe0, vty=0x8099818,
> cmd=0x0)
> >     at command.c:2087
> > #13 0xb7fd59e8 in vty_command (vty=0x8099818, buf=0x80998f8 "mpls ldp ")
> >     at vty.c:357
> > #14 0xb7fd7247 in vty_read (thread=0x18) at vty.c:1209
> > #15 0xb7fd0b8b in thread_call (thread=0xbffffc4c) at thread.c:877
> > #16 0x0804c0e6 in main (argc=7, argv=0xbffffd54) at ldp_main.c:236
> >
> >
> > I'm searching too...
> >
> >
> >
> > Selon "James R. Leu" <jl...@mi...>:
> >
> > > You could try running ldpd in gdb to figure out where it is dieing.
> > >
> > > gdb /usr/sbin/ldpd
> > > run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
> > > <use telnet to issue ldpd commands>
> > > <after ldpd dies>
> > > where
> > >
> > > Send the output to the list and we can start debugging it.
> > >
> > > On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> > > > Hi everybody,
> > > >
> > > > First of all, I can tell you that mpls between Quagga / Cisco is good.
> > > > But, Cisco -> Quagga takes more problems.
> > > >
> > > > I think it's linked to LDP.
> > > >
> > > > So, when I try to type 'mpls ldp' in the ldpd administration console
> (via
> > > > telnet), my console is over and I must kill the process ldpd to go back
> > > again.
> > > >
> > > > In the log, I have the follow message :
> > > >
> > > > Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
> > > > (296)headroom=12 tailroom=28
> > > >
> > > >
> > > > Any idea ?
> > > >
> > > > With TcpDump, I don't see any ldp packets...
> > > >
> > > > Thanks for your help
> > > >
> > > > Bertrand Lemaitre
> > > >
> > > > ----------------------------------------------------------------
> > > > This message was sent using IMP, the Internet Messaging Program.
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by: Tell us your software development plans!
> > > > Take this survey and enter to win a one-year sub to SourceForge.net
> > > > Plus IDC's 2005 look-ahead and a copy of this survey
> > > > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> > > > _______________________________________________
> > > > mpls-linux-general mailing list
> > > > mpl...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > > --
> > > James R. Leu
> > > jl...@mi...
> > >
> >
> >
> > Bertrand Lemaitre
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
>
> --
> James R. Leu
> jl...@mi...
>


Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[mpls-linux-general] TC qos support for mpls in kernel 2.6.9

[<ram...@wi...>]

Hi,

I downloaded kernel-2.6.9 and mpls-linux. I patched the kernel for mpls
support and iproute2 which gives mpls and tc. Now I booted with mpls
support. I want to know whether this iproute2 supports mpls Qos.

Thanks in advance

Regards

Ramesh.s

Re: [mpls-linux-general] LDP :(

[Bertrand L. <ble...@in...>]

in fact, in searching, I think the probleme is somewhere else...

I fand this error message  :
Program received signal SIGTERM, Terminated.
malloc_consolidate (av=0xb7f5e480) at malloc.c:4400
4400    malloc.c: No such file or directory.
        in malloc.c

and, I have a malloc.c file but it is located in filesystem jff2...
and the line number told by gdb don't correspond at all... these numbers are
greater than the total lines in the file....

ideas ???

thanks


Selon "James R. Leu" <jl...@mi...>:

> If you want to debug further, I would add a fprintf to the functions in
> impl_mm.c.  It will make ldpd very chatty, but it will help debug a
> "double free" which is kind of what it is looking like.
>
> On Thu, Apr 28, 2005 at 04:03:33PM +0200, Bertrand Lemaitre wrote:
> > I have the following :
> >
> > (gdb) where
> > #0  0xb7eae03e in malloc_consolidate (av=0xb7f5e480) at malloc.c:4391
> > #1  0xb7eaf02d in _int_malloc (av=0xb7f5e480, bytes=24) at malloc.c:3849
> > #2  0xb7eb05a1 in *__GI___libc_malloc (bytes=4096) at malloc.c:3308
> > #3  0xb7fce60b in zmalloc (type=115, size=4096) at memory.c:56
> > #4  0x0804a915 in mpls_malloc (size=4096) at impl_mm.c:12
> > #5  0x080525c1 in ldp_buf_create (size=4096) at ldp_buf.c:31
> > #6  0x0805c99c in ldp_if_create (g=0x809a050) at ldp_if.c:60
> > #7  0x08054cde in ldp_cfg_if_set (handle=0x809a050, i=0x80987c8, flag=3)
> >     at ldp_cfg.c:860
> > #8  0x0804c77a in ldp_interface_create (li=0x8098738) at ldp_interface.c:51
> > #9  0x0804c412 in ldp_new () at ldp.c:116
> > #10 0x0804c962 in mpls_ldp (self=0x80819e0, vty=0x8099818, argc=0,
> >     argv=0xbffff868) at ldp_vty.c:50
> > #11 0xb7fd3ae4 in cmd_execute_command_real (vline=0x8099fe0, vty=0x8099818,
> >     cmd=0x0) at command.c:2053
> > #12 0xb7fd3bd0 in cmd_execute_command (vline=0x8099fe0, vty=0x8099818,
> cmd=0x0)
> >     at command.c:2087
> > #13 0xb7fd59e8 in vty_command (vty=0x8099818, buf=0x80998f8 "mpls ldp ")
> >     at vty.c:357
> > #14 0xb7fd7247 in vty_read (thread=0x18) at vty.c:1209
> > #15 0xb7fd0b8b in thread_call (thread=0xbffffc4c) at thread.c:877
> > #16 0x0804c0e6 in main (argc=7, argv=0xbffffd54) at ldp_main.c:236
> >
> >
> > I'm searching too...
> >
> >
> >
> > Selon "James R. Leu" <jl...@mi...>:
> >
> > > You could try running ldpd in gdb to figure out where it is dieing.
> > >
> > > gdb /usr/sbin/ldpd
> > > run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
> > > <use telnet to issue ldpd commands>
> > > <after ldpd dies>
> > > where
> > >
> > > Send the output to the list and we can start debugging it.
> > >
> > > On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> > > > Hi everybody,
> > > >
> > > > First of all, I can tell you that mpls between Quagga / Cisco is good.
> > > > But, Cisco -> Quagga takes more problems.
> > > >
> > > > I think it's linked to LDP.
> > > >
> > > > So, when I try to type 'mpls ldp' in the ldpd administration console
> (via
> > > > telnet), my console is over and I must kill the process ldpd to go back
> > > again.
> > > >
> > > > In the log, I have the follow message :
> > > >
> > > > Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
> > > > (296)headroom=12 tailroom=28
> > > >
> > > >
> > > > Any idea ?
> > > >
> > > > With TcpDump, I don't see any ldp packets...
> > > >
> > > > Thanks for your help
> > > >
> > > > Bertrand Lemaitre
> > > >
> > > > ----------------------------------------------------------------
> > > > This message was sent using IMP, the Internet Messaging Program.
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by: Tell us your software development plans!
> > > > Take this survey and enter to win a one-year sub to SourceForge.net
> > > > Plus IDC's 2005 look-ahead and a copy of this survey
> > > > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> > > > _______________________________________________
> > > > mpls-linux-general mailing list
> > > > mpl...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > > --
> > > James R. Leu
> > > jl...@mi...
> > >
> >
> >
> > Bertrand Lemaitre
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
>
> --
> James R. Leu
> jl...@mi...
>


Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [mpls-linux-general] LDP :(

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

If you want to debug further, I would add a fprintf to the functions in
impl_mm.c.  It will make ldpd very chatty, but it will help debug a
"double free" which is kind of what it is looking like.

On Thu, Apr 28, 2005 at 04:03:33PM +0200, Bertrand Lemaitre wrote:
> I have the following :
>=20
> (gdb) where
> #0  0xb7eae03e in malloc_consolidate (av=3D0xb7f5e480) at malloc.c:4391
> #1  0xb7eaf02d in _int_malloc (av=3D0xb7f5e480, bytes=3D24) at malloc.c:3=
849
> #2  0xb7eb05a1 in *__GI___libc_malloc (bytes=3D4096) at malloc.c:3308
> #3  0xb7fce60b in zmalloc (type=3D115, size=3D4096) at memory.c:56
> #4  0x0804a915 in mpls_malloc (size=3D4096) at impl_mm.c:12
> #5  0x080525c1 in ldp_buf_create (size=3D4096) at ldp_buf.c:31
> #6  0x0805c99c in ldp_if_create (g=3D0x809a050) at ldp_if.c:60
> #7  0x08054cde in ldp_cfg_if_set (handle=3D0x809a050, i=3D0x80987c8, flag=
=3D3)
>     at ldp_cfg.c:860
> #8  0x0804c77a in ldp_interface_create (li=3D0x8098738) at ldp_interface.=
c:51
> #9  0x0804c412 in ldp_new () at ldp.c:116
> #10 0x0804c962 in mpls_ldp (self=3D0x80819e0, vty=3D0x8099818, argc=3D0,
>     argv=3D0xbffff868) at ldp_vty.c:50
> #11 0xb7fd3ae4 in cmd_execute_command_real (vline=3D0x8099fe0, vty=3D0x80=
99818,
>     cmd=3D0x0) at command.c:2053
> #12 0xb7fd3bd0 in cmd_execute_command (vline=3D0x8099fe0, vty=3D0x8099818=
, cmd=3D0x0)
>     at command.c:2087
> #13 0xb7fd59e8 in vty_command (vty=3D0x8099818, buf=3D0x80998f8 "mpls ldp=
 ")
>     at vty.c:357
> #14 0xb7fd7247 in vty_read (thread=3D0x18) at vty.c:1209
> #15 0xb7fd0b8b in thread_call (thread=3D0xbffffc4c) at thread.c:877
> #16 0x0804c0e6 in main (argc=3D7, argv=3D0xbffffd54) at ldp_main.c:236
>=20
>=20
> I'm searching too...
>=20
>=20
>=20
> Selon "James R. Leu" <jl...@mi...>:
>=20
> > You could try running ldpd in gdb to figure out where it is dieing.
> >
> > gdb /usr/sbin/ldpd
> > run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
> > <use telnet to issue ldpd commands>
> > <after ldpd dies>
> > where
> >
> > Send the output to the list and we can start debugging it.
> >
> > On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> > > Hi everybody,
> > >
> > > First of all, I can tell you that mpls between Quagga / Cisco is good.
> > > But, Cisco -> Quagga takes more problems.
> > >
> > > I think it's linked to LDP.
> > >
> > > So, when I try to type 'mpls ldp' in the ldpd administration console =
(via
> > > telnet), my console is over and I must kill the process ldpd to go ba=
ck
> > again.
> > >
> > > In the log, I have the follow message :
> > >
> > > Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len =
88
> > > (296)headroom=3D12 tailroom=3D28
> > >
> > >
> > > Any idea ?
> > >
> > > With TcpDump, I don't see any ldp packets...
> > >
> > > Thanks for your help
> > >
> > > Bertrand Lemaitre
> > >
> > > ----------------------------------------------------------------
> > > This message was sent using IMP, the Internet Messaging Program.
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by: Tell us your software development plans!
> > > Take this survey and enter to win a one-year sub to SourceForge.net
> > > Plus IDC's 2005 look-ahead and a copy of this survey
> > > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=3D105h=
ix
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
>=20
>=20
> Bertrand Lemaitre
>=20
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.

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

Re: [mpls-linux-general] LDP :(

[Bertrand L. <ble...@in...>]

I have the following :

(gdb) where
#0  0xb7eae03e in malloc_consolidate (av=0xb7f5e480) at malloc.c:4391
#1  0xb7eaf02d in _int_malloc (av=0xb7f5e480, bytes=24) at malloc.c:3849
#2  0xb7eb05a1 in *__GI___libc_malloc (bytes=4096) at malloc.c:3308
#3  0xb7fce60b in zmalloc (type=115, size=4096) at memory.c:56
#4  0x0804a915 in mpls_malloc (size=4096) at impl_mm.c:12
#5  0x080525c1 in ldp_buf_create (size=4096) at ldp_buf.c:31
#6  0x0805c99c in ldp_if_create (g=0x809a050) at ldp_if.c:60
#7  0x08054cde in ldp_cfg_if_set (handle=0x809a050, i=0x80987c8, flag=3)
    at ldp_cfg.c:860
#8  0x0804c77a in ldp_interface_create (li=0x8098738) at ldp_interface.c:51
#9  0x0804c412 in ldp_new () at ldp.c:116
#10 0x0804c962 in mpls_ldp (self=0x80819e0, vty=0x8099818, argc=0,
    argv=0xbffff868) at ldp_vty.c:50
#11 0xb7fd3ae4 in cmd_execute_command_real (vline=0x8099fe0, vty=0x8099818,
    cmd=0x0) at command.c:2053
#12 0xb7fd3bd0 in cmd_execute_command (vline=0x8099fe0, vty=0x8099818, cmd=0x0)
    at command.c:2087
#13 0xb7fd59e8 in vty_command (vty=0x8099818, buf=0x80998f8 "mpls ldp ")
    at vty.c:357
#14 0xb7fd7247 in vty_read (thread=0x18) at vty.c:1209
#15 0xb7fd0b8b in thread_call (thread=0xbffffc4c) at thread.c:877
#16 0x0804c0e6 in main (argc=7, argv=0xbffffd54) at ldp_main.c:236


I'm searching too...



Selon "James R. Leu" <jl...@mi...>:

> You could try running ldpd in gdb to figure out where it is dieing.
>
> gdb /usr/sbin/ldpd
> run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
> <use telnet to issue ldpd commands>
> <after ldpd dies>
> where
>
> Send the output to the list and we can start debugging it.
>
> On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> > Hi everybody,
> >
> > First of all, I can tell you that mpls between Quagga / Cisco is good.
> > But, Cisco -> Quagga takes more problems.
> >
> > I think it's linked to LDP.
> >
> > So, when I try to type 'mpls ldp' in the ldpd administration console (via
> > telnet), my console is over and I must kill the process ldpd to go back
> again.
> >
> > In the log, I have the follow message :
> >
> > Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
> > (296)headroom=12 tailroom=28
> >
> >
> > Any idea ?
> >
> > With TcpDump, I don't see any ldp packets...
> >
> > Thanks for your help
> >
> > Bertrand Lemaitre
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Tell us your software development plans!
> > Take this survey and enter to win a one-year sub to SourceForge.net
> > Plus IDC's 2005 look-ahead and a copy of this survey
> > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
> jl...@mi...
>


Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [mpls-linux-general] LDP :(

[Bertrand L. <ble...@in...>]

I have to install gdb and I came back

thanks a lot

Selon "James R. Leu" <jl...@mi...>:

> You could try running ldpd in gdb to figure out where it is dieing.
>
> gdb /usr/sbin/ldpd
> run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
> <use telnet to issue ldpd commands>
> <after ldpd dies>
> where
>
> Send the output to the list and we can start debugging it.
>
> On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> > Hi everybody,
> >
> > First of all, I can tell you that mpls between Quagga / Cisco is good.
> > But, Cisco -> Quagga takes more problems.
> >
> > I think it's linked to LDP.
> >
> > So, when I try to type 'mpls ldp' in the ldpd administration console (via
> > telnet), my console is over and I must kill the process ldpd to go back
> again.
> >
> > In the log, I have the follow message :
> >
> > Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
> > (296)headroom=12 tailroom=28
> >
> >
> > Any idea ?
> >
> > With TcpDump, I don't see any ldp packets...
> >
> > Thanks for your help
> >
> > Bertrand Lemaitre
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Tell us your software development plans!
> > Take this survey and enter to win a one-year sub to SourceForge.net
> > Plus IDC's 2005 look-ahead and a copy of this survey
> > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
> jl...@mi...
>


Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [mpls-linux-general] LDP :(

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

You could try running ldpd in gdb to figure out where it is dieing.

gdb /usr/sbin/ldpd
run -A 127.0.0.1 -f /etc/quagga/ldpd.conf
<use telnet to issue ldpd commands>
<after ldpd dies>
where

Send the output to the list and we can start debugging it.

On Thu, Apr 28, 2005 at 03:18:25PM +0200, Bertrand Lemaitre wrote:
> Hi everybody,
>=20
> First of all, I can tell you that mpls between Quagga / Cisco is good.
> But, Cisco -> Quagga takes more problems.
>=20
> I think it's linked to LDP.
>=20
> So, when I try to type 'mpls ldp' in the ldpd administration console (via
> telnet), my console is over and I must kill the process ldpd to go back a=
gain.
>=20
> In the log, I have the follow message :
>=20
> Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
> (296)headroom=3D12 tailroom=3D28
>=20
>=20
> Any idea ?
>=20
> With TcpDump, I don't see any ldp packets...
>=20
> Thanks for your help
>=20
> Bertrand Lemaitre
>=20
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=3D105hix
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

[mpls-linux-general] LDP :(

[Bertrand L. <ble...@in...>]

Hi everybody,

First of all, I can tell you that mpls between Quagga / Cisco is good.
But, Cisco -> Quagga takes more problems.

I think it's linked to LDP.

So, when I try to type 'mpls ldp' in the ldpd administration console (via
telnet), my console is over and I must kill the process ldpd to go back again.

In the log, I have the follow message :

Apr 28 14:53:45 NX7H7 kernel: MPLS mpls_skb_dump: from eth1 with len 88
(296)headroom=12 tailroom=28


Any idea ?

With TcpDump, I don't see any ldp packets...

Thanks for your help

Bertrand Lemaitre

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [mpls-linux-general] Mapping traffic to a LSP using iptables

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

Just for sanity sake do a 'which iptables' to make sure your
running the binary from the RPM.  If that checks out then do a

    strace -f iptables <your parameters from before>

You'll probably want to redirect the output to a file.  Look through that
output for where it tries to load libipt_spec_nh.so, check to see what
error number is being returned.  Send that portion of the output to
the list.

On Thu, Apr 28, 2005 at 09:21:32AM +0200, Claus Holst wrote:
> The RPM lists the /lib/iptables/libipt_spec_nh.so file. I have always
> executed the commands when logged in as root.
>=20
> On Tue, Apr 26, 2005 at 06:09:58PM +0200, Claus Holst wrote:
> > I cannot get to the machines at the moment, but what should I be lookin=
g=20
> > for in the output?
>=20
> In particular you are looking to make sure the RPM lists the file:
>=20
>     /lib/iptables/libipt_spec_nh.so
>=20
> and that the file exists on the system.  If is does then is must be
> something about how it's being called (not being run as root etc) and
> we will have to do some tracing to see what is happening.
>=20
> In the future please use 'wide' reply (ie reply to the list and to me).
> Thanks
>=20
> > James R. Leu wrote:
> >=20
> > > Do a 'rpm -ql iptables' and send the output to the list.
> > >=20
> > > On Tue, Apr 26, 2005 at 05:44:32PM +0200, Claus Holst wrote:
> > >=20
> > >=20
> > > > I downloaded the RPM from=20
> > > > http://prdownloads.sourceforge.net/mpls-linux/iptables-1.2.11-3.1.F=
C3mpls1_946.i386.rpm?download
> > > >=20
> > > > /Claus
> > > >=20
> > > > James R. Leu wrote:
> > > >=20
> > > >  =20
> > > >=20
> > > > > Did you download the iptables RPM from http://mpls-linux.sf.net/
> > > > > or patch/compile iptables by hand?
> > > > >=20
> > > > > On Tue, Apr 26, 2005 at 02:41:18PM +0200, Claus Holst wrote:
> > > > >=20
> > > > >=20
> > > > >    =20
> > > > >=20
> > > > > > After executing the following commands:
> > > > > >=20
> > > > > > mpls nhlfe add key 0
> > > > > > mpls nhlfe change key 0x2 instructions push gen 10000 nexthop e=
th0 ipv4=20
> > > > > > 130.225.185.243
> > > > > > iptables -A OUTPUT -d 130.225.185.241 -j spec_nh --spec_nh 0x88=
47:0x2
> > > > > >=20
> > > > > > I get the following error:
> > > > > >=20
> > > > > > iptables: No chain/target/match by that name
> > > > > >=20
> > > > > > I guess it is the target that is wrong?
> > > > > >=20
> > > > > > Regards,
> > > > > > Claus
> > > > > >=20
> > > > > >=20
> > > > > >=20
> > > > > > -------------------------------------------------------
> > > > > > SF email is sponsored by - The IT Product Guide
> > > > > > Read honest & candid reviews on hundreds of IT Products from re=
al users.
> > > > > > Discover which products truly live up to the hype. Start readin=
g now.
> > > > > > http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> > > > > > _______________________________________________
> > > > > > mpls-linux-general mailing list
> > > > > > mpl...@li...
> > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > > >=20
> > > > > >=20
> > > > > >      =20
> > > > > >=20
> > > > >    =20
> > > > --=20
> > > > No virus found in this outgoing message.
> > > > Checked by AVG Anti-Virus.
> > > > Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2=
005
> > > >  =20
> > > >=20
> > >=20
> >=20
> > --=20
> > No virus found in this outgoing message.
> > Checked by AVG Anti-Virus.
> > Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2005
>=20
> --=20
> James R. Leu
> jl...@mi...
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=3D105hix
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Re: [mpls-linux-general] Mapping traffic to a LSP using iptables

[Claus H. <200...@ei...>]

The RPM lists the /lib/iptables/libipt_spec_nh.so file. I have always
executed the commands when logged in as root.

On Tue, Apr 26, 2005 at 06:09:58PM +0200, Claus Holst wrote:
> I cannot get to the machines at the moment, but what should I be looking 
> for in the output?

In particular you are looking to make sure the RPM lists the file:

    /lib/iptables/libipt_spec_nh.so

and that the file exists on the system.  If is does then is must be
something about how it's being called (not being run as root etc) and
we will have to do some tracing to see what is happening.

In the future please use 'wide' reply (ie reply to the list and to me).
Thanks

> James R. Leu wrote:
> 
> > Do a 'rpm -ql iptables' and send the output to the list.
> > 
> > On Tue, Apr 26, 2005 at 05:44:32PM +0200, Claus Holst wrote:
> > 
> > 
> > > I downloaded the RPM from 
> > > http://prdownloads.sourceforge.net/mpls-linux/iptables-1.2.11-3.1.FC3mpls1_946.i386.rpm?download
> > > 
> > > /Claus
> > > 
> > > James R. Leu wrote:
> > > 
> > >   
> > > 
> > > > Did you download the iptables RPM from http://mpls-linux.sf.net/
> > > > or patch/compile iptables by hand?
> > > > 
> > > > On Tue, Apr 26, 2005 at 02:41:18PM +0200, Claus Holst wrote:
> > > > 
> > > > 
> > > >     
> > > > 
> > > > > After executing the following commands:
> > > > > 
> > > > > mpls nhlfe add key 0
> > > > > mpls nhlfe change key 0x2 instructions push gen 10000 nexthop eth0 ipv4 
> > > > > 130.225.185.243
> > > > > iptables -A OUTPUT -d 130.225.185.241 -j spec_nh --spec_nh 0x8847:0x2
> > > > > 
> > > > > I get the following error:
> > > > > 
> > > > > iptables: No chain/target/match by that name
> > > > > 
> > > > > I guess it is the target that is wrong?
> > > > > 
> > > > > Regards,
> > > > > Claus
> > > > > 
> > > > > 
> > > > > 
> > > > > -------------------------------------------------------
> > > > > SF email is sponsored by - The IT Product Guide
> > > > > Read honest & candid reviews on hundreds of IT Products from real users.
> > > > > Discover which products truly live up to the hype. Start reading now.
> > > > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > > 
> > > > > 
> > > > >       
> > > > > 
> > > >     
> > > -- 
> > > No virus found in this outgoing message.
> > > Checked by AVG Anti-Virus.
> > > Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2005
> > >   
> > > 
> > 
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25-04-2005

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