mpls-linux-general Mailing List for MPLS for Linux (Page 83)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general — Mailing list for general discussion about MPLS for Linux
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(26) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(22) |
Feb
(19) |
Mar
(19) |
Apr
(45) |
May
(52) |
Jun
(101) |
Jul
(79) |
Aug
(24) |
Sep
(43) |
Oct
(54) |
Nov
(71) |
Dec
(53) |
| 2002 |
Jan
(111) |
Feb
(123) |
Mar
(67) |
Apr
(61) |
May
(75) |
Jun
(26) |
Jul
(36) |
Aug
(41) |
Sep
(79) |
Oct
(85) |
Nov
(58) |
Dec
(39) |
| 2003 |
Jan
(26) |
Feb
(61) |
Mar
(80) |
Apr
(56) |
May
(39) |
Jun
(44) |
Jul
(28) |
Aug
(25) |
Sep
(4) |
Oct
(20) |
Nov
(38) |
Dec
(9) |
| 2004 |
Jan
(14) |
Feb
(14) |
Mar
(68) |
Apr
(17) |
May
(45) |
Jun
(42) |
Jul
(41) |
Aug
(23) |
Sep
(46) |
Oct
(89) |
Nov
(55) |
Dec
(33) |
| 2005 |
Jan
(74) |
Feb
(39) |
Mar
(105) |
Apr
(96) |
May
(43) |
Jun
(48) |
Jul
(21) |
Aug
(22) |
Sep
(33) |
Oct
(28) |
Nov
(29) |
Dec
(81) |
| 2006 |
Jan
(37) |
Feb
(32) |
Mar
(147) |
Apr
(37) |
May
(33) |
Jun
(28) |
Jul
(15) |
Aug
(20) |
Sep
(15) |
Oct
(23) |
Nov
(30) |
Dec
(40) |
| 2007 |
Jan
(20) |
Feb
(24) |
Mar
(65) |
Apr
(69) |
May
(41) |
Jun
(53) |
Jul
(39) |
Aug
(76) |
Sep
(53) |
Oct
(43) |
Nov
(26) |
Dec
(24) |
| 2008 |
Jan
(19) |
Feb
(67) |
Mar
(91) |
Apr
(75) |
May
(47) |
Jun
(63) |
Jul
(68) |
Aug
(39) |
Sep
(44) |
Oct
(33) |
Nov
(62) |
Dec
(84) |
| 2009 |
Jan
(14) |
Feb
(39) |
Mar
(55) |
Apr
(63) |
May
(16) |
Jun
(9) |
Jul
(4) |
Aug
(6) |
Sep
(1) |
Oct
(2) |
Nov
(10) |
Dec
(5) |
| 2010 |
Jan
(3) |
Feb
(1) |
Mar
(5) |
Apr
(13) |
May
(4) |
Jun
(5) |
Jul
(2) |
Aug
(8) |
Sep
(6) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(21) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
|
Nov
(2) |
Dec
(6) |
| 2012 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(5) |
Aug
(3) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: James R. L. <jl...@mi...> - 2005-02-01 15:27:01
|
Why do you not listen to what I've said before? There are more significant
bugs to fix then to try and port all of the 'extra' commands to the new
porting layer. If you are determined to work on the code grab the latest
from my development tree and get the basic commands working.
On Tue, Feb 01, 2005 at 05:19:01PM +0800, ?????x wrote:
> Hi James,
>=20
> When I canceled "#if 0" of some parts of "ldp_vtysh.c", for example:=20
>=20
> DEFUN(ldp_if_remote_tcp_port,
> ldp_if_remote_tcp_port_cmd,
> "remote-tcp-port <1-65535>",
> "MPLS interface configuration\n"
> "remote LDP port\n"
> "port number\n")
> {
> struct interface *ifp =3D vty->index;
> struct ldp_interface *li =3D (struct ldp_interface*)ifp->info;
> struct ldp *ldp =3D li->ldp;
>=20
> li->entity.remote_tcp_port =3D atoi(argv[0]);
> if (!ldp) {
> li->create_on_hold =3D MPLS_BOOL_TRUE;
> return CMD_SUCCESS;
> }
>=20
> ldp_cfg_entity_set(ldp->h, &li->entity, LDP_ENTITY_CFG_REMOTE_TCP);
> return CMD_SUCCESS;
> }
>=20
> When I compile it, there was an error:
> ldp_vty.c:1555: error: structure has no member named `ldp'
>=20
> Then I went to check "ldp_interface.h", I found that there actually has n=
o this member in "struct ldp_interface".
>=20
> Thanks.
>=20
> Timothy
> 2005.02.01
--=20
James R. Leu
jl...@mi...
|
|
From: <m9...@cn...> - 2005-02-01 09:13:24
|
Hi James,
When I canceled "#if 0" of some parts of "ldp_vtysh.c", for example:=20
DEFUN(ldp_if_remote_tcp_port,
ldp_if_remote_tcp_port_cmd,
"remote-tcp-port <1-65535>",
"MPLS interface configuration\n"
"remote LDP port\n"
"port number\n")
{
struct interface *ifp =3D vty->index;
struct ldp_interface *li =3D (struct ldp_interface*)ifp->info;
struct ldp *ldp =3D li->ldp;
li->entity.remote_tcp_port =3D atoi(argv[0]);
if (!ldp) {
li->create_on_hold =3D MPLS_BOOL_TRUE;
return CMD_SUCCESS;
}
ldp_cfg_entity_set(ldp->h, &li->entity, LDP_ENTITY_CFG_REMOTE_TCP);
return CMD_SUCCESS;
}
When I compile it, there was an error:
ldp_vty.c:1555: error: structure has no member named `ldp'
Then I went to check "ldp_interface.h", I found that there actually has =
no this member in "struct ldp_interface".
Thanks.
Timothy
2005.02.01 |
|
From: Jiun-Shian H. <as...@sy...> - 2005-01-31 05:12:09
|
Thanks, it works and I can get zImage for trying. Could you show me some references about the "reasons" that ARM include files or compilers can not to find __exit functions ?! ----- Original Message ----- From: "James R. Leu" <jl...@mi...> To: "Jiun-Shian Ho" <jiu...@gm...> Cc: <mpl...@li...> Sent: Monday, January 31, 2005 12:48 PM Subject: Re: [mpls-linux-general] Compile error on IXP425 |
|
From: James R. L. <jl...@mi...> - 2005-01-31 04:48:43
|
For some reason the ARM include files or compiler are not able to find
the 'exit' functions.
You can try a couple of things, try them one at a time on just one of the
functions and see if the error for that functions disappear.
Here is the original code in mpls_ilm.c:
void __exit mpls_ilm_exit(void)
Try changing it to:
void mpls_ilm_exit(void)
OR try adding this to the end of the file:
EXPORT_SYMBOL(mpls_ilm_exit);
On Mon, Jan 31, 2005 at 12:39:22PM +0800, Jiun-Shian Ho wrote:
> The kernel patch file is from mpls-linux-1.946a.tar.bz2
> and I patch it to official Linux 2.6.9 without *.rej
> (I also tried SRPM from sf.net, but fail, too)
> The attatch is the error log and my config (No IPv6)
>=20
> BTW
> The cross-toolchain is on CentOS v3.1
> I'll try to re-compile kernel on FC-3 again.
>=20
> Thanks for your attention.
>=20
>=20
>=20
>=20
> ----- Original Message -----=20
> From: "James R. Leu" <jl...@mi...>
> To: "Jiun-Shian Ho" <as...@sy...>
> Cc: <mpl...@li...>
> Sent: Monday, January 31, 2005 12:20 PM
> Subject: Re: [mpls-linux-general] Compile error on IXP425
>=20
--=20
James R. Leu
jl...@mi...
|
|
From: Jiun-Shian Ho <jiu...@gm...> - 2005-01-31 04:39:30
|
The kernel patch file is from mpls-linux-1.946a.tar.bz2 and I patch it to official Linux 2.6.9 without *.rej (I also tried SRPM from sf.net, but fail, too) The attatch is the error log and my config (No IPv6) BTW The cross-toolchain is on CentOS v3.1 I'll try to re-compile kernel on FC-3 again. Thanks for your attention. ----- Original Message ----- From: "James R. Leu" <jl...@mi...> To: "Jiun-Shian Ho" <as...@sy...> Cc: <mpl...@li...> Sent: Monday, January 31, 2005 12:20 PM Subject: Re: [mpls-linux-general] Compile error on IXP425 |
|
From: James R. L. <jl...@mi...> - 2005-01-31 04:20:29
|
Did you apply the patch? If so check for rejects: find /usr/src/linux -name '*.rej' Can you include the failures again? On Mon, Jan 31, 2005 at 10:22:00AM +0800, Jiun-Shian Ho wrote: > Yes,=20 > I compiled with configuration like=20 >=20 > Device Drivers ---> > Networking support ---> > Networking options ---> > <*> Multiprotocol Label Switching > ... > <*> IP: MPLS support > ... > <*> IPv6: MPLS support > ... > Network packet filtering (replaces ipchains) ---> > IP: Netfilter Configuration ---> > <*> spec_nh target support > IPv6: Netfilter Configuration ---> > <*> IP6 tables support (required for filtering/masq/NAT) > ... > <*> spec_nh target support >=20 >=20 >=20 > ----- Original Message -----=20 > From: "James R. Leu" <jl...@mi...> > To: "Jiun-Shian Ho" <as...@sy...> > Cc: <mpl...@li...> > Sent: Saturday, January 29, 2005 1:17 AM > Subject: Re: [mpls-linux-general] Compile error on IXP425 >=20 >=20 --=20 James R. Leu jl...@mi... |
|
From: Jiun-Shian H. <as...@sy...> - 2005-01-31 02:24:07
|
Yes,
I compiled with configuration like
Device Drivers --->
Networking support --->
Networking options --->
<*> Multiprotocol Label Switching
...
<*> IP: MPLS support
...
<*> IPv6: MPLS support
...
Network packet filtering (replaces ipchains) --->
IP: Netfilter Configuration --->
<*> spec_nh target support
IPv6: Netfilter Configuration --->
<*> IP6 tables support (required for filtering/masq/NAT)
...
<*> spec_nh target support
----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "Jiun-Shian Ho" <as...@sy...>
Cc: <mpl...@li...>
Sent: Saturday, January 29, 2005 1:17 AM
Subject: Re: [mpls-linux-general] Compile error on IXP425
|
|
From: James R. L. <jl...@mi...> - 2005-01-30 23:51:21
|
If you search the mailing list you will see that LDP is not ready for users. If you are going to help develop it then download the code and dig in. On Sun, Jan 30, 2005 at 06:58:28PM +0530, Kiran Kaipa wrote: > hi, > we have managed to successfully setup quagga and have setup static lsp. > could someone please tell us how to use the ldp functionality in quagga. > thanks > kiran >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2005-01-30 23:50:26
|
As it says in the release notes for 1.946 .... no http://sourceforge.net/project/shownotes.php?release_id=3D299363 Read the examples on http://mpls-linux.sf.net/ On Sun, Jan 30, 2005 at 02:50:30PM +0530, Kiran Kaipa wrote: > hi, > Does MPLS 1.946 support mplsadm2...? > thanks > kiran >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: Kiran K. <kir...@gm...> - 2005-01-30 13:28:33
|
hi, we have managed to successfully setup quagga and have setup static lsp. could someone please tell us how to use the ldp functionality in quagga. thanks kiran |
|
From: Kiran K. <kir...@gm...> - 2005-01-30 09:20:35
|
hi, Does MPLS 1.946 support mplsadm2...? thanks kiran |
|
From: Kiran K. <kir...@gm...> - 2005-01-30 08:57:22
|
hi, I am having problems running this command, mplsadm2 -L eth0:0 it gives me the following error.. MPLSADM mplsadm.c:680:main: Label Space input: eth0:0 MPLSADM mplsadm.c:740:main: Interface: eth0 Label Space: 0 MPLSADM mplsadm.c:753:main: Request or argp is not valid. Set Labelspace: Invalid argument this command has been shown using mplsadm in the user guide. please let us know if there are differences between mplsadm and mplsadm2 command arguments. thanks kiran |
|
From: Kiran K. <kir...@gm...> - 2005-01-30 05:49:17
|
hi, Thanks a lot for the help so far. Our group has successfully installed the kernel and supporting rpms. We could set up an LSP but are still not clear with the commands... could some one please help us in the way to go about implementing a simple test scenario.. also our next step is to implement VPN and diffserv over MPLS linux, can you help us in this regard... thanks kiran |
|
From: James R. L. <jl...@mi...> - 2005-01-29 18:45:18
|
On Sat, Jan 29, 2005 at 09:43:59AM +0530, Kiran Kaipa wrote: > hi, > could some one please tell me what the exact function of quagga and > ldp-portable. > plus, are these two modules required to set up a simple test scenario > with static LSPs. All you _need_ to setup static LSPs is: -MPLS enabled kernel -MPLS enabled iproute2 Optionally you could install: -MPLS enabled iptables -MPLS enabled quagga LDP portable is a library that implements major pieces of RFC3036. It is useless by itself. LDP portable requires the infrastructure of a routing system, such as quagga. BTW please do not post to mpls-linux-devel unless you are asking questions or proposing changes to specific areas of code. > thanks. > kiran >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: Kiran K. <kir...@gm...> - 2005-01-29 04:14:05
|
hi, could some one please tell me what the exact function of quagga and ldp-portable. plus, are these two modules required to set up a simple test scenario with static LSPs. thanks. kiran |
|
From: James R. L. <jl...@mi...> - 2005-01-28 19:16:45
|
Make sure to compile MPLS static into the kernel. The module work is not complete yet. On Fri, Jan 28, 2005 at 05:31:13PM +0800, Jiun-Shian Ho wrote: > Hi, > I try to compile mpls-linux 1.946a on IXP425 platform, > but I encounter errors as attach file. > Can anyone give some hints ? >=20 > Thanks. --=20 James R. Leu jl...@mi... |
|
From: Jiun-Shian H. <as...@sy...> - 2005-01-28 09:31:29
|
Hi,
I try to compile mpls-linux 1.946a on IXP425 platform,
but I encounter errors as attach file.
Can anyone give some hints ?
Thanks. |
|
From: James R. L. <jl...@mi...> - 2005-01-27 15:59:32
|
I uploaded newer versions of the kernel/quagga/mpls-linux files to
sourceforge. These files contain a couple of crucial fixes for MPLS tunnel
interfaces. So anyone who has downloaded the kernel or quagga RPMs you will
want to get the updated ones, I've changed the release number and added
or incremented the letter at the end. Here is a list of the updated
files:
kernel-2.6.9-1.6_FC2mpls_1_946a.src.rpm
kernel-2.6.9-1.6_FC2mpls_1_946a.i686.rpm
quagga-0.97.3-1.FC3mpls1_946b.src.rpm
quagga-0.97.3-1.FC3mpls1_946b.i386.rpm
mpls-linux-1.946a.tar.bz2
In addition I've added new examples to the mpls-linux home page. The
examples cover the new 'mpls' commands usage and the new quagga MPLS CLI
usage as well.
http://mpls-linux.sf.net/
--=20
James R. Leu
jl...@mi...
|
|
From: Kiran K. <kir...@gm...> - 2005-01-27 14:03:29
|
---------- Forwarded message ---------- From: Kiran Kaipa <kir...@gm...> Date: Thu, 27 Jan 2005 19:32:28 +0530 Subject: installing rpms To: mpl...@li... hi, i am a student from Symbiosis Center for Information Technology, Pune, Maharashtra, India. I am currently working on a project which is the study of the working of MPLS on Linux. It would be great if someone could give me insights as to how to go about installing the rpms and more specefically, which build to download for Red Hat 9 or Fedora Core 2. Thanks. Kiran |
|
From: James R. L. <jl...@mi...> - 2005-01-26 15:34:43
|
I do not suggest using mpls-linux 1.172. Please move to a linux 2.6 kernel and use mpls-linux 1.946 On Wed, Jan 26, 2005 at 02:34:19PM +0800, sanjeev ravindran wrote: > Thank you for ur response James, > Things are fine now... Im going ahead.. > However, I would like to clarify one thing----- Is MPLS Linux 1.172 kerne= l patch supports Linux QoS? > Thanks in advance... > With best regards, > Sanjeev R >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > ----- Original Message ----- > From: "James R. Leu" <jl...@mi...> > To: "sanjeev ravindran" <san...@li...> > Subject: Re: [mpls-linux-general] activate label > Date: Sun, 23 Jan 2005 09:21:02 -0600 >=20 > >=20 > > On Sun, Jan 23, 2005 at 03:39:47PM +0800, sanjeev ravindran wrote: > > > Thanks a lot for ur detailed explination James, > > > > > > Things are much clearer now... However, I have one more doubt=20 > > > regarding the same condition in a transit router.. > > > In a transit router, suppose if I bind an incoming label with an=20 > > > outgoing label, traffic is activated right? In this scenario, if=20 > > > I want to inactivate the traffic flow, still want to maintain the=20 > > > incoming-outgoing label binding, is there any way? This=20 > > > requirement will arise if i want to have multiple=20 > > > icoming-outgoing label bindings but still only one is active...=20 > > > Im not very sure if this is required by RSVP-TE.. Im slowly=20 > > > getting hold of it... > >=20 > > You are correct that traffic _could_ flow on that LSP, but for that to = happen > > the ingress LER would have to have mapped map traffic on to it, which t= akes > > us back to the previous email :-) So in general the Ingress LER is the > > only one that has to worry about 'activating' a LSP. > >=20 > >=20 > > > > > > With best regards, > > > Sanjeev R. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > From: "James R. Leu" <jl...@mi...> > > > To: "sanjeev ravindran" <san...@li...> > > > Subject: Re: [mpls-linux-general] activate label > > > Date: Fri, 21 Jan 2005 08:26:30 -0600 > > > > > > > > On Fri, Jan 21, 2005 at 04:26:33PM +0800, sanjeev ravindran wrote: > > > > > Thank you so much for ur response James, > > > > > As you explained, RSVPTE can have back up LSPs. And currently=20 > > > all > > the backup LSPs also will be installed in the forwarding=20 > > > plane. > > But in my perspective, this doesnt serve the actual=20 > > > purpose.. A > > back up LSP needs to be enabled only when the=20 > > > primary LSP fails.. > > In this scenario, there needs to be some=20 > > > mechanism where we can > > bind a label and activate it later=20 > > > for LSPs. Im not sure if this > > is a valid point... This is=20 > > > what I feel... > > > > > One this to remember is that installing the LSP into the forwardi= ng plan > > > > and mapping traffic to it are two different steps. For example I c= an > > > > create 2 LSPs, but only map traffic to one of them. So for all int= ents and > > > > purposes the 2nd LSP is not used for anything. Only when I maps tr= affic to > > > > it will it be used. > > > > > MPLS Linux provides 3 mechanisms for mapping traffic to a LSP: > > > > -spec_nh system which allow IPv4 or IPv6 routes to be mapped to a L= SP > > > > -MPLS tunnel interface represents a LSP as a logical interface. > > > > The interface can be configured to appear as a PtP interface conn= ected > > > > to the egress LER > > > > -spec_nh system can be used in combination with iptables (netfilter= ) to > > > > map and/or mark specific traffic that will traverse a LSP. > > > > > Here is an example of how you could use a MPLS tunnel interface to > > > > facilitate a primary/backup situation. > > > > > An ingress LER uses RSVP-TE to signal 2 LSPs which terminate on t= he same > > > > egress LER, but take two seperate paths through the network. These= LSPs > > > > will be used for for a primary/backup senerio. The ingress LER use= s a > > > > MPLS tunnel interface to map traffic to the primary LSP. It config= ured > > > > the MPLS tunnel interface to look like a PtP connection to the egre= ss LER. > > > > At this point traffic destined to the egress LER used the primary L= SP. > > > > No traffic will traverse the backup LSP. > > > > > If/when the primary LSP breaks, RSVP-TE will receive a path-tear = for the > > > > primary LSP. At that time it will trigger the ingress LER to modif= y the > > > > MPLS tunnel interface and detattach the primary LSP from the MPLS t= unnel > > > > interface and attach the backup LSP to the MPLS tunnel interface (t= he > > > > process of modifing a MPLS tunnel interface to move from one LSP to= another > > > > takes just one system call). At that point traffic destined to the= egress > > > > LER uses the backup LSP. No traffic will attempt to traverse=20 > > > the primary LSP. > > > > > Let me know if this will suit your needs or if you still require = more > > > > functionality. > > > > > > With best regards, > > > > > Sanjeev R > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "James R. Leu" <jl...@mi...> > > > > > To: "sanjeev ravindran" <san...@li...> > > > > > Subject: Re: [mpls-linux-general] activate label > > > > > Date: Thu, 20 Jan 2005 23:14:38 -0600 > > > > > > > > > > > > On Thu, Jan 20, 2005 at 06:34:12PM +0800, sanjeev ravindran w= rote: > > > > > > > Thank you for ur response James, > > > > > > > > > > > > > > Ur explanation cleared my doubts regarding the activation=20 > > > of > > > > labels.. However, i would like to know if the LSP will=20 > > > be > > > > activated [I mean to say traffic will be forwared]=20 > > > when label > > > > binding[installation in to the forwarding=20 > > > plane] is done at the > > > > switch level. > > > > > > > Or is there any way i can bind the label at the switch=20 > > > level > > but > > still keep it inactive? and i can activate it=20 > > > to forward > > traffic > > at a later time? > > > > > > > MPLS linux does not currently implement admin status on=20 > > > each > > MPLS segment. > > > > > > Up till now, I've not seen a need to. I'd be open to implementi= ng it, > > > > > > provided there is a valid application for it. > > > > > > > > Thanks in advance... > > > > > > > With best regards, > > > > > > > Sanjeev R > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "James R. Leu" <jl...@mi...> > > > > > > > To: rameshv <ram...@wi...> > > > > > > > Subject: Re: [mpls-linux-general] activate label > > > > > > > Date: Wed, 19 Jan 2005 09:08:50 -0600 > > > > > > > > > > > > > > > > On Wed, Jan 19, 2005 at 04:20:50PM +0530, rameshv wrote: > > > > > > > > > hi, > > > > > > > > > > > > > > > > > > what is meant by activating label, active connection,=20 > > > > > backup connection ? > > > > > > > > > I believe you are referring to the difference between=20 > > > allocating and > > > > > > > > activating. Allocation is done in the signaling layer. Ty= pically > > > > > > > > activation of a label means to install it into the > >=20 > > > forwarding plane. For > > > > > > > > example RSVP-TE could signal a backup LSP, meaning=20 > > > allocate > > and distribute > > > > > > > > labels for the LSP, but it would only install the=20 > > > labels > > into > > the forwarding > > > > > > > > plane (activate) when the primary LSP fails. > > > > > > > > > (note that the above is a contrived example, all=20 > > > deployed > > implementations > > > > > > > > of RSVP-TE that signal backup LSPs install them into >=20 > > > > forwarding plane prior > > > > > > > > to the failure of the primary LSP) > > > > > > > > > > any help is appreciated > > > > > > > > > > > > > > > > > > regards > > > > > > > > > ramesh > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday b= lues > > > > > > > > > Get a FREE limited edition SourceForge.net t-shirt=20 > > > from ThinkGeek. > > > > > > > > > It's fun and FREE -- well,=20 > > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > > > _______________________________________________ > > > > > > > > > mpls-linux-general mailing list > > > > > > > > > mpl...@li... > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-g= eneral > > > > > > > > > -- > > > > > > > > James R. Leu > > > > > > > > jl...@mi... > > > > > > > > > > ------------------------------------------------------- > > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday blu= es > > > > > > > > Get a FREE limited edition SourceForge.net t-shirt from Thi= nkGeek. > > > > > > > > It's fun and FREE -- well,=20 > > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > > _______________________________________________ > > > > > > > > mpls-linux-general mailing list > > > > > > > > mpl...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-gen= eral > > > > > > > > > > > > > > -- ______________________________________________ > > > > > > > Check out the latest SMS services @=20 > > > http://www.linuxmail.org > > This > > allows you to send and=20 > > > receive SMS through your mailbox. > > > > > > > > > > > > > > > > > > > > > Powered by Outblaze > > > > > > > -- > > > > > > James R. Leu > > > > > > jl...@mi... > > > > > > > > ------------------------------------------------------- > > > > > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive R= eporting > > > > > > Tool for open source databases. Create drag-&-drop reports. Sav= e time > > > > > > by over 75%! Publish reports on the web. Export to DOC, XLS, RT= F, etc. > > > > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > > > > > _______________________________________________ > > > > > > mpls-linux-general mailing list > > > > > > mpl...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > > > > > > > -- ______________________________________________ > > > > > Check out the latest SMS services @ http://www.linuxmail.org=20 > > > This > > allows you to send and receive SMS through your mailbox. > > > > > > > > > > > > > > > Powered by Outblaze > > > > > -- > > > > James R. Leu > > > > jl...@mi... > > > > > > -- ______________________________________________ > > > Check out the latest SMS services @ http://www.linuxmail.org This=20 > > > allows you to send and receive SMS through your mailbox. > > > > > > > > > Powered by Outblaze > >=20 > > -- > > James R. Leu > > jl...@mi... >=20 > --=20 > ______________________________________________ > Check out the latest SMS services @ http://www.linuxmail.org=20 > This allows you to send and receive SMS through your mailbox. >=20 >=20 > Powered by Outblaze --=20 James R. Leu jl...@mi... |
|
From: sanjeev r. <san...@li...> - 2005-01-26 06:34:26
|
Thank you for ur response James, Things are fine now... Im going ahead.. However, I would like to clarify one thing----- Is MPLS Linux 1.172 kernel = patch supports Linux QoS? Thanks in advance... With best regards, Sanjeev R ----- Original Message ----- From: "James R. Leu" <jl...@mi...> To: "sanjeev ravindran" <san...@li...> Subject: Re: [mpls-linux-general] activate label Date: Sun, 23 Jan 2005 09:21:02 -0600 >=20 > On Sun, Jan 23, 2005 at 03:39:47PM +0800, sanjeev ravindran wrote: > > Thanks a lot for ur detailed explination James, > > > > Things are much clearer now... However, I have one more doubt=20 > > regarding the same condition in a transit router.. > > In a transit router, suppose if I bind an incoming label with an=20 > > outgoing label, traffic is activated right? In this scenario, if=20 > > I want to inactivate the traffic flow, still want to maintain the=20 > > incoming-outgoing label binding, is there any way? This=20 > > requirement will arise if i want to have multiple=20 > > icoming-outgoing label bindings but still only one is active...=20 > > Im not very sure if this is required by RSVP-TE.. Im slowly=20 > > getting hold of it... >=20 > You are correct that traffic _could_ flow on that LSP, but for that to ha= ppen > the ingress LER would have to have mapped map traffic on to it, which tak= es > us back to the previous email :-) So in general the Ingress LER is the > only one that has to worry about 'activating' a LSP. >=20 >=20 > > > > With best regards, > > Sanjeev R. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > From: "James R. Leu" <jl...@mi...> > > To: "sanjeev ravindran" <san...@li...> > > Subject: Re: [mpls-linux-general] activate label > > Date: Fri, 21 Jan 2005 08:26:30 -0600 > > > > > > On Fri, Jan 21, 2005 at 04:26:33PM +0800, sanjeev ravindran wrote: > > > > Thank you so much for ur response James, > > > > As you explained, RSVPTE can have back up LSPs. And currently=20 > > all > > the backup LSPs also will be installed in the forwarding=20 > > plane. > > But in my perspective, this doesnt serve the actual=20 > > purpose.. A > > back up LSP needs to be enabled only when the=20 > > primary LSP fails.. > > In this scenario, there needs to be some=20 > > mechanism where we can > > bind a label and activate it later=20 > > for LSPs. Im not sure if this > > is a valid point... This is=20 > > what I feel... > > > > One this to remember is that installing the LSP into the forwarding= plan > > > and mapping traffic to it are two different steps. For example I can > > > create 2 LSPs, but only map traffic to one of them. So for all inten= ts and > > > purposes the 2nd LSP is not used for anything. Only when I maps traf= fic to > > > it will it be used. > > > > MPLS Linux provides 3 mechanisms for mapping traffic to a LSP: > > > -spec_nh system which allow IPv4 or IPv6 routes to be mapped to a LSP > > > -MPLS tunnel interface represents a LSP as a logical interface. > > > The interface can be configured to appear as a PtP interface connec= ted > > > to the egress LER > > > -spec_nh system can be used in combination with iptables (netfilter) = to > > > map and/or mark specific traffic that will traverse a LSP. > > > > Here is an example of how you could use a MPLS tunnel interface to > > > facilitate a primary/backup situation. > > > > An ingress LER uses RSVP-TE to signal 2 LSPs which terminate on the= same > > > egress LER, but take two seperate paths through the network. These L= SPs > > > will be used for for a primary/backup senerio. The ingress LER uses a > > > MPLS tunnel interface to map traffic to the primary LSP. It configur= ed > > > the MPLS tunnel interface to look like a PtP connection to the egress= LER. > > > At this point traffic destined to the egress LER used the primary LSP. > > > No traffic will traverse the backup LSP. > > > > If/when the primary LSP breaks, RSVP-TE will receive a path-tear fo= r the > > > primary LSP. At that time it will trigger the ingress LER to modify = the > > > MPLS tunnel interface and detattach the primary LSP from the MPLS tun= nel > > > interface and attach the backup LSP to the MPLS tunnel interface (the > > > process of modifing a MPLS tunnel interface to move from one LSP to a= nother > > > takes just one system call). At that point traffic destined to the e= gress > > > LER uses the backup LSP. No traffic will attempt to traverse=20 > > the primary LSP. > > > > Let me know if this will suit your needs or if you still require mo= re > > > functionality. > > > > > With best regards, > > > > Sanjeev R > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: "James R. Leu" <jl...@mi...> > > > > To: "sanjeev ravindran" <san...@li...> > > > > Subject: Re: [mpls-linux-general] activate label > > > > Date: Thu, 20 Jan 2005 23:14:38 -0600 > > > > > > > > > > On Thu, Jan 20, 2005 at 06:34:12PM +0800, sanjeev ravindran wro= te: > > > > > > Thank you for ur response James, > > > > > > > > > > > > Ur explanation cleared my doubts regarding the activation=20 > > of > > > > labels.. However, i would like to know if the LSP will=20 > > be > > > > activated [I mean to say traffic will be forwared]=20 > > when label > > > > binding[installation in to the forwarding=20 > > plane] is done at the > > > > switch level. > > > > > > Or is there any way i can bind the label at the switch=20 > > level > > but > > still keep it inactive? and i can activate it=20 > > to forward > > traffic > > at a later time? > > > > > > MPLS linux does not currently implement admin status on=20 > > each > > MPLS segment. > > > > > Up till now, I've not seen a need to. I'd be open to implementing= it, > > > > > provided there is a valid application for it. > > > > > > > Thanks in advance... > > > > > > With best regards, > > > > > > Sanjeev R > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "James R. Leu" <jl...@mi...> > > > > > > To: rameshv <ram...@wi...> > > > > > > Subject: Re: [mpls-linux-general] activate label > > > > > > Date: Wed, 19 Jan 2005 09:08:50 -0600 > > > > > > > > > > > > > > On Wed, Jan 19, 2005 at 04:20:50PM +0530, rameshv wrote: > > > > > > > > hi, > > > > > > > > > > > > > > > > what is meant by activating label, active connection,=20 > > > > backup connection ? > > > > > > > > I believe you are referring to the difference between=20 > > allocating and > > > > > > > activating. Allocation is done in the signaling layer. Typi= cally > > > > > > > activation of a label means to install it into the > >=20 > > forwarding plane. For > > > > > > > example RSVP-TE could signal a backup LSP, meaning=20 > > allocate > > and distribute > > > > > > > labels for the LSP, but it would only install the=20 > > labels > > into > > the forwarding > > > > > > > plane (activate) when the primary LSP fails. > > > > > > > > (note that the above is a contrived example, all=20 > > deployed > > implementations > > > > > > > of RSVP-TE that signal backup LSPs install them into >=20 > > > forwarding plane prior > > > > > > > to the failure of the primary LSP) > > > > > > > > > any help is appreciated > > > > > > > > > > > > > > > > regards > > > > > > > > ramesh > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday blu= es > > > > > > > > Get a FREE limited edition SourceForge.net t-shirt=20 > > from ThinkGeek. > > > > > > > > It's fun and FREE -- well,=20 > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > > _______________________________________________ > > > > > > > > mpls-linux-general mailing list > > > > > > > > mpl...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-gen= eral > > > > > > > > -- > > > > > > > James R. Leu > > > > > > > jl...@mi... > > > > > > > > > ------------------------------------------------------- > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday blues > > > > > > > Get a FREE limited edition SourceForge.net t-shirt from Think= Geek. > > > > > > > It's fun and FREE -- well,=20 > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > _______________________________________________ > > > > > > > mpls-linux-general mailing list > > > > > > > mpl...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-gener= al > > > > > > > > > > > > -- ______________________________________________ > > > > > > Check out the latest SMS services @=20 > > http://www.linuxmail.org > > This > > allows you to send and=20 > > receive SMS through your mailbox. > > > > > > > > > > > > > > > > > > Powered by Outblaze > > > > > > -- > > > > > James R. Leu > > > > > jl...@mi... > > > > > > > ------------------------------------------------------- > > > > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Rep= orting > > > > > Tool for open source databases. Create drag-&-drop reports. Save = time > > > > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF,= etc. > > > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > > > > _______________________________________________ > > > > > mpls-linux-general mailing list > > > > > mpl...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > > > > > -- ______________________________________________ > > > > Check out the latest SMS services @ http://www.linuxmail.org=20 > > This > > allows you to send and receive SMS through your mailbox. > > > > > > > > > > > > Powered by Outblaze > > > > -- > > > James R. Leu > > > jl...@mi... > > > > -- ______________________________________________ > > Check out the latest SMS services @ http://www.linuxmail.org This=20 > > allows you to send and receive SMS through your mailbox. > > > > > > Powered by Outblaze >=20 > -- > James R. Leu > jl...@mi... --=20 ______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org=20 This allows you to send and receive SMS through your mailbox. Powered by Outblaze |
|
From: James R. L. <jl...@mi...> - 2005-01-26 02:16:27
|
The quagga patch that came with probably assumes you are compiling with IPv6 support. Unless your ready to do some coding you might be wasting your time. quagga+ldp is not ready for users. It is in a very unstable state and needs a lot of development work. On Tue, Jan 25, 2005 at 06:30:20PM +0100, tr...@gh... wrote: > Hello! >=20 > I patched Quagga 0.94 with ldp-800. I follow with instruction and when > i try install quagga (./make) occurs an error shown below. Could you > help me ? >=20 > make[2]: Entering directory `$QUAGGA/zebra' > source=3D'zserv.c' object=3D'zserv.o' libtool=3Dno \ > depfile=3D'.deps/zserv.Po' tmpdepfile=3D'.deps/zserv.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 'zserv.c' > || echo './'`zserv.c > zserv.c: In function `zsend_mpls_out_segment_add': > zserv.c:639: error: union has no member named `prefix6' > zserv.c:639: error: union has no member named `ipv6' > zserv.c: In function `zsend_mpls_out_segment_delete': > zserv.c:681: error: union has no member named `prefix6' > zserv.c:681: error: union has no member named `ipv6' > zserv.c: In function `zread_mpls_out_segment_add': > zserv.c:1725: error: union has no member named `ipv6' > zserv.c:1725: error: union has no member named `prefix6' > zserv.c: In function `zread_mpls_out_segment_delete': > zserv.c:1764: error: union has no member named `ipv6' > zserv.c:1764: error: union has no member named `prefix6' > make[2]: *** [zserv.o] Error 1 > make[2]: Leaving directory `$QUAGGA/zebra' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `$QUAGGA/q_96.4' > make: *** [all] Error 2 >=20 >=20 > What's wrong with ipv6? How to repair it? >=20 > Thanks and Regards, > Bartek >=20 > mailto:tr...@gh... >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: <tr...@gh...> - 2005-01-25 17:30:38
|
Hello! I patched Quagga 0.94 with ldp-800. I follow with instruction and when i try install quagga (./make) occurs an error shown below. Could you help me ? make[2]: Entering directory `$QUAGGA/zebra' source=3D'zserv.c' object=3D'zserv.o' libtool=3Dno \ depfile=3D'.deps/zserv.Po' tmpdepfile=3D'.deps/zserv.TPo' \ depmode=3Dgcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -DSYSCONFDIR=3D\"/usr/local/etc/\" -DMULTIPATH_NUM=3D= 1 -I. -I. -I.. -I.. -I.. -I../lib -g -O2 -Wall -c `test -f 'zserv.c' || echo './'`zserv.c zserv.c: In function `zsend_mpls_out_segment_add': zserv.c:639: error: union has no member named `prefix6' zserv.c:639: error: union has no member named `ipv6' zserv.c: In function `zsend_mpls_out_segment_delete': zserv.c:681: error: union has no member named `prefix6' zserv.c:681: error: union has no member named `ipv6' zserv.c: In function `zread_mpls_out_segment_add': zserv.c:1725: error: union has no member named `ipv6' zserv.c:1725: error: union has no member named `prefix6' zserv.c: In function `zread_mpls_out_segment_delete': zserv.c:1764: error: union has no member named `ipv6' zserv.c:1764: error: union has no member named `prefix6' make[2]: *** [zserv.o] Error 1 make[2]: Leaving directory `$QUAGGA/zebra' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `$QUAGGA/q_96.4' make: *** [all] Error 2 What's wrong with ipv6? How to repair it? Thanks and Regards, Bartek mailto:tr...@gh... |
|
From: Bartosz D. <bar...@op...> - 2005-01-25 17:15:20
|
Hello! I patched Quagga 0.94 with ldp-800. I follow with instruction and when i try install quagga (./make) occurs an error shown below. Could you help me ? make[2]: Entering directory `$QUAGGA/zebra' source='zserv.c' object='zserv.o' libtool=no \ depfile='.deps/zserv.Po' tmpdepfile='.deps/zserv.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 'zserv.c' || echo './'`zserv.c zserv.c: In function `zsend_mpls_out_segment_add': zserv.c:639: error: union has no member named `prefix6' zserv.c:639: error: union has no member named `ipv6' zserv.c: In function `zsend_mpls_out_segment_delete': zserv.c:681: error: union has no member named `prefix6' zserv.c:681: error: union has no member named `ipv6' zserv.c: In function `zread_mpls_out_segment_add': zserv.c:1725: error: union has no member named `ipv6' zserv.c:1725: error: union has no member named `prefix6' zserv.c: In function `zread_mpls_out_segment_delete': zserv.c:1764: error: union has no member named `ipv6' zserv.c:1764: error: union has no member named `prefix6' make[2]: *** [zserv.o] Error 1 make[2]: Leaving directory `$QUAGGA/zebra' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `$QUAGGA/q_96.4' make: *** [all] Error 2 What's wrong with ipv6? How to repair it? Thanks and Regards, Bartek mailto:tr...@gh... |
|
From: Fahad D. <fah...@gm...> - 2005-01-24 11:56:19
|
Is there any working implementation of restoration routing which uses RSVP-TE and Fast Reroute? Thanks in advance, Fahad |
533 messages has been excluded from this view by a project administrator.
