mpls-linux-general Mailing List for MPLS for Linux (Page 84)
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: Jikku <ji...@cs...> - 2005-01-24 11:00:35
|
IF anyone has any experience setting up an MPls router could they please mail me back. -- A child when asked to name the seven wonder of the world said: "To touch, to taste, to see, to hear, to run, to laugh and to love." |
|
From: James R. L. <jl...@mi...> - 2005-01-24 04:40:44
|
I have just uploaded the binary and source RPMs for mpls-linux 1.946, tarballs
will follow soon.
Release Name: 1.946
Notes:
The binaries RPMs are built on a Fedora Core 2 installation. The source
RPMs can be used to build binary RPMs for other RPM systems.
Their is no longer a mplsadm2 utility. The CLI for creating LSPs is now
implemented in the 'mpls' utility which is part of the iproute2 package.
Changes:
Kernel changes
-----------------
-remove the procfs interface
-remove most of the sysfs interface
-remove the IOCTL API
-finish the netlink API
-MPLS tunnel interface is no longer a module
-add counter support to the netlink API
iproute2 changes
-------------------
-add all instructions to the 'mpls' utility
-add tunnel support to the 'mpls' utility
-add counter support to the 'mpls' utility
-add mpls-linux version to -V command
iptables changes
------------------
-add mpls-linux version to the -V command
quagga
------
-add the new MPLS framework
I will be updating the mpls-linux.sf.net web page with updated examples
using the 'mpls' utility and the new quagga CLI.
For now here are some simple examples:
'mpls' utility usage
--------------------
mpls nhlfe add key 0 instructions push gen 16 nexthop wlan0 ipv4 192.168.2.1
(output: "Key: 0x2")
mpls ilm add label gen 16 labelspace 0
mpls labelspace add dev eth0 labelspace 0
mpls xc add ilm_label gen 16 ilm_labelspace 0 nhlfe_key 0x2
mpls tunnel add dev mpls0 key 0x2
ip route add 10.0.0.0/24 via 192.168.2.1 spec_nh 0x8847 0x2
quagga MPLS CLI
---------------
Ingress LER
-----------
iler# conf t
iler(config)# ip route 10.0.0.0/24 gen 16 nexthop eth1 192.168.2.1
iler(config)# end
iler# show mpls forwarding
Insegments:
Total 0
Outsegments:
Interface Label Next Hop Owner
eth1 16 192.168.2.1 STATIC
Total 1
Cross Connects:
Total 0
iler# show ip route 10.0.0.0/24
Routing entry for 10.0.0.0/24
Known via "static", distance 1, metric 0, best
* 192.168.2.1, via eth1 (label 16)
iler#
LSR
---
lsr# conf t
lsr(config)# mpls static 0
lsr(config-ls)# label-map gen 16 swap gen 17 nexthop eth1 192.168.3.1
lsr(config-ls)# exit
lsr(config)# int eth0
lsr(config-if)# mpls labelspace 0
lsr(config-if)# end
lsr# show mpls forwarding
Insegments:
Lbl Spc Label Owner
0 16 STATIC
Total 1
Outsegments:
Interface Label Next Hop Owner
eth1 17 192.168.3.1 STATIC
Total 1
Cross Connects:
Lbl Spc In Label Out Label Interface Next Hop Owner
0 16 17 eth1 192.168.3.1 STATIC
Total 1
lsr# show interface eth0
Interface eth0 is up, line protocol detection is disabled
index 8 metric 1 mtu 1500 <UP,BROADCAST,RUNNING,MULTICAST>
HWaddr: 00:05:5d:a6:e4:33
MPLS labelspace 0
inet 192.168.2.1/24 broadcast 192.168.2.255
inet6 fe80::205:5dff:fea6:e433/64
input packets 2737, bytes 1650440, dropped 0, multicast packets 0
input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
output packets 2862, bytes 452923, dropped 0
output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
collisions 0
lsr#
Egress LER
----------
eler# conf t
eler(config)# int eth0
eler(config-if)# mpls labelspace 0
eler(config-if)# exit
eler(config)# mpls static 0
eler(config-ls)# label-map gen 17 pop
eler(config-ls)# end
eler# show mpls forwarding
Insegments:
Lbl Spc Label Owner
0 17 STATIC
Total 1
Outsegments:
Total 0
Cross Connects:
Total 0
eler# show int eth0
Interface eth0 is up, line protocol detection is disabled
index 8 metric 1 mtu 1500 <UP,BROADCAST,MULTICAST>
HWaddr: 00:05:5d:a6:e4:33
MPLS labelspace 0
inet 192.168.3.1/24 broadcast 192.168.3.255
inet6 fe80::205:5dff:fea6:e433/64
input packets 2759, bytes 1657918, dropped 0, multicast packets 0
input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0
output packets 2881, bytes 454579, dropped 0
output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
collisions 0
eler#
Please post questions to the mpl...@li...
--
James R. Leu
jl...@mi...
|
|
From: James R. L. <jl...@mi...> - 2005-01-21 14:26:33
|
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 all the backup LSPs also will be installed in the forwarding plane. But in my perspective, this doesnt serve the actual purpose.. A back up LSP needs to be enabled only when the primary LSP fails.. In this scenario, there needs to be some mechanism where we can bind a label and activate it later for LSPs. Im not sure if this is a valid point... This is 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 intents and
purposes the 2nd LSP is not used for anything. Only when I maps traffic 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 connected
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 LSPs
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 configured
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 for 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 tunnel
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 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 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 wrote:
> > > Thank you for ur response James,
> > >
> > > Ur explanation cleared my doubts regarding the activation of
> > > labels.. However, i would like to know if the LSP will be
> > > activated [I mean to say traffic will be forwared] when label
> > > binding[installation in to the forwarding plane] is done at the
> > > switch level.
> > > Or is there any way i can bind the label at the switch level but
> > > still keep it inactive? and i can activate it to forward traffic
> > > at a later time?
> >
> > MPLS linux does not currently implement admin status on 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, backup connection ?
> > > > > I believe you are referring to the difference between allocating and
> > > > activating. Allocation is done in the signaling layer. Typically
> > > > activation of a label means to install it into the forwarding plane. For
> > > > example RSVP-TE could signal a backup LSP, meaning allocate and distribute
> > > > labels for the LSP, but it would only install the labels into
> > > the forwarding
> > > > plane (activate) when the primary LSP fails.
> > > > > (note that the above is a contrived example, all deployed implementations
> > > > of RSVP-TE that signal backup LSPs install them into 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 blues
> > > > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > > > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > > --
> > > > 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 ThinkGeek.
> > > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > > > _______________________________________________
> > > > 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 This
> > > allows you to send and receive SMS through your mailbox.
> > >
> > >
> > > Powered by Outblaze
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
> >
> > -------------------------------------------------------
> > 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
>
> --
> ______________________________________________
> Check out the latest SMS services @ http://www.linuxmail.org
> This allows you to send and receive SMS through your mailbox.
>
>
> Powered by Outblaze
--
James R. Leu
jl...@mi...
|
|
From: sanjeev r. <san...@li...> - 2005-01-21 08:26:48
|
Thank you so much for ur response James, As you explained, RSVPTE can have back up LSPs. And currently all the backu= p LSPs also will be installed in the forwarding plane. But in my perspectiv= e, this doesnt serve the actual purpose.. A back up LSP needs to be enabled= only when the primary LSP fails.. In this scenario, there needs to be some= mechanism where we can bind a label and activate it later for LSPs. Im no= t sure if this is a valid point... This is what I feel...=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: Thu, 20 Jan 2005 23:14:38 -0600 >=20 > On Thu, Jan 20, 2005 at 06:34:12PM +0800, sanjeev ravindran wrote: > > Thank you for ur response James, > > > > Ur explanation cleared my doubts regarding the activation of=20 > > labels.. However, i would like to know if the LSP will be=20 > > activated [I mean to say traffic will be forwared] when label=20 > > binding[installation in to the forwarding plane] is done at the=20 > > switch level. > > Or is there any way i can bind the label at the switch level but=20 > > still keep it inactive? and i can activate it to forward traffic=20 > > at a later time? >=20 > MPLS linux does not currently implement admin status on 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. >=20 > > 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, backup connec= tion ? > > > > I believe you are referring to the difference between allocating and > > > activating. Allocation is done in the signaling layer. Typically > > > activation of a label means to install it into the forwarding plane. = For > > > example RSVP-TE could signal a backup LSP, meaning allocate and distr= ibute > > > labels for the LSP, but it would only install the labels into=20 > > the forwarding > > > plane (activate) when the primary LSP fails. > > > > (note that the above is a contrived example, all deployed implement= ations > > > of RSVP-TE that signal backup LSPs install them into 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 blues > > > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshi= rt > > > > _______________________________________________ > > > > mpls-linux-general mailing list > > > > mpl...@li... > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > -- > > > 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 ThinkGeek. > > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > > _______________________________________________ > > > 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 This=20 > > allows you to send and receive SMS through your mailbox. > > > > > > Powered by Outblaze >=20 > -- > James R. Leu > jl...@mi... >=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 ______________________________________________ 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-21 05:14:40
|
On Thu, Jan 20, 2005 at 06:34:12PM +0800, sanjeev ravindran wrote: > Thank you for ur response James, > > Ur explanation cleared my doubts regarding the activation of labels.. However, i would like to know > if the LSP will be activated [I mean to say traffic will be forwared] when label binding[installation in to the forwarding plane] is done at the switch level. > Or is there any way i can bind the label at the switch level but still keep it inactive? and i can activate it to > forward traffic at a later time? MPLS linux does not currently implement admin status on 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, backup connection ? > > > > I believe you are referring to the difference between allocating and > > activating. Allocation is done in the signaling layer. Typically > > activation of a label means to install it into the forwarding plane. For > > example RSVP-TE could signal a backup LSP, meaning allocate and distribute > > labels for the LSP, but it would only install the labels into the forwarding > > plane (activate) when the primary LSP fails. > > > > (note that the above is a contrived example, all deployed implementations > > of RSVP-TE that signal backup LSPs install them into 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 blues > > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > > _______________________________________________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > -- > > 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 ThinkGeek. > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > 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 > This allows you to send and receive SMS through your mailbox. > > > Powered by Outblaze -- James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2005-01-21 05:04:20
|
It depends what you mean. You can create as many LSPs as you want, and only create FEC binding for one, thus traffic only flows on that LSP. All you have to do is change the FEC binding and you can move traffic to the 'backup' LSP. If this doesn't fit your needs, let me know what would and we'll see if existing features can meet it, otherwise I'm open to implementing new features. On Fri, Jan 21, 2005 at 12:46:25PM +0800, ramesh selvaraj wrote: > hi > > is it possible to create backup lsp using mplsadm2 > if posiible how. > just for experimental purpose > > regards > selvaraj > -- > ______________________________________________ > Check out the latest SMS services @ http://www.linuxmail.org > This allows you to send and receive SMS through your mailbox. > > > Powered by Outblaze > > > ------------------------------------------------------- > 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 -- James R. Leu jl...@mi... |
|
From: ramesh s. <ram...@li...> - 2005-01-21 04:46:42
|
hi=20 is it possible to create backup lsp using mplsadm2 if posiible how. just for experimental purpose regards selvaraj --=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: sanjeev r. <san...@li...> - 2005-01-20 10:34:26
|
Thank you for ur response James, Ur explanation cleared my doubts regarding the activation of labels.. Howev= er, i would like to know=20 if the LSP will be activated [I mean to say traffic will be forwared] when = label binding[installation in to the forwarding plane] is done at the switc= h level. Or is there any way i can bind the label at the switch level but still keep= it inactive? and i can activate it to=20 forward traffic at a later time? 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 >=20 > On Wed, Jan 19, 2005 at 04:20:50PM +0530, rameshv wrote: > > hi, > > > > what is meant by activating label, active connection, backup connection= ? >=20 > I believe you are referring to the difference between allocating and > activating. Allocation is done in the signaling layer. Typically > activation of a label means to install it into the forwarding plane. For > example RSVP-TE could signal a backup LSP, meaning allocate and distribute > labels for the LSP, but it would only install the labels into the forward= ing > plane (activate) when the primary LSP fails. >=20 > (note that the above is a contrived example, all deployed implementations > of RSVP-TE that signal backup LSPs install them into forwarding plane pri= or > to the failure of the primary LSP) >=20 > > any help is appreciated > > > > regards > > ramesh > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > mpls-linux-general mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general >=20 > -- > James R. Leu > jl...@mi... >=20 >=20 > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=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-19 15:06:34
|
On Wed, Jan 19, 2005 at 04:20:50PM +0530, rameshv wrote: > hi, > > what is meant by activating label, active connection, backup connection ? I believe you are referring to the difference between allocating and activating. Allocation is done in the signaling layer. Typically activation of a label means to install it into the forwarding plane. For example RSVP-TE could signal a backup LSP, meaning allocate and distribute labels for the LSP, but it would only install the labels into the forwarding plane (activate) when the primary LSP fails. (note that the above is a contrived example, all deployed implementations of RSVP-TE that signal backup LSPs install them into 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 blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu jl...@mi... |
|
From: rameshv <ram...@wi...> - 2005-01-19 10:51:03
|
hi, what is meant by activating label, active connection, backup connection ? any help is appreciated regards ramesh |
|
From: sanjeev r. <san...@li...> - 2005-01-19 09:49:49
|
Hi, I would like to know what is meant by activation of a label... or activatio= n of an LSP from the implementation perspective.. how it is different from = binding a label? when label is binded, it will get activated- thats what I = believe.. is it right? This may sound silly..=20 With best regards,=20 Sanjeev --=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-19 05:03:30
|
<snip>
> The command: "mplsadm2 -I gen:16:0 -O -0x2 -B" doesn't work here.
^
Make sure you're not type the dash like you have it above.
Otherwise it looks like a valid command. Check the output from the
kernel by doing a 'dmesg', maybe it will point you to the problem. If
you're not getting any kernel output from the bind command then some how
you're using the wrong syntax. To make sure we're seeing the same things
try using the 'script' command to record your work:
# script
Script started, file is typescript
<work work work>
# exit
Script done, file is typescript
Then send me the contents of the file 'typescript'
> The binding command at [R4] has to be a different one ( I tried different order of the components -I, gen:16:0, -B, 0x2 ...without success).
> I ran tcpdump at output of [R4] (eth1), no packets.
>
> On [R5]:
> I plan to have:
> mplsadm2 -A -I gen:16:0 -i pop:peek
> mplsadm2 -L eth0:0
>
>
>
> First I try to send ping to 10.0.3.0 network. Yet I didn't worry about the reply. Probably I just need to flip the direction.
>
> Problem is at [R4], unless you have other suggestions for the rest.
>
> Again sorry for the confusion I made. Thanks for any reply.
>
>
> mpl...@li... wrote:Send mpls-linux-general mailing list submissions to
> mpl...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> or, via email, send a message with subject or body 'help' to
> mpl...@li...
>
> You can reach the person managing the list at
> mpl...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mpls-linux-general digest..."
>
>
> Today's Topics:
>
> 1. Help needs to apply mpls patch (sanjeev ravindran)
> 2. Re: A smaller network for label stack, mpls-linux-general digest, Vol 1 #730 - 2 msgs (murat)
> 3. Correction of network configurtation (murat)
>
> --__--__--
>
> Message: 1
> From: "sanjeev ravindran"
> To: mpl...@li...
> Date: Mon, 17 Jan 2005 13:19:41 +0800
> Subject: [mpls-linux-general] Help needs to apply mpls patch
>
> Hi,=20=20
> =20
> I have a doubt... can i apply the mpls-linux patch of 1.938 version to a 2.=
> 4-20 kernel..=20
> however, in the readme file it is specified to be for 2.6.6...=20
> any help will be most appreciated...=20
> thanks in advance,=20
> sanjeev=20
> --=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
>
>
> --__--__--
>
> Message: 2
> Date: Mon, 17 Jan 2005 07:18:37 -0800 (PST)
> From: murat
> Subject: Re: [mpls-linux-general] A smaller network for label stack, mpls-linux-general digest, Vol 1 #730 - 2 msgs
> To: mpl...@li...
>
> --0-578198851-1105975117=:85386
> Content-Type: text/plain; charset=us-ascii
>
> Hi James and all.
> (First of all: thank you for your great work.)
>
> The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors.
>
> For setting up my system I used the RMP packages from
> sf-net:
> iproute-2.4.7-14mpls_1_938.i386.rpm
> iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
> kernel-2.6.8-1.521mpls_1_938a.i686.rpm
> mplsadm2-1.938-1.i386.rpm
>
> [root@Rio root]# uname -a
> Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
> CDT 2004 i686 athlon i386 GNU/Linux
>
> [root@Rio root]# more /etc/fedora-release
> Fedora Core release 2 (Tettnang)
> [root@Rio root]# rpm -qa | grep tcpdump
> tcpdump-3.8.2-3
>
> I'm very very short of time for finishing my thesis.
>
>
>
>
> [R1] eth0:10.0.1.50/24
>
>
>
>
> ?? IP packet ?? IP packet
>
> (ping 10.0.3.50) (ping reply)
>
>
>
> [R2] eth0:10.0.1.1/24
>
> eth1:10.0.2.1/30
>
>
>
>
> ?? MPLS ?? MPLS
>
>
>
>
>
> [R3] eth0:10.0.2.2/30
>
> eth1:10.0.4.5/30
>
>
>
>
> ?? MPLS ?? MPLS
>
>
>
>
>
> [R4] eth0:10.0.2.6/30
>
> eth1:10.0.8.9/30
>
>
>
> ?? MPLS ?? MPLS
>
>
>
>
>
> [R5] eth0:10.0.8.10/30
>
> eth1:10.0.3.1/24
>
>
>
>
> ?? IP packet ?? IP packet
>
> (ping 10.0.3.50) (ping reply)
>
>
>
> [R6] eth0:10.0.3.50/24
>
>
>
> Can you help me realizing this network. It is possible to make "forwarding" or "multiple pushes" at [R2], [R3], [R4] and [R5]. The documentation I have seems to be to old even I couldn't find any newer one (MPLS for Linux Developer's Guide, James Leu, Ramon Casellas, 2003 - and - mpls-linux-1.938.tar.bz2 /utils/README)
>
> Thanks in advance for any help.
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> --0-578198851-1105975117=:85386
> Content-Type: text/html; charset=us-ascii
>
>
> Hi James and all.
>
> (First of all: thank you for your great work.)
>
>
>
> The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors.
>
>
>
> For setting up my system I used the RMP packages from
> sf-net:
> iproute-2.4.7-14mpls_1_938.i386.rpm
> iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
> kernel-2.6.8-1.521mpls_1_938a.i686.rpm
> mplsadm2-1.938-1.i386.rpm
>
> [root@Rio root]# uname -a
> Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
> CDT 2004 i686 athlon i386 GNU/Linux
>
>
> [root@Rio root]# more /etc/fedora-release
> Fedora Core release 2 (Tettnang)
> [root@Rio root]# rpm -qa | grep tcpdump
> tcpdump-3.8.2-3
>
>
> I'm very very short of time for finishing my thesis.
>
>
>
>
>
>
>
>
> [R1] eth0:10.0.1.50/24
>
>
> size=3>
>
>
>
> ?? IP packet ?? IP packet
>
>
> (ping 10.0.3.50) (ping reply)
>
>
>
>
>
> [R2] eth0:10.0.1.1/24
>
>
> eth1:10.0.2.1/30
>
>
>
>
>
>
> ?? MPLS ?? MPLS
>
>
>
>
>
>
>
>
> [R3] eth0:10.0.2.2/30
>
>
> eth1:10.0.4.5/30
>
>
>
>
>
>
> ?? MPLS ?? MPLS g=DE
> style="mso-ansi-language: DE">
>
>
>
>
>
>
>
>
> [R4] eth0:10.0.2.6/30
>
>
> 3"> eth1:10.0.8.9/30
>
>
>
>
>
> ?? MPLS ?? MPLS g=DE
> style="mso-ansi-language: DE">
>
>
>
>
>
>
>
>
> [R5] eth0:10.0.8.10/30
>
>
> eth1:10.0.3.1/24
>
>
>
>
>
>
> ?? IP packet ?? IP packet
>
>
> === message truncated ===
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - Helps protect you from nasty viruses.
--
James R. Leu
jl...@mi...
|
|
From: murat <te...@ya...> - 2005-01-18 23:32:33
|
Again sorry on network configuration, it's a crying shame having stolen your time on this, I was to fast :-( Here what I did: On [R2]: mplsadm2 -A -O 0 -o push:gen:16:set:eth1:ipv4:10.0.2.2 (key 0x2) ip route add 10.0.3.0/24 via 10.0.2.2 spec_nh 0x8847 0x2 advmss 1452 On [R3]: mplsadm2 -A -O 0 -o push:gen:1160:push:gen:16:set:eth1:ipv4:10.0.2.6 (key 0x2) mplsadm2 -L eth0:0 mplsadm2 -A -I gen:16:0 mplsadm2 -I gen:16:0 -O -0x2 -B I can capture MPLS label "16" at [R3] (eth0) :-) I can capture MPLS labels "16" and "1160"at [R3] (eth1) :-) On [R4]: mplsadm2 -A -O 0 -o push:gen:16:set:eth1:ipv4:10.0.2.10 (key 0x2) mplsadm2 -L eth0:0 mplsadm2 -A -I gen:1160:0 -i pop:peek With above settings I can capture MPLS labels "16" and "1160" at [R4] (eth0) :-) The command: "mplsadm2 -I gen:16:0 -O -0x2 -B" doesn't work here. The binding command at [R4] has to be a different one ( I tried different order of the components -I, gen:16:0, -B, 0x2 ...without success). I ran tcpdump at output of [R4] (eth1), no packets. On [R5]: I plan to have: mplsadm2 -A -I gen:16:0 -i pop:peek mplsadm2 -L eth0:0 First I try to send ping to 10.0.3.0 network. Yet I didn't worry about the reply. Probably I just need to flip the direction. Problem is at [R4], unless you have other suggestions for the rest. Again sorry for the confusion I made. Thanks for any reply. mpl...@li... wrote:Send mpls-linux-general mailing list submissions to mpl...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/mpls-linux-general or, via email, send a message with subject or body 'help' to mpl...@li... You can reach the person managing the list at mpl...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of mpls-linux-general digest..." Today's Topics: 1. Help needs to apply mpls patch (sanjeev ravindran) 2. Re: A smaller network for label stack, mpls-linux-general digest, Vol 1 #730 - 2 msgs (murat) 3. Correction of network configurtation (murat) --__--__-- Message: 1 From: "sanjeev ravindran" To: mpl...@li... Date: Mon, 17 Jan 2005 13:19:41 +0800 Subject: [mpls-linux-general] Help needs to apply mpls patch Hi,=20=20 =20 I have a doubt... can i apply the mpls-linux patch of 1.938 version to a 2.= 4-20 kernel..=20 however, in the readme file it is specified to be for 2.6.6...=20 any help will be most appreciated...=20 thanks in advance,=20 sanjeev=20 --=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 --__--__-- Message: 2 Date: Mon, 17 Jan 2005 07:18:37 -0800 (PST) From: murat Subject: Re: [mpls-linux-general] A smaller network for label stack, mpls-linux-general digest, Vol 1 #730 - 2 msgs To: mpl...@li... --0-578198851-1105975117=:85386 Content-Type: text/plain; charset=us-ascii Hi James and all. (First of all: thank you for your great work.) The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors. For setting up my system I used the RMP packages from sf-net: iproute-2.4.7-14mpls_1_938.i386.rpm iptables-1.2.9-2.3.1mpls_1_938.i386.rpm kernel-2.6.8-1.521mpls_1_938a.i686.rpm mplsadm2-1.938-1.i386.rpm [root@Rio root]# uname -a Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28 CDT 2004 i686 athlon i386 GNU/Linux [root@Rio root]# more /etc/fedora-release Fedora Core release 2 (Tettnang) [root@Rio root]# rpm -qa | grep tcpdump tcpdump-3.8.2-3 I'm very very short of time for finishing my thesis. [R1] eth0:10.0.1.50/24 « IP packet ª IP packet (ping 10.0.3.50) (ping reply) [R2] eth0:10.0.1.1/24 eth1:10.0.2.1/30 « MPLS ª MPLS [R3] eth0:10.0.2.2/30 eth1:10.0.4.5/30 « MPLS ª MPLS [R4] eth0:10.0.2.6/30 eth1:10.0.8.9/30 « MPLS ª MPLS [R5] eth0:10.0.8.10/30 eth1:10.0.3.1/24 « IP packet ª IP packet (ping 10.0.3.50) (ping reply) [R6] eth0:10.0.3.50/24 Can you help me realizing this network. It is possible to make "forwarding" or "multiple pushes" at [R2], [R3], [R4] and [R5]. The documentation I have seems to be to old even I couldn't find any newer one (MPLS for Linux Developer's Guide, James Leu, Ramon Casellas, 2003 - and - mpls-linux-1.938.tar.bz2 /utils/README) Thanks in advance for any help. --------------------------------- Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. --0-578198851-1105975117=:85386 Content-Type: text/html; charset=us-ascii Hi James and all. (First of all: thank you for your great work.) The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors. For setting up my system I used the RMP packages from sf-net: iproute-2.4.7-14mpls_1_938.i386.rpm iptables-1.2.9-2.3.1mpls_1_938.i386.rpm kernel-2.6.8-1.521mpls_1_938a.i686.rpm mplsadm2-1.938-1.i386.rpm [root@Rio root]# uname -a Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28 CDT 2004 i686 athlon i386 GNU/Linux [root@Rio root]# more /etc/fedora-release Fedora Core release 2 (Tettnang) [root@Rio root]# rpm -qa | grep tcpdump tcpdump-3.8.2-3 I'm very very short of time for finishing my thesis. [R1] eth0:10.0.1.50/24 size=3> « IP packet ª IP packet (ping 10.0.3.50) (ping reply) [R2] eth0:10.0.1.1/24 eth1:10.0.2.1/30 « MPLS ª MPLS [R3] eth0:10.0.2.2/30 eth1:10.0.4.5/30 « MPLS ª MPLS g=DE style="mso-ansi-language: DE"> [R4] eth0:10.0.2.6/30 3"> eth1:10.0.8.9/30 « MPLS ª MPLS g=DE style="mso-ansi-language: DE"> [R5] eth0:10.0.8.10/30 eth1:10.0.3.1/24 « IP packet ª IP packet === message truncated === --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. |
|
From: James R. L. <jl...@mi...> - 2005-01-18 15:00:28
|
I believe I answered this question last time you posted it.
"There is no need to include advanced configuration commands when
the basics do not work.
I'm not sure what you mean by 'struct ldp seems unfinished'. The
main parts of the ldp control structures are in ldp-portable not in
the 'quagga-wrapper'."
On Tue, Jan 18, 2005 at 08:53:57PM +0800, ?????x wrote:
> Hi James,
>
> I have a question between ldp-portable-0.310 and ldp-portable-0.800.
> The programmer uses "struct mpls_interface" in ldp-portable-0.310 patch file, but "stuct
> ldp_interface" in ldp-portable-0.800 patch file.
>
> It seems that there is no data member named ldp in ldp_interface.h, so all related commands
> in ldp_vty.c were marked by #if 0.
>
> Why to change that? Could you give me some hint, maybe I can help to test ldp code.
>
>
> ldp_vty.c - 0.310
>
> 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 = vty->index;
> struct mpls_interface *mi = (struct mpls_interface*)ifp->info;
> struct ldp_interface *li = mi->ldp;
>
>
> ldp_vty.c - 0.800
>
> 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 = vty->index;
> struct ldp_interface *li = (struct ldp_interface*)ifp->info;
> struct ldp *ldp = li->ldp;
>
>
>
> ldp_interface.h - there is no data member named ldp
>
> struct ldp_interface {
> struct interface *ifp;
> struct connected *connected;
> struct l2cc_interface *l2cc;
>
> ldp_entity entity;
> ldp_if iff;
> mpls_bool configured;
> mpls_bool admin_up;
> mpls_bool create_on_hold;
> int labelspace;
> };
>
>
>
> Thanks.
>
> Timothy
> 2005.01.06
--
James R. Leu
jl...@mi...
|
|
From: <m9...@cn...> - 2005-01-18 12:48:48
|
Hi James,
I have a question between ldp-portable-0.310 and ldp-portable-0.800.
The programmer uses "struct mpls_interface" in ldp-portable-0.310 patch =
file, but "stuct
ldp_interface" in ldp-portable-0.800 patch file.
=20
It seems that there is no data member named ldp in ldp_interface.h, so =
all related commands
in ldp_vty.c were marked by #if 0.
Why to change that? Could you give me some hint, maybe I can help to =
test ldp code.
=20
=20
ldp_vty.c - 0.310=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 mpls_interface *mi =3D (struct mpls_interface*)ifp->info;
struct ldp_interface *li =3D mi->ldp;
=20
=20
ldp_vty.c - 0.800=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
=20
=20
ldp_interface.h - there is no data member named ldp
=20
struct ldp_interface {
struct interface *ifp;
struct connected *connected;
struct l2cc_interface *l2cc;
=20
ldp_entity entity;
ldp_if iff;
mpls_bool configured;
mpls_bool admin_up;
mpls_bool create_on_hold;
int labelspace;
};
=20
=20
=20
Thanks.
=20
Timothy
2005.01.06
|
|
From: James R. L. <jl...@mi...> - 2005-01-18 02:40:39
|
No. You can not apply any of the 1.1xx patches to 2.4 kernels. I nolonger support 2.4 kernels. On Mon, Jan 17, 2005 at 01:19:41PM +0800, sanjeev ravindran wrote: > Hi, > > I have a doubt... can i apply the mpls-linux patch of 1.938 version to a 2.4-20 kernel.. > however, in the readme file it is specified to be for 2.6.6... > any help will be most appreciated... > thanks in advance, > sanjeev > -- > ______________________________________________ > Check out the latest SMS services @ http://www.linuxmail.org > This allows you to send and receive SMS through your mailbox. > > > Powered by Outblaze > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu jl...@mi... |
|
From: murat <te...@ya...> - 2005-01-17 17:48:58
|
Sorry for sending this a second time. Network configuration was not visible as I expected.
And I discovered a mistake at [R4]:
Old: [R4] eth0:10.0.2.6/30
New: [R4] eth0:10.0.4.6/30
Hi James and all.
(First of all: thank you for your great work.)
The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors.
For setting up my system I used the RMP packages from
sf-net:
iproute-2.4.7-14mpls_1_938.i386.rpm
iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
kernel-2.6.8-1.521mpls_1_938a.i686.rpm
mplsadm2-1.938-1.i386.rpm
[root@Rio root]# uname -a
Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
CDT 2004 i686 athlon i386 GNU/Linux
[root@Rio root]# more /etc/fedora-release
Fedora Core release 2 (Tettnang)
[root@Rio root]# rpm -qa | grep tcpdump
tcpdump-3.8.2-3
I'm very very short of time for finishing my thesis.
Network configuration:
Sending (ping 10.0.3.50) downwards, getting (ping reply) upwards.
[R1] eth0:10.0.1.50/24
| IP packet /\ IP packet
\/ (ping 10.0.3.50) | (ping reply)
[R2] eth0:10.0.1.1/24
eth1:10.0.2.1/30
| MPLS /\ MPLS
\/ |
[R3] eth0:10.0.2.2/30
eth1:10.0.4.5/30
| MPLS /\ MPLS
\/ |
[R4] eth0:10.0.4.6/30
eth1:10.0.8.9/30
| MPLS /\ MPLS
\/ |
[R5] eth0:10.0.8.10/30
eth1:10.0.3.1/24
| IP packet /\ IP packet
\/ (ping 10.0.3.50) | (ping reply)
[R6] eth0:10.0.3.50/24
Can you help me realizing this network. It is possible to make "forwarding" or "multiple pushes" at [R2], [R3], [R4] and [R5]. The documentation I have seems to be to old even I couldn't find any newer one (MPLS for Linux Developer's Guide, James Leu, Ramon Casellas, 2003 - and - mpls-linux-1.938.tar.bz2 /utils/README).
Thanks in advance for any help.
---------------------------------
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses. |
|
From: murat <te...@ya...> - 2005-01-17 15:18:49
|
Hi James and all.
(First of all: thank you for your great work.)
The problem that I face with MPLS is: The documentation is to old. When I try to follow the instuctions or type the commands in the documentation - I get lot of errors.
For setting up my system I used the RMP packages from
sf-net:
iproute-2.4.7-14mpls_1_938.i386.rpm
iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
kernel-2.6.8-1.521mpls_1_938a.i686.rpm
mplsadm2-1.938-1.i386.rpm
[root@Rio root]# uname -a
Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
CDT 2004 i686 athlon i386 GNU/Linux
[root@Rio root]# more /etc/fedora-release
Fedora Core release 2 (Tettnang)
[root@Rio root]# rpm -qa | grep tcpdump
tcpdump-3.8.2-3
I'm very very short of time for finishing my thesis.
[R1] eth0:10.0.1.50/24
« IP packet ª IP packet
(ping 10.0.3.50) (ping reply)
[R2] eth0:10.0.1.1/24
eth1:10.0.2.1/30
« MPLS ª MPLS
[R3] eth0:10.0.2.2/30
eth1:10.0.4.5/30
« MPLS ª MPLS
[R4] eth0:10.0.2.6/30
eth1:10.0.8.9/30
« MPLS ª MPLS
[R5] eth0:10.0.8.10/30
eth1:10.0.3.1/24
« IP packet ª IP packet
(ping 10.0.3.50) (ping reply)
[R6] eth0:10.0.3.50/24
Can you help me realizing this network. It is possible to make "forwarding" or "multiple pushes" at [R2], [R3], [R4] and [R5]. The documentation I have seems to be to old even I couldn't find any newer one (MPLS for Linux Developer's Guide, James Leu, Ramon Casellas, 2003 - and - mpls-linux-1.938.tar.bz2 /utils/README)
Thanks in advance for any help.
---------------------------------
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone. |
|
From: sanjeev r. <san...@li...> - 2005-01-17 05:19:48
|
Hi,=20=20 =20 I have a doubt... can i apply the mpls-linux patch of 1.938 version to a 2.= 4-20 kernel..=20 however, in the readme file it is specified to be for 2.6.6...=20 any help will be most appreciated...=20 thanks in advance,=20 sanjeev=20 --=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: windtim\@libero\.i <wi...@li...> - 2005-01-14 15:25:16
|
Hi,
i'm testing MPLS on Linux on a network with 3 Linux box. I wo=
uld like to
show like MPLS router can work following IP standard. My que=
stion is: if i
configure a pc installing on it software for MPLS but i =
don't set LSP, NHLFE
ecc can i consider it an MPLS router? For me it can=
consider it an MPLS router
working on IP standard. Is it correct? Thank=
s in advance for the help
=0A=0A=0A=0A__________________________________=
__________________________=0ALibero ADSL: 3 mesi gratis e navighi a 1.2 M=
ega. E poi hai l'Adsl senza limiti a meno di 1 euro al giorno. =0AAbbonat=
i subito senza costi di attivazione su http://www.libero.it=0A=0A
|
|
From: windtim <wi...@li...> - 2005-01-14 05:25:55
|
Hi, i'm looking messages about MPLS speed and, in one of these, i've read " mpls skb dump messages", What are they? Can you make me an example? How they can affect efficiency of router? Thanks in advance for the help P.S.:Excuse me for the duplicate mail |
|
From: windtim <wi...@li...> - 2005-01-14 05:24:53
|
Hi, i'm looking messages about MPLS speed and, in one of these, i've read " mpls skb dump messages", What are they? Can you make me an example? How they can affect speed of router? Thanks in advance for the help |
|
From: windtim <wi...@li...> - 2005-01-14 04:58:39
|
Hi,
i'm testing MPLS Linux on a network with 3 Linux box. I've
noticed that when i don't bind label space to an interface (mplsadm - L
ethx:0) and try to ping an host traffic goes but on video i don't see
nothing while when i make this association it is possible to see all the
comunications between hosts. Why does it happen? I've tryed to see if
packets have MPLS header and i've found it correctly. Can you help me?
Thanks in advance for the help
|
|
From: James R. L. <jl...@mi...> - 2005-01-13 18:28:33
|
The method for binding a NHLFE to a tunnel changed somewhere between
the writting of the example you read and the the release of 1.938, it
will be changing again when I release 1.945
In 1.938 you need to use the sysfs filesystem. You might need to
create a directory and mount it before you'll be able to use it.
For example:
mkdir /sys
mount -t sysfs sysfs /sys
Then you will have a /sys/mpls directory that has tunnel, nhlfe, and ilm
information. To bind the NHLFE to the tunnel, you echo the NHLFE index to
the tunnels nhlfe file, something like:
echo 0x2 > /sys/mpls/tunnel/mpls0/nhlfe
(I do not remeber the exact file name, you will have to look around to
find it)
On Thu, Jan 13, 2005 at 10:06:53AM -0800, murat wrote:
> Hello James and all.
>
> Maybe you remember I couldn't run graphical-ethereal.
> It still doesn't but tethereal and tcpdump work.
>
> For setting up my system I used the RMP packages from
> sf-net:
> iproute-2.4.7-14mpls_1_938.i386.rpm
> iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
> kernel-2.6.8-1.521mpls_1_938a.i686.rpm
> mplsadm2-1.938-1.i386.rpm
>
> [root@Rio root]# uname -a
> Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
> CDT 2004 i686 athlon i386 GNU/Linux
> [root@Rio root]# more /etc/fedora-release
> Fedora Core release 2 (Tettnang)
> [root@Rio root]# rpm -qa | grep tcpdump
> tcpdump-3.8.2-3
>
>
> I worked with your MPLS-Linux example
> -------- eth1 11.0.1.0/24 eth1 --------
> | uml1 |----------------------------| uml2 |
> --------.1 .2--------
> I get different output messages from the computer then
> you do:
> [root@Rio root]# ls /proc/net/mpls/
> in labelspaces out tunnels
>
> uml 1
> [root@Rio root]# cat /proc/net/mpls_version
> cat: /proc/net/mpls_version: No such file or directory
> [root@Rio root]# mplsadm2 -A -O 0
> MPLSADM mplsadm.c:692:main: Out segment input: 0
> Key: 0x00000002
> Out Segment add: Success
> [root@Rio root]# mplsadm2 -O 0x2 -o
> push:gen:10000:set:eth0:ipv4:192.168.20.2
> MPLSADM mplsadm.c:692:main: Out segment input: 0x2
> MPLSADM mplsadm.c:688:main: Out instr input:
> push:gen:10000:set:eth0:ipv4:192.168.20.2
> MPLSADM mplsadm.c:292:fill_instructions: Instruction:
> push
> MPLSADM mplsadm.c:229:fill_label: Label type: gen
> MPLSADM mplsadm.c:292:fill_instructions: Instruction:
> set
> MPLSADM mplsadm.c:181:parse_nh_info: eth0
> MPLSADM mplsadm.c:182:parse_nh_info: 192.168.20.2
> MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol:
> ipv4
> MPLSADM mplsadm.c:596:fill_instructions: Length: 2
> Out Instr: Success
> [root@Rio root]# ip route add 192.168.20.2/32 via
> 192.168.20.2 spec_nh 0x8847 0x2
> [root@Rio root]# cat /proc/net/mpls_out
> cat: /proc/net/mpls_out: No such file or directory
> [root@Rio root]# cat /proc/net/mpls/out
> NHLFE Key:0x00000002 Instruction Set
> PUSH PUSH(gen 10000)
> SET SET(eth0,ipv4 192.168.20.2)
>
>
>
> [root@Rio root]# ip route show
> 192.168.20.2 via 192.168.20.2 dev eth0 spec_nh 0x8847
> 0x00000002
> 192.168.20.0/24 dev eth0 scope link
> 192.168.0.0/24 dev eth1 scope link
> 169.254.0.0/16 dev eth0 scope link
> 127.0.0.0/8 dev lo scope link
> default via 192.168.0.1 dev eth1
>
>
> uml 2
> [root@Rio root]# mplsadm2 -L eth0:0
> MPLSADM mplsadm.c:680:main: Label Space input: eth0:0
> MPLSADM mplsadm.c:740:main: Interface: eth0 Label
> Space: 0
> Set Labelspace: Success
> [root@Rio root]# mplsadm2 -A -I gen:11000:0
> MPLSADM mplsadm.c:676:main: In label input:
> gen:11000:0
> MPLSADM mplsadm.c:229:fill_label: Label type: gen
> In Label add: Success
> [root@Rio root]# cat /proc/net/mpls_in
> cat: /proc/net/mpls_in: No such file or directory
> [root@Rio root]# cat /proc/net/mpls/in
> ILM Key:0x02af8001 Instruction Set
> POP
> PEEK
>
> I could send/receive/capture MPLS packets with this
> example. Thanks a lot!
>
>
> I don't know what's wrong, but something seems to be
> bad with my mpls settings.
>
>
> Problem: MPLS Tunnel Interfaces
> [root@Rio root]# mplsadm2 -A -O 0 -o
> push:gen:1024:set:eth0:ipv4:192.168.20.3
> MPLSADM mplsadm.c:692:main: Out segment input: 0
> MPLSADM mplsadm.c:688:main: Out instr input:
> push:gen:1024:set:eth0:ipv4:192.168.20.3
> Key: 0x00000003
> Out Segment add: Success
> MPLSADM mplsadm.c:292:fill_instructions: Instruction:
> push
> MPLSADM mplsadm.c:229:fill_label: Label type: gen
> MPLSADM mplsadm.c:292:fill_instructions: Instruction:
> set
> MPLSADM mplsadm.c:181:parse_nh_info: eth0
> MPLSADM mplsadm.c:182:parse_nh_info: 192.168.20.3
> MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol:
> ipv4
> MPLSADM mplsadm.c:596:fill_instructions: Length: 2
> Out Instr: Success
> [root@Rio root]# mplsadm2 -A -T mpls0
> MPLSADM mplsadm.c:696:main: Tunnel input: mpls0
> [root@Rio root]# ifconfig mpls0 192.168.20.1 netmask
> 255.255.255.255
> [root@Rio root]# mplsadm2 -B -O 0x3 -T mpls0
> MPLSADM mplsadm.c:692:main: Out segment input: 0x3
> MPLSADM mplsadm.c:696:main: Tunnel input: mpls0
> Using mplsadm2 to bind/unbind MOIs to tunnels is
> deprecated in 2.6
> Use:
> echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-mpls0/moi
> to bind / unbind a MOI to a tunnel
> Bind/Unbind MOI: Invalid argument
>
> Binding of the outgoing label to the tunnel doesn't
> work.
> Pleeeease help me out of this. Thank you very much in
> advance. (Sorry for writing so much, this way it was
> easier to explane for me)
>
>
>
>
>
>
>
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Helps protect you from nasty viruses.
> http://promotions.yahoo.com/new_mail
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
--
James R. Leu
jl...@mi...
|
|
From: murat <te...@ya...> - 2005-01-13 18:06:57
|
Hello James and all.
Maybe you remember I couldn't run graphical-ethereal.
It still doesn't but tethereal and tcpdump work.
For setting up my system I used the RMP packages from
sf-net:
iproute-2.4.7-14mpls_1_938.i386.rpm
iptables-1.2.9-2.3.1mpls_1_938.i386.rpm
kernel-2.6.8-1.521mpls_1_938a.i686.rpm
mplsadm2-1.938-1.i386.rpm
[root@Rio root]# uname -a
Linux Rio 2.6.8-1.521mpls_1_938a #1 Sun Oct 3 21:20:28
CDT 2004 i686 athlon i386 GNU/Linux
[root@Rio root]# more /etc/fedora-release
Fedora Core release 2 (Tettnang)
[root@Rio root]# rpm -qa | grep tcpdump
tcpdump-3.8.2-3
I worked with your MPLS-Linux example
-------- eth1 11.0.1.0/24 eth1 --------
| uml1 |----------------------------| uml2 |
--------.1 .2--------
I get different output messages from the computer then
you do:
[root@Rio root]# ls /proc/net/mpls/
in labelspaces out tunnels
uml 1
[root@Rio root]# cat /proc/net/mpls_version
cat: /proc/net/mpls_version: No such file or directory
[root@Rio root]# mplsadm2 -A -O 0
MPLSADM mplsadm.c:692:main: Out segment input: 0
Key: 0x00000002
Out Segment add: Success
[root@Rio root]# mplsadm2 -O 0x2 -o
push:gen:10000:set:eth0:ipv4:192.168.20.2
MPLSADM mplsadm.c:692:main: Out segment input: 0x2
MPLSADM mplsadm.c:688:main: Out instr input:
push:gen:10000:set:eth0:ipv4:192.168.20.2
MPLSADM mplsadm.c:292:fill_instructions: Instruction:
push
MPLSADM mplsadm.c:229:fill_label: Label type: gen
MPLSADM mplsadm.c:292:fill_instructions: Instruction:
set
MPLSADM mplsadm.c:181:parse_nh_info: eth0
MPLSADM mplsadm.c:182:parse_nh_info: 192.168.20.2
MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol:
ipv4
MPLSADM mplsadm.c:596:fill_instructions: Length: 2
Out Instr: Success
[root@Rio root]# ip route add 192.168.20.2/32 via
192.168.20.2 spec_nh 0x8847 0x2
[root@Rio root]# cat /proc/net/mpls_out
cat: /proc/net/mpls_out: No such file or directory
[root@Rio root]# cat /proc/net/mpls/out
NHLFE Key:0x00000002 Instruction Set
PUSH PUSH(gen 10000)
SET SET(eth0,ipv4 192.168.20.2)
[root@Rio root]# ip route show
192.168.20.2 via 192.168.20.2 dev eth0 spec_nh 0x8847
0x00000002
192.168.20.0/24 dev eth0 scope link
192.168.0.0/24 dev eth1 scope link
169.254.0.0/16 dev eth0 scope link
127.0.0.0/8 dev lo scope link
default via 192.168.0.1 dev eth1
uml 2
[root@Rio root]# mplsadm2 -L eth0:0
MPLSADM mplsadm.c:680:main: Label Space input: eth0:0
MPLSADM mplsadm.c:740:main: Interface: eth0 Label
Space: 0
Set Labelspace: Success
[root@Rio root]# mplsadm2 -A -I gen:11000:0
MPLSADM mplsadm.c:676:main: In label input:
gen:11000:0
MPLSADM mplsadm.c:229:fill_label: Label type: gen
In Label add: Success
[root@Rio root]# cat /proc/net/mpls_in
cat: /proc/net/mpls_in: No such file or directory
[root@Rio root]# cat /proc/net/mpls/in
ILM Key:0x02af8001 Instruction Set
POP
PEEK
I could send/receive/capture MPLS packets with this
example. Thanks a lot!
I don't know what's wrong, but something seems to be
bad with my mpls settings.
Problem: MPLS Tunnel Interfaces
[root@Rio root]# mplsadm2 -A -O 0 -o
push:gen:1024:set:eth0:ipv4:192.168.20.3
MPLSADM mplsadm.c:692:main: Out segment input: 0
MPLSADM mplsadm.c:688:main: Out instr input:
push:gen:1024:set:eth0:ipv4:192.168.20.3
Key: 0x00000003
Out Segment add: Success
MPLSADM mplsadm.c:292:fill_instructions: Instruction:
push
MPLSADM mplsadm.c:229:fill_label: Label type: gen
MPLSADM mplsadm.c:292:fill_instructions: Instruction:
set
MPLSADM mplsadm.c:181:parse_nh_info: eth0
MPLSADM mplsadm.c:182:parse_nh_info: 192.168.20.3
MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol:
ipv4
MPLSADM mplsadm.c:596:fill_instructions: Length: 2
Out Instr: Success
[root@Rio root]# mplsadm2 -A -T mpls0
MPLSADM mplsadm.c:696:main: Tunnel input: mpls0
[root@Rio root]# ifconfig mpls0 192.168.20.1 netmask
255.255.255.255
[root@Rio root]# mplsadm2 -B -O 0x3 -T mpls0
MPLSADM mplsadm.c:692:main: Out segment input: 0x3
MPLSADM mplsadm.c:696:main: Tunnel input: mpls0
Using mplsadm2 to bind/unbind MOIs to tunnels is
deprecated in 2.6
Use:
echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-mpls0/moi
to bind / unbind a MOI to a tunnel
Bind/Unbind MOI: Invalid argument
Binding of the outgoing label to the tunnel doesn't
work.
Pleeeease help me out of this. Thank you very much in
advance. (Sorry for writing so much, this way it was
easier to explane for me)
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
|
533 messages has been excluded from this view by a project administrator.
