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

Re: [mpls-linux-general] Help

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

If your using the latest from CVS look in linux-port/ldp_netlink.c
The fine folks from MindTree contributed that code.

Jim

On Thu, Sep 13, 2001 at 01:40:17PM +0530, Pradeep wrote:
> Hi All
>         How should I extract routing table information from kernel
> through the net link socket.
> Please help me in this.
> 
> Thanks in advance.
> With regards.
> 
> pradeep.
> 
> 
> --
> Pradeep C Pangi,
> Software Engineer,
> Sasken Communication Technologies,
> Domlur, Bangalore 560 071.
> Ph : 5355501/3 - Ext 8253
> Fax: 5351133
> 
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] generation of the label release message

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

On Wed, Sep 19, 2001 at 12:19:59PM +0530, Abhijit Gadgil wrote:
> amit goyal wrote :
> 
> >I have a doubt regarding generation of Label release
> >message in response of withdraw message ,
> >Its like this:
> >If upstream receives wildcard FEC in the withdraw
> >message then will it send individual release message
> >for each of the FEC's for which it has received labels
> >from the down stream LSR or it will send a single
> >release message with the same FEC and label TLV
> >combination as of the withdraw message.
> 
> Here sending a release message with wild card FEC may be a bit problematic
> for the end which sent the withdraw message. (Note that this is not
> incorrect if one looks at the specifications. But it won't be guaranteed
> that this is interoperable.) The better idea would be to send FEC vector
> corrosponding to the released FECs.

First, if the downstream sent a wild card FEC in the withdraw it most
likely will support a wild card FEC in the release.

Second, exploding a single withdraw into possibly thousands of releases is
not practical.  The reason the wild card FEC was created was to keep
traffic being generated at session tear down time to a minimum.

Jim

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

-- 
James R. Leu

Re: [mpls-linux-general] RSVP-TE extension on kom RSVP engne

[<pim...@in...>]

"James R. Leu" wrote:

> NIST added TE support to the ISI RSVP implementation.
> (http://snad.ncsl.nist.gov/itg/nistswitch/) Some guys
> from IBCN (http://ds_mpls.atlantis.rug.ac.be/) adapted
> that implementation to work on MPLS for Linux.

Yep we did that, we also added DiffServ support to MPLS for Linux.

> As you know the ISI RSVP implementation is NOT GPL.

The ISI RSVP implementaion has a BSD license. Parts that were added by
Alexey and us are GPL. If you can live with that ... we sure could use an
extra hand.

Cheers,
"One of the guys from IBCN"
Pim

> The goal
> of the MPLS for LInux project is to make a MPLS forwarding and signalling
> plan eavailble under the GPL (or LGPL).  With this in mind I would really
> like someone to modify the KOM implmenetaion (which I believe is covered
> under the GPL) to support TE.
>
> Jim
>
> On Tue, Sep 18, 2001 at 12:29:31PM -0700, nitin panjwani wrote:
> > Hi,
> > I want to enhance the RSVP-TEfeatures for MPLS in the
> > KOM RSVP Engine which is available at :
> >
> > http://www.kom.e-technik.tu-darmstadt.de/rsvp/
> >
> > I want to know has anyone done similar kind of thing
> > before . If so Please mail me . I need your help for
> > the initiation of this project . As I am not very sure
> > that what are the resources required to work on such
> > kind of Project .
> >
> > Thanks in advance
> > Nitin
> >
> >
> > __________________________________________________
> > Terrorist Attacks on U.S. - How can you help?
> > Donate cash, emergency relief information
> > http://dailynews.yahoo.com/fc/US/Emergency_Information/
> >
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--
Pim Van Heuven
Ghent University - IMEC
Department of Information Technology (INTEC)
Sint-Pietersnieuwstraat, 41
B-9000, Gent, Belgium
tel.: +32-(0)9267 3592, secr.: +32-(0)9267 3570
fax : +32-(0)9267 3599
e-mail : pim...@in...
WWW :  http://www.intec.rug.ac.be

Re: [mpls-linux-general] generation of the label release message

[Abhijit G. <gab...@ee...>]

amit goyal wrote :

>I have a doubt regarding generation of Label release
>message in response of withdraw message ,
>Its like this:
>If upstream receives wildcard FEC in the withdraw
>message then will it send individual release message
>for each of the FEC's for which it has received labels
>from the down stream LSR or it will send a single
>release message with the same FEC and label TLV
>combination as of the withdraw message.

Here sending a release message with wild card FEC may be a bit problematic
for the end which sent the withdraw message. (Note that this is not
incorrect if one looks at the specifications. But it won't be guaranteed
that this is interoperable.) The better idea would be to send FEC vector
corrosponding to the released FECs.

--a

RE: [mpls-linux-general] LDP labels

[Abhijit G. <gab...@ee...>]

Look for iproute2 sources.. Excellent stuff.. I guess the sourceforge-ldp
is also doing that.

I will explain the basic idea.
create a netlink socket, bind it to a multicast group of all netlink
messages. (Binding it to routing message group is also suffice.)

Listen on this netlink socket for any messages delievered by
kernel.

Decode and use the info. Look at the sources above would help u in using
them

--a

nomit kalidhar wrote :

>Hi
>In my local LDP implementation i was not able to get a change in routing
>table notification
>but i am able to get the entire routing table so i am comparing that
>with the previous list of routing entries i have then seeing the next
>hop doing the appropiate action ( new FEC etc..).
>This i am running as a background process. Should this helpfull. :-)
>but a better approach would be to catch the routing table change from
>rtnetlink sockets any pointers how to do this i have not been able to do
>so far :-(.
>
>
>Nomit

RE: [mpls-linux-general] LDP labels

[nomit k. <nom...@in...>]

Hi
In my local LDP implementation i was not able to get a change in routing
table notification
but i am able to get the entire routing table so i am comparing that
with the previous list of routing entries i have then seeing the next
hop doing the appropiate action ( new FEC etc..).
This i am running as a background process. Should this helpfull. :-)
but a better approach would be to catch the routing table change from
rtnetlink sockets any pointers how to do this i have not been able to do
so far :-(.


Nomit

-----Original Message-----
From: James R. Leu [mailto:jl...@mi...]
Sent: Wednesday, September 19, 2001 12:53 AM
To: ric...@ya...
Cc: mpls
Subject: Re: [mpls-linux-general] LDP labels


ldp_linux will operate on exiting route entries.  So gated must populate
the tabel BEFORE firing up ldp_linux.

This could be changed by someone finishing the netlink route listener
support ...

On Tue, Sep 11, 2001 at 03:17:02PM -0700, ric...@ya... wrote:
> Hi:
>=20
>        I recently upgraded my Linux kernel with mpls
>  patch ver 0.993. I also downloaded portable LDP
>  version 0.060. I have Gated running on linux machine.
>  Just wondering how can i populate labels so that MPLS
>  forwarding plane can start forwarding my IP traffic
>  using those labels. In nutshell i want to know how
>  this LDP version will interact with kernel routing
>  table to create LSP(s) and is there any command  =20
>  available which can display labels populated through=20
>=20
>  LDP.
>=20
> Thanks,
> Rich
>=20
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo!
Messenger
> http://im.yahoo.com
>=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

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

Re: [mpls-linux-general] back trace of core

[Abhijit G. <gab...@ee...>]

>#0  0x4007524b in chunk_free (ar_ptr=0x40109d60, p=0x80758e0) at malloc.c:3121
>#1  0x40074fba in __libc_free (mem=0x80758e8) at malloc.c:3023
>#2  0x8064add in ldp_free (mem=0x80758e8) at ldp_mm_impl.c:18

This ldp_free is the culprit most likely. Look at how many bytes are
actually getting free. Are they same as malloced ones.


--a

[mpls-linux-general] back trace of core

[L S. R. <ls...@ya...>]

Dear all and james,
	finaly i got core ,please look into the core but problem is strange ;-).


[root@lsreddy ldp-portable-0.060]# gdb ldp_linux core 
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `./ldp_linux'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0  0x4007524b in chunk_free (ar_ptr=0x40109d60, p=0x80758e0) at malloc.c:3121
3121    malloc.c: No such file or directory.
(gdb) bt
#0  0x4007524b in chunk_free (ar_ptr=0x40109d60, p=0x80758e0) at malloc.c:3121
#1  0x40074fba in __libc_free (mem=0x80758e8) at malloc.c:3023
#2  0x8064add in ldp_free (mem=0x80758e8) at ldp_mm_impl.c:18
#3  0x80592c0 in Mpls_encodeLdpPDU (g=0x80736b0, lsraddr=2886730497, label_space=0, msg=0x8074870, buf=0x8075ecc "", 
    buf_size=4096) at ldp_pdu.c:134
#4  0x8050ef7 in ldp_msg_send_udp (g=0x80736b0, e=0x8076f20, msg=0x8074870) at ldp_msg.c:98
#5  0x804fde5 in ldp_hello_send (g=0x80736b0, e=0x8076f20) at ldp_hello.c:124
#6  0x804fb7b in ldp_hello_send_callback (timer=0x8076fa8, extra=0x8076f20, g=0x80736b0) at ldp_hello.c:54
#7  0x8049cc5 in main (argc=1, argv=0xbffffb24) at ldp_linux.c:606
(gdb) 

regards
lsr

Re: [mpls-linux-general] gdb out put of segmentation fault.

[Abhijit G. <gab...@ee...>]

Perhaps the problem here is some pointer which is not valid in current
context is tried to be freed. I dont know the ready made solution, but
look for a "free" statement that u think should get executed before the
malloc where the core dump is occring. Or you could be freeing more data
than malloced in previous case.

--a

L Srinivas Reddy wrote :

>GNU gdb 19991004
>Copyright 1998 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "i386-redhat-linux"...
>(gdb) r
>Starting program: /usr/home/lsreddy/mpls/ldp-portable-0.060/ldp_linux
>add global 172.16.3.1
>Adding interface eth0
>Adding interface eth1
>Adding route ac100201/32 via 3
>Adding route ac100301/32 via 3
>Adding route ac100300/24 via 3
>Adding route ac100100/24 via 2
>Adding route 7f000000/8 via 0
>Adding route 00000000/0 via 2
>Adding global object with LSRID ac100301
>prompt>add interface eth1
>Adding interface eth1
>prompt>SWITCHED TO TCP LISTEN
>SWITCHED TO TCP EVENTDATA
>PRT: ldp_state_recv_init: cannot find adj
>SWITCHED TO UDP DATA
>SWITCHED TO TCP LISTEN
>SWITCHED TO TCP EVENTDATA
>SWITCHED TO TCP EVENTDATA
>SWITCHED TO TCP EVENTDATA
>SWITCHED TO TCP EVENTDATA
>index:   1 ac100202/32 2
>SWITCHED TO UDP DATA
>SWITCHED TO UDP DATA
>SWITCHED TO UDP DATA
>SWITCHED TO TCP LISTEN

[mpls-linux-general] gdb out put of segmentation fault.

[L S. R. <ls...@ya...>]

GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) r
Starting program: /usr/home/lsreddy/mpls/ldp-portable-0.060/ldp_linux 
add global 172.16.3.1
Adding interface eth0
Adding interface eth1
Adding route ac100201/32 via 3
Adding route ac100301/32 via 3
Adding route ac100300/24 via 3
Adding route ac100100/24 via 2
Adding route 7f000000/8 via 0
Adding route 00000000/0 via 2
Adding global object with LSRID ac100301
prompt>add interface eth1
Adding interface eth1
prompt>SWITCHED TO TCP LISTEN
SWITCHED TO TCP EVENTDATA
PRT: ldp_state_recv_init: cannot find adj
SWITCHED TO UDP DATA
SWITCHED TO TCP LISTEN
SWITCHED TO TCP EVENTDATA
SWITCHED TO TCP EVENTDATA
SWITCHED TO TCP EVENTDATA
SWITCHED TO TCP EVENTDATA
index:   1 ac100202/32 2
SWITCHED TO UDP DATA
SWITCHED TO UDP DATA
SWITCHED TO UDP DATA
SWITCHED TO TCP LISTEN

Program received signal SIGSEGV, Segmentation fault.
chunk_alloc (ar_ptr=0x40109d60, nb=184) at malloc.c:2868
2868    malloc.c: No such file or directory.
(gdb) 

[mpls-linux-general] a small correction to previous mail: regarding segmentation problem

[L S. R. <ls...@ya...>]

dear all,
 this is the out put ,if u want i will enable trace to 0xfffffffff and i
will send  . one thing i want to let you know is i reduced keepalve time to 10
sec. and i am not (was not there) sending keepalive at all.
thanks for your responce,
with regards
lsr

[root@lsreddy ldp-portable-0.060]# ./ldp_linux

prompt>add global 172.16.3.1
Adding interface eth0
Adding interface eth1
Adding route ac100201/32 via 3
Adding route ac100301/32 via 3
Adding route ac100300/24 via 3
Adding route ac100100/24 via 2
Adding route 7f000000/8 via 0
Adding route 00000000/0 via 2
Adding global object with LSRID ac100301
prompt>add interface eth1
Adding interface eth1
prompt>
index:   1 ac100202/32 2
Segmentation fault
[root@lsreddy ldp-portable-0.060]# ls
CVS  Makefile  README  THANKYOU  doc  ldp_linux  ldp_linux.lsr  lib  port
[root@lsreddy ldp-portable-0.060]# 

[mpls-linux-general] regarding segmentation problem

[L S. R. <ls...@ya...>]

dear all,
	this is the out put ,if u want i will enable trace to 0xfffffffff and i
will send  . one thing i want to let you know is i reduced keepalve time to 10
sec. and i am sending keepalive at all.
thanks for your responce,
with regards
lsr

  [root@lsreddy ldp-portable-0.060]# ./ldp_linux

prompt>add global 172.16.3.1
Adding interface eth0
Adding interface eth1
Adding route ac100201/32 via 3
Adding route ac100301/32 via 3
Adding route ac100300/24 via 3
Adding route ac100100/24 via 2
Adding route 7f000000/8 via 0
Adding route 00000000/0 via 2
Adding global object with LSRID ac100301
prompt>add interface eth1
Adding interface eth1
prompt>
index:   1 ac100202/32 2
Segmentation fault
[root@lsreddy ldp-portable-0.060]# ls
CVS  Makefile  README  THANKYOU  doc  ldp_linux  ldp_linux.lsr  lib  port
[root@lsreddy ldp-portable-0.060]# 

[mpls-linux-general] Q on DoD and DU interoperation in Linux?

[HariKishan <har...@er...>]

In RFC 3036 ( LDP specification) Section 3.5.3 
states that if two LSRs, one supporting DU and
the other supporting DoD try to establish a LDP
session over a NON-ATM link, they should back off
to DU. If this is not acceptable to any of the
LSRs it should send a notification message and
should not establish the session.

Where as in Section 3.5.7.1.3 states a rule, 
which, if followed, can let the above two LSRs
interoperate with each other.

What does the Linux implementation do in such
a situation? 

Thanks,
Kishan

 

Re: [mpls-linux-general] RSVP-TE extension on kom RSVP engne

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

NIST added TE support to the ISI RSVP implementation.
(http://snad.ncsl.nist.gov/itg/nistswitch/) Some guys
from IBCN (http://ds_mpls.atlantis.rug.ac.be/) adapted
that implementation to work on MPLS for Linux.

As you know the ISI RSVP implementation is NOT GPL.  The goal
of the MPLS for LInux project is to make a MPLS forwarding and signalling
plan eavailble under the GPL (or LGPL).  With this in mind I would really
like someone to modify the KOM implmenetaion (which I believe is covered
under the GPL) to support TE.

Jim

On Tue, Sep 18, 2001 at 12:29:31PM -0700, nitin panjwani wrote:
> Hi,
> I want to enhance the RSVP-TEfeatures for MPLS in the
> KOM RSVP Engine which is available at :
> 
> http://www.kom.e-technik.tu-darmstadt.de/rsvp/
> 
> I want to know has anyone done similar kind of thing
> before . If so Please mail me . I need your help for
> the initiation of this project . As I am not very sure
> that what are the resources required to work on such
> kind of Project .
> 
> Thanks in advance
> Nitin
> 
> 
> __________________________________________________
> Terrorist Attacks on U.S. - How can you help?
> Donate cash, emergency relief information
> http://dailynews.yahoo.com/fc/US/Emergency_Information/
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] RSVP-TE extension on kom RSVP engne

[Dhiman B. <dh...@cs...>]

Have you looked at http://dsmpls.atlantis.rug.ac.be/.

-dhiman

nitin panjwani claims the following:
> Hi,
> I want to enhance the RSVP-TEfeatures for MPLS in the
> KOM RSVP Engine which is available at :
> 
> http://www.kom.e-technik.tu-darmstadt.de/rsvp/
> 
> I want to know has anyone done similar kind of thing
> before . If so Please mail me . I need your help for
> the initiation of this project . As I am not very sure
> that what are the resources required to work on such
> kind of Project .
> 
> Thanks in advance
> Nitin
> 
> 
> __________________________________________________
> Terrorist Attacks on U.S. - How can you help?
> Donate cash, emergency relief information
> http://dailynews.yahoo.com/fc/US/Emergency_Information/
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
Vote anarchist

[mpls-linux-general] RSVP-TE extension on kom RSVP engne

[nitin p. <tac...@ya...>]

Hi,
I want to enhance the RSVP-TEfeatures for MPLS in the
KOM RSVP Engine which is available at :

http://www.kom.e-technik.tu-darmstadt.de/rsvp/

I want to know has anyone done similar kind of thing
before . If so Please mail me . I need your help for
the initiation of this project . As I am not very sure
that what are the resources required to work on such
kind of Project .

Thanks in advance
Nitin


__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/

Re: [mpls-linux-general] LDP labels

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

ldp_linux will operate on exiting route entries.  So gated must populate
the tabel BEFORE firing up ldp_linux.

This could be changed by someone finishing the netlink route listener
support ...

On Tue, Sep 11, 2001 at 03:17:02PM -0700, ric...@ya... wrote:
> Hi:
> 
>        I recently upgraded my Linux kernel with mpls
>  patch ver 0.993. I also downloaded portable LDP
>  version 0.060. I have Gated running on linux machine.
>  Just wondering how can i populate labels so that MPLS
>  forwarding plane can start forwarding my IP traffic
>  using those labels. In nutshell i want to know how
>  this LDP version will interact with kernel routing
>  table to create LSP(s) and is there any command   
>  available which can display labels populated through 
> 
>  LDP.
> 
> Thanks,
> Rich
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] generation of the label release message

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

I believe it is implementation specific, but it is allowable to just return a
label release with a wild card FEC.

On Fri, Sep 14, 2001 at 04:11:37AM -0700, amit goyal wrote:
> I have a doubt regarding generation of Label release
> message in response of withdraw message ,
> Its like this:
> If upstream receives wildcard FEC in the withdraw
> message then will it send individual release message
> for each of the FEC's for which it has received labels
> from the down stream LSR or it will send a single 
> release message with the same FEC and label TLV
> combination as of the withdraw message.
> 
> Thanks in advance
> Amit Goyal
> 
> __________________________________________________
> Terrorist Attacks on U.S. - How can you help?
> Donate cash, emergency relief information
> http://dailynews.yahoo.com/fc/US/Emergency_Information/
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] getting segmentation problem in LDP-portable-066 and on

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

Can you sent me the stack trace?  If you have the core file do:

gdb ldp_linux core
bt

On Tue, Sep 18, 2001 at 05:56:47PM +0530, Lonka wrote:
> Dear all,
> 	we are facing segmentation problem in ldp_keepalive_send() , if setup
> is some thing like lsr1----------lsr2, if we stop sending keepalive from lsr2
> and after keepalive timeout in lsr1, re-establishment of session before processing 
> label map message it is getting segmentation fault.
> 
> our setup is something like this: comment the ldp_keepalive_send in lsr2
> in ldp_keepalive_send_callback function  in
> /ldp-portable-0.060/lib/ldp_keepalive.c file (line num:45).
> 
> thanks in adv. for your earliest reply,
> with regards,
> lsr
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] getting segmentation problem in LDP-portable-066 and on

[Lonka <red...@ya...>]

Dear all,
	we are facing segmentation problem in ldp_keepalive_send() , if setup
is some thing like lsr1----------lsr2, if we stop sending keepalive from lsr2
and after keepalive timeout in lsr1, re-establishment of session before processing 
label map message it is getting segmentation fault.

our setup is something like this: comment the ldp_keepalive_send in lsr2
in ldp_keepalive_send_callback function  in
/ldp-portable-0.060/lib/ldp_keepalive.c file (line num:45).

thanks in adv. for your earliest reply,
with regards,
lsr

[mpls-linux-general] generation of the label release message

[amit g. <ami...@ya...>]

I have a doubt regarding generation of Label release
message in response of withdraw message ,
Its like this:
If upstream receives wildcard FEC in the withdraw
message then will it send individual release message
for each of the FEC's for which it has received labels
from the down stream LSR or it will send a single 
release message with the same FEC and label TLV
combination as of the withdraw message.

Thanks in advance
Amit Goyal

__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/

[mpls-linux-general] Compilation error.

[<ap...@av...>]

Greetings,

     I'm getting an "ARPHRD_MPLS_TUNNER undeclared" error in mpls_tunnel.c,
during the compilation of the kernel. I'm using kernel version 2.4.9 and
MPLS patch version 0.993. Can anyone help me please?

Arménio Pinto
Portugal Telecom Inovação, SA

[mpls-linux-general] Help

[Pradeep <pra...@sa...>]

Hi All
        How should I extract routing table information from kernel
through the net link socket.
Please help me in this.

Thanks in advance.
With regards.

pradeep.


--
Pradeep C Pangi,
Software Engineer,
Sasken Communication Technologies,
Domlur, Bangalore 560 071.
Ph : 5355501/3 - Ext 8253
Fax: 5351133

[mpls-linux-general] LDP labels

[<ric...@ya...>]

Hi:

       I recently upgraded my Linux kernel with mpls
 patch ver 0.993. I also downloaded portable LDP
 version 0.060. I have Gated running on linux machine.
 Just wondering how can i populate labels so that MPLS
 forwarding plane can start forwarding my IP traffic
 using those labels. In nutshell i want to know how
 this LDP version will interact with kernel routing
 table to create LSP(s) and is there any command   
 available which can display labels populated through 

 LDP.

Thanks,
Rich

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

Re: [mpls-linux-general] tcpdump question

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

Are you connected to a switch?  That would cause this.  Can your switch
do port mirroring?  Do you have a hub?

Jim

On Fri, Aug 31, 2001 at 02:40:07PM -0700, henry mpls wrote:
> I was tring to monitor the ldp traffic on my local net
> by useing tcpdump. Problem I have is I can see all the
> broadcast traffic and unicast traffic on monitor
> station but can't see the unicast traffic between
> other stations on my local net. In other words, on
> monitor station, I can only see the traffic to monitor
> station but not other traffic between other station.
> Anyone who familiar with tcpdump please help me.
> 
> Thanks
> 
> HH
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu