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

Re: [mpls-linux-general] BETA: mpls-linux 1.128

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

On Tue, Feb 05, 2002 at 03:18:41PM +0100, Steven Van den Berghe wrote:
> The scenario i was looking at looks like (ingress LER):
> 
> * use ingress queueing to meter/police traffic and mark traffic internally to 
> a certain DSCP (i.e. set tcindex)
> 
> * use firewall to classify <src, dst, whatever you can give me) and select 
> output opcode chain
> 
> * use tc_fwd to select outgoing label/exp/outgoing interface based on tcindex 
> (so firewalling points to tc_fwd instruction, and tc_fwd intruction maps each 
> tcindex to the correct push(label):set_exp(exp):set(inteface).
> 
> So, is this a valid scenario for the use of tc_fwd ?

This sounds like a great scenario.  I will add a complete version of tc_fwd :-)

Jim

> 
> Cheers,
> Steven
> 
> On Tuesday 05 February 2002 17:03, James R. Leu wrote:
> > It wasn't fully implemented and I haven't had anyone give me a good example
> > of how it would be used.  If it is needed, I can add it back (completly
> > implemented this time).
> >
> > Jim
> >
> > On Tue, Feb 05, 2002 at 10:54:05AM +0100, Steven Van den Berghe wrote:
> > > Hi Jim,
> > >
> > > I haven't been able to catch up on some of the discussions on the list in
> > > the last few weeks, but i couldn't find a reason why MPLS_OP_TC_FWD has
> > > disappeared between release 1.126 and 1.127. Can i just merge it back in,
> > > or am i (as happened before) missing a subtile point here?
> > >
> > > cheers,
> > > Steven
> > >
> > > On Tuesday 05 February 2002 07:50, James R. Leu wrote:
> > > > I commit mpls-linux 1.128 to CVS. It contains only minor
> > > > changes.  The most noticible of which is the fact that
> > > > netdevices are now reference counted correctly (or so I
> > > > think) so if you've ever seen some odd messages about
> > > > netdevices not being released while rebooting, this should
> > > > get rid of them (as long as you manually remove all of the
> > > > outgoing labels).
> > > >
> > > > This release also contains more fixes from Stefano (thanks)
> > > > and the start of new and improved documentation.  If anyone
> > > > has some documentation they think would be a good addition
> > > > or want to update an existing document, sent it my way and
> > > > I'll consider including it.
> > > >
> > > > Jim
> > >
> > > --
> > > Steven Van den Berghe
> > > ste...@in...
> > > Workgroup Broadband Communication Networks
> > > Department Information Technology
> > > Ghent University - Belgium
> > > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > >  A Windows user spends 1/3 of his life sleeping, 1/3
> > >  working, 1/3 waiting.
> > >
> > >
> > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> 
> -- 
> Steven Van den Berghe             
> ste...@in...
> Workgroup Broadband Communication Networks
> Department Information Technology 
> Ghent University - Belgium
> Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>  I cna ytpe 300 wrods pre mniuet!!!  
>  
>  
>  
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>  

-- 
James R. Leu

[mpls-linux-general] =?iso-8859-1?Q?RE:_mpls_beta_1.127_-_Diffserv?=

[=?utf-8?Q?<avi...@li...>]

SGkgUGF1bCwNCg0KZmlyc3Qgb2YgYWxsIGdldCB0aGUgbGF0ZXN0IHZlcnNpb24gKDEuMTI4
KSBvZiBtcGxzLWxpbnV4IGZyb20gQ1ZTICh0aGUgDQp0YWcgaXMgbXBscy1saW51eF8xXzEp
LCB3aGljaCBzb2x2ZXMgc29tZSBidWdzLg0KVGhlIG1hc2sgb2YgZHMyZXhwIGluc3RydWN0
aW9uIGFwcGxpZXMgdG8gdGhlIERTIGNvZGUgcG9pbnQsIHNvIHlvdSANCmhhdmUgdG8gc3Bl
Y2lmeSBmb3IgbWFzayBhIHZhbHVlIGxlc3MgdGhhbiA2NCAodGhlIG51bWJlciBvZiBwb3Nz
aWJsZSANCkRTQ1BzKS4NCg0KU3RlZmFubw==

Re: [mpls-linux-general] BETA: mpls-linux 1.128

[Steven V. d. B. <ste...@in...>]

The scenario i was looking at looks like (ingress LER):

* use ingress queueing to meter/police traffic and mark traffic internally to 
a certain DSCP (i.e. set tcindex)

* use firewall to classify <src, dst, whatever you can give me) and select 
output opcode chain

* use tc_fwd to select outgoing label/exp/outgoing interface based on tcindex 
(so firewalling points to tc_fwd instruction, and tc_fwd intruction maps each 
tcindex to the correct push(label):set_exp(exp):set(inteface).

So, is this a valid scenario for the use of tc_fwd ?

Cheers,
Steven

On Tuesday 05 February 2002 17:03, James R. Leu wrote:
> It wasn't fully implemented and I haven't had anyone give me a good example
> of how it would be used.  If it is needed, I can add it back (completly
> implemented this time).
>
> Jim
>
> On Tue, Feb 05, 2002 at 10:54:05AM +0100, Steven Van den Berghe wrote:
> > Hi Jim,
> >
> > I haven't been able to catch up on some of the discussions on the list in
> > the last few weeks, but i couldn't find a reason why MPLS_OP_TC_FWD has
> > disappeared between release 1.126 and 1.127. Can i just merge it back in,
> > or am i (as happened before) missing a subtile point here?
> >
> > cheers,
> > Steven
> >
> > On Tuesday 05 February 2002 07:50, James R. Leu wrote:
> > > I commit mpls-linux 1.128 to CVS. It contains only minor
> > > changes.  The most noticible of which is the fact that
> > > netdevices are now reference counted correctly (or so I
> > > think) so if you've ever seen some odd messages about
> > > netdevices not being released while rebooting, this should
> > > get rid of them (as long as you manually remove all of the
> > > outgoing labels).
> > >
> > > This release also contains more fixes from Stefano (thanks)
> > > and the start of new and improved documentation.  If anyone
> > > has some documentation they think would be a good addition
> > > or want to update an existing document, sent it my way and
> > > I'll consider including it.
> > >
> > > Jim
> >
> > --
> > Steven Van den Berghe
> > ste...@in...
> > Workgroup Broadband Communication Networks
> > Department Information Technology
> > Ghent University - Belgium
> > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> >  A Windows user spends 1/3 of his life sleeping, 1/3
> >  working, 1/3 waiting.
> >
> >
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

-- 
Steven Van den Berghe             
ste...@in...
Workgroup Broadband Communication Networks
Department Information Technology 
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 I cna ytpe 300 wrods pre mniuet!!!  
 
 
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 

Re: [mpls-linux-general] BETA: mpls-linux 1.128

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

It wasn't fully implemented and I haven't had anyone give me a good example
of how it would be used.  If it is needed, I can add it back (completly
implemented this time).

Jim

On Tue, Feb 05, 2002 at 10:54:05AM +0100, Steven Van den Berghe wrote:
> Hi Jim,
> 
> I haven't been able to catch up on some of the discussions on the list in the 
> last few weeks, but i couldn't find a reason why MPLS_OP_TC_FWD has 
> disappeared between release 1.126 and 1.127. Can i just merge it back in, or 
> am i (as happened before) missing a subtile point here?
> 
> cheers,
> Steven
> 
> On Tuesday 05 February 2002 07:50, James R. Leu wrote:
> > I commit mpls-linux 1.128 to CVS. It contains only minor
> > changes.  The most noticible of which is the fact that
> > netdevices are now reference counted correctly (or so I
> > think) so if you've ever seen some odd messages about
> > netdevices not being released while rebooting, this should
> > get rid of them (as long as you manually remove all of the
> > outgoing labels).
> >
> > This release also contains more fixes from Stefano (thanks)
> > and the start of new and improved documentation.  If anyone
> > has some documentation they think would be a good addition
> > or want to update an existing document, sent it my way and
> > I'll consider including it.
> >
> > Jim
> 
> -- 
> Steven Van den Berghe             
> ste...@in...
> Workgroup Broadband Communication Networks
> Department Information Technology 
> Ghent University - Belgium
> Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>  A Windows user spends 1/3 of his life sleeping, 1/3
>  working, 1/3 waiting.  
>  
>  
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>  

-- 
James R. Leu

Re: [mpls-linux-general] BETA: mpls-linux 1.128

[Steven V. d. B. <ste...@in...>]

Hi Jim,

I haven't been able to catch up on some of the discussions on the list in the 
last few weeks, but i couldn't find a reason why MPLS_OP_TC_FWD has 
disappeared between release 1.126 and 1.127. Can i just merge it back in, or 
am i (as happened before) missing a subtile point here?

cheers,
Steven

On Tuesday 05 February 2002 07:50, James R. Leu wrote:
> I commit mpls-linux 1.128 to CVS. It contains only minor
> changes.  The most noticible of which is the fact that
> netdevices are now reference counted correctly (or so I
> think) so if you've ever seen some odd messages about
> netdevices not being released while rebooting, this should
> get rid of them (as long as you manually remove all of the
> outgoing labels).
>
> This release also contains more fixes from Stefano (thanks)
> and the start of new and improved documentation.  If anyone
> has some documentation they think would be a good addition
> or want to update an existing document, sent it my way and
> I'll consider including it.
>
> Jim

-- 
Steven Van den Berghe             
ste...@in...
Workgroup Broadband Communication Networks
Department Information Technology 
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 A Windows user spends 1/3 of his life sleeping, 1/3
 working, 1/3 waiting.  
 
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 

[mpls-linux-general] BETA: mpls-linux 1.128

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

I commit mpls-linux 1.128 to CVS. It contains only minor
changes.  The most noticible of which is the fact that
netdevices are now reference counted correctly (or so I
think) so if you've ever seen some odd messages about
netdevices not being released while rebooting, this should
get rid of them (as long as you manually remove all of the
outgoing labels).

This release also contains more fixes from Stefano (thanks)
and the start of new and improved documentation.  If anyone
has some documentation they think would be a good addition
or want to update an existing document, sent it my way and
I'll consider including it.

Jim
-- 
James R. Leu

Re: [mpls-linux-general] Mpls beta 1.127 - Deleting outgoing labels.

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

On Mon, Feb 04, 2002 at 12:24:02PM -0500, ncc49a wrote:
> Hi,
> 
>   I am trying out the newest mpls for linux.  I have problems deleting 
> outgoing labels from the /proc/net/mpls_out with the -D flag. It returns 
> error: No such process.

Make sure to use -D -O key:<key> where key if found in the first field of
mpls_out.  You can no longer use -D -O gen:16:eth1 or the like.

Summary:

-When creating an outgoing label info (-A -O) you MUST use the
 gen:<label>:<interface> notation
-All other uses of -O use the key:<key> notation.  Get the key from mpls_out
-Al uses of -I use the gen:<label>:<labelspace> notation

>   I wonder if anyone has encountered this?
> 
>   Thanks.
> 
> Paul
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Status of CR-LDP on Linux

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

On Mon, Feb 04, 2002 at 03:37:33PM +0100, Josip Gracin wrote:
> Hello!
> 
> Could someone please tell me what is the current status of CR-LDP support
> in Linux?  I see some CR-LDP code in ldp-portable distribution but OTOH I
> also see CR-LDP on the TODO list of the project.

It is not complete.

> Also, are there any other implementations of CR-LDP available, besides
> ldp-portable, that is?

None that I know of, although there was recently a post to the IETF MPLS
mailing list about a multi-threaded LDP implementation, you may want to check
with them to see if they have added the CR extentions.

Alternativly you could help finish the CR extentions for ldp-portable.

Jim

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

-- 
James R. Leu

[mpls-linux-general] Re: Help & Guide ME

[Irfan L. <il...@vi...>]

Muzammil,

Go to http://www.antd.nist.gov/itg/nistswitch/

Download the NIST switch and start playing with it.

I dont think it has VPN in it. but you can try to add it.

Hope this helps!
Irfan Lateef

Muzammil Ahmad Khan wrote:

> Respected Sir,
>
> My name is Muzammil Ahmad Khan.
>
> I am doing research on Implementation on MPLS in VPN's".
>
> I want to have guidence from you for this purpose.
>
> I want some simulations to study regarding MPLS.
>
> If u have in any platform plz mail me
>
> I will be very thankful to you.
>
> Regards,
> Muzammil
> ________
>
> ----- Original Message -----
> From: "Lakshmikantha A.S" <a_k...@re...>
> To: <jl...@mi...>
> Cc: <mpl...@li...>; <mpl...@mp...>
> Sent: Friday, February 01, 2002 6:17 PM
> Subject: Hello Sir
>
> >
> > Hello,
> >   I am a M.Sc(Computer Science ) student.Presently I am doing a project of
> "Development of MPLS Based Router".
> > I am working on Cyrix CPU with 128MB RAM on RedHat Linux7.1 on
> Kernel-2.4.2-2.I am using mpls-linux-0.990 for mplsadm utility.Now I enabled
> both the systems with mplsadm by adding the patch and compiling the kernel
> and make mplsadm.
> >
> >     Before using the mplsadm , both the systems r pinging each other and i
> was able to make FTP and telnet also.after I use mplsadm on both the system
> , they r pinging each other.but when i give FTP or telnet to remote system ,
> the system in which i gave the ftp or telnet will display the 1 to 2 pages
> of error like below and will hang.
> >
> >   CPU:0
> > EFLAGS:00010292
> > eax:0000001c ebx:c085bfb0 ecx:c351c000 edx:c0322ce4
> > esi:c085bfc7 edi:   some number       ebp:        esp:
> >
> > ds:0018  es :0018 ss:0018
> >
> > Process kapm-idled (pid:3,stackpage=c1157000)
> > stack:c02f20cb
> >
> > Call trace:[<c02f20cb>]
> >
> >
> >
> >
> > junk numbers
> >
> >
> >
> >
> > code : 0f 0b 83 c4 0c c3 a1 4c .........
> >
> >
> >
> > Kernel panic:Aiee,killing interrupt handler!
> > In interrupt handler-not syncing.
> >
> >
> >
> > -----------------------------------
> >
> > of course some more r there befor this page which has passed in prevous
> screen while those errors occured.
> >
> > I tried for 5 or 6 times.I am getting the same problem.
> > So what may be the reason.Please do suggest some solutions for this.I am
> waiting for solution.because without this I  cant procced further.
> >
> > SO please ........please help me .
> >
> >
> >
> > With Regards,
> > Kantha.
> >
> >
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

--
Irfan Lateef
Village Networks Inc,

[mpls-linux-general] Status of CR-LDP on Linux

[Josip G. <gr...@te...>]

Hello!

Could someone please tell me what is the current status of CR-LDP support
in Linux?  I see some CR-LDP code in ldp-portable distribution but OTOH I
also see CR-LDP on the TODO list of the project.

Also, are there any other implementations of CR-LDP available, besides
ldp-portable, that is?

Thanks!
Josip

[mpls-linux-general] mpls beta 1.127 - Diffserv

[ncc49a <nc...@si...>]

Hi James,

	I am trying out the diffserv functionality for the latest mpls patch.

 	When I input this instruction:

$MPLSADM -v -A -O gen:37:eth0 -o 
ds2exp:0xff:0x1a:0x1:push:gen:37:set:eth0:ipv4:192.168.1.161 

 	I get the errors saying: 
1) Mask for ds2exp is too large, must be less then 0x40
2) Out Instr: No such device or address.

 	I must be using the above instruction wrongly. Can u provide me some 
pointers on this?

	Next, for the above mask... is it applied to the DS code point or the entire 
DS field? I am not sure, but I think "tc" from iproute2 applies the mask to 
the whole field..., such that a mask of 0x3 and a DS field of 0x6b will give 
a DS Code Point of 0x1a, which is AF. 

	Thanks a lot!

Paul

Re: [mpls-linux-general] BETA: mpls-linux 1.127

[Olivier D. <Oli...@rd...>]

James R. Leu wrote:

> On Fri, Feb 01, 2002 at 06:08:05PM +0100, Olivier Dugeon wrote:
> <snip>
>  > My trouble is that in the case of PRE_ROUTING nf_hook (ie. before the
>  > packet is route) the dst field is not set for the packet. So, if you
>  > would use the PRE_ROUTING netfilter hook, i think this scenario will
>  > happen :
>  >
>  >   - first packet arrive, dst field is null because no such flow raise
>  > this Ingress node.
>  >   - PRE_ROUTING netfilter doesn't setup the mpls stuff because the dst
>  > filed is null
>  >   - the packet continue its journey and get a dst field after calling
>  > ip_route_input function. The skb->dst->output remain unchange to
>  > ip_route_output, so this packet is process as usual and not labeled.
>  >   - second packet arrive, dst field is null, and the packet retrieve its
>  > dst field from the route hash table.
>  >
>  > In the case of PRE_ROUTING netfilter setup, (iptables -A INPUT) the
>  > packets is never labeled.
>  >
>  > If it's not a bug, it's preferable to avoid setting mpls-key with
>  > iptable for the PRE_ROUTING nf_hook.
> 
> I had not planned on the MPLS target to be used with the PRE_ROUTING hook.


Ok. Is what i'm thinking.


> 
>  > Second trouble, and i think it's more serious. You can't make difference
>  >
>  > for two flows with same IP src and dst address but with different port
>  > src and/or dst number. PRE_ROUTING dosen't work, so 2 packets comming
>  > from the same machine to the same machine get the same dst field :-(
>  > The ip_route_input function use IP src, dst address, input/output
>  > interface number, tos fied and optionnaly fwmark. So, you can't make any
>  > difference based on the source or destination port number or protocol.
> 
> So are you saying that if the MPLS target worked with PRE_ROUTING
> this problem would be solved?


Not completely. The only way i found to differentiate to flow for the 
same peer machine is to use nfmark to force the routing kernel mechanism 
  to create two differents dst entry (ie. two route cache entries)


> 
>  > Solution: I'll follow the PRE_ROUTING trak. I think it's possible to
>  > setup the dst field in netfilter mpls hook. So,
> 
> Each MOI can potentially have a dst (as part of the SET info).  So
> the the packets hitting PRE_ROUTING could use that, or a dst could be 
> built,
> that has the necessary info to redirect the packet to the MPLS layer.
> Another option is to ship the packet into the MPLS layer form inside the
> NF_HOOK, and return that is was dropped.


Ok. Perhaps this is the way to skip part of the ip routing stuff. Just 
keep the header verification and the segmentation stuff.


> 
>  > 1/ we can make difference between packet based on all field header
>  > 2/ we skipp low routing process
>  >
>  > What do you think about this ? I am wrong ?
> 
> I think it is good that you brought this up (support for port/protocol 
> based
> redirection).  Although I'm not sure how often it will be used.  MPLS isn't
> meant for microflow TE.


We would use this forwarding descrimination in conjonction with CR-LDP 
or/and RSVP-TE (we use i propriary stack for the moment).


> 
> Until we figure out a better way to do this, you could use a combination
> of iptables (do nfmark or dsmark based on protocol/port, making sure the
> aggregate route points out a mpls tunnel interface) and a nffwd or dsfwd
> instruction on the MOI which is attached to the mpls tunnel interface.
> 


Ok. I try it.


Olivier

-- 
  FTR&D/DAC/CPN
  Technopole Anticipa     | mailto:Oli...@fr...
  2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
  F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52

[mpls-linux-general] Mpls beta 1.127 - Deleting outgoing labels.

[ncc49a <nc...@si...>]

Hi,

  I am trying out the newest mpls for linux.  I have problems deleting 
outgoing labels from the /proc/net/mpls_out with the -D flag. It returns 
error: No such process.

  I wonder if anyone has encountered this?

  Thanks.

Paul

Re: [mpls-linux-general] Question about dummy0

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

I do not use the dummy interface, I instead use user-mode-linux to
provide me a network of upto 5 virtual machines.
Take a look at http://sf.net/projects/user-mode-linux/

Jim

On Sat, Feb 02, 2002 at 08:23:10PM -0800, Cheng Zhengchao wrote:
> Hi,All,
>   I am trying ldp_linux now.I only have 2 pc now,in
> order to establish LSP and bind FEC/Label,I must use
> dummy0 interface?What is the purpose of dummy?
>   After "ifconfig dummy0",can I config a virtual net
> via dummy?For example
>  ifconfig dummy0 1.2.3.4
>  route add -net 10.1.1.0/24 gw 1.2.3.4
> In fact,the net 10.1.1.0/24 does not exist.Can such
> config establish a LSP?
> 
>  Best Regard 
> 
> Cheng
> 
> __________________________________________________
> Do You Yahoo!?
> Great stuff seeking new owners in Yahoo! Auctions! 
> http://auctions.yahoo.com
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Help & Guide ME

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

Your best bet will be to start by looking at zebra (http://www.zebra.org).
It has a MPLS BGP VPN implementation.  It is just lacking the binding to
a MPLS tunnel.  If ldp-portable were fully integrated into zebra, the
result should be a full MPLS BGP VPN implementation.

Jim

On Sat, Feb 02, 2002 at 11:42:53AM +0500, Muzammil Ahmad Khan wrote:
> 
> 
> Respected Sir,
> 
> My name is Muzammil Ahmad Khan.
> 
> I am doing research on Implementation on MPLS in VPN's".
> 
> I want to have guidence from you for this purpose.
> 
> I want some simulations to study regarding MPLS.
> 
> If u have in any platform plz mail me
> 
> 
> I will be very thankful to you.
> 
> Regards,
> Muzammil
> ________
> 
> 
> ----- Original Message -----
> From: "Lakshmikantha A.S" <a_k...@re...>
> To: <jl...@mi...>
> Cc: <mpl...@li...>; <mpl...@mp...>
> Sent: Friday, February 01, 2002 6:17 PM
> Subject: Hello Sir
> 
> 
> >
> > Hello,
> >   I am a M.Sc(Computer Science ) student.Presently I am doing a project of
> "Development of MPLS Based Router".
> > I am working on Cyrix CPU with 128MB RAM on RedHat Linux7.1 on
> Kernel-2.4.2-2.I am using mpls-linux-0.990 for mplsadm utility.Now I enabled
> both the systems with mplsadm by adding the patch and compiling the kernel
> and make mplsadm.
> >
> >     Before using the mplsadm , both the systems r pinging each other and i
> was able to make FTP and telnet also.after I use mplsadm on both the system
> , they r pinging each other.but when i give FTP or telnet to remote system ,
> the system in which i gave the ftp or telnet will display the 1 to 2 pages
> of error like below and will hang.
> >
> >   CPU:0
> > EFLAGS:00010292
> > eax:0000001c ebx:c085bfb0 ecx:c351c000 edx:c0322ce4
> > esi:c085bfc7 edi:   some number       ebp:        esp:
> >
> > ds:0018  es :0018 ss:0018
> >
> > Process kapm-idled (pid:3,stackpage=c1157000)
> > stack:c02f20cb
> >
> > Call trace:[<c02f20cb>]
> >
> >
> >
> >
> > junk numbers
> >
> >
> >
> >
> > code : 0f 0b 83 c4 0c c3 a1 4c .........
> >
> >
> >
> > Kernel panic:Aiee,killing interrupt handler!
> > In interrupt handler-not syncing.
> >
> >
> >
> > -----------------------------------
> >
> > of course some more r there befor this page which has passed in prevous
> screen while those errors occured.
> >
> > I tried for 5 or 6 times.I am getting the same problem.
> > So what may be the reason.Please do suggest some solutions for this.I am
> waiting for solution.because without this I  cant procced further.
> >
> > SO please ........please help me .
> >
> >
> >
> > With Regards,
> > Kantha.
> >
> >
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Question about dummy0

[Cheng Z. <che...@ya...>]

Hi,All,
  I am trying ldp_linux now.I only have 2 pc now,in
order to establish LSP and bind FEC/Label,I must use
dummy0 interface?What is the purpose of dummy?
  After "ifconfig dummy0",can I config a virtual net
via dummy?For example
 ifconfig dummy0 1.2.3.4
 route add -net 10.1.1.0/24 gw 1.2.3.4
In fact,the net 10.1.1.0/24 does not exist.Can such
config establish a LSP?

 Best Regard 

Cheng

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

[mpls-linux-general] Help & Guide ME

[Muzammil A. K. <mu...@ss...>]

Respected Sir,

My name is Muzammil Ahmad Khan.

I am doing research on Implementation on MPLS in VPN's".

I want to have guidence from you for this purpose.

I want some simulations to study regarding MPLS.

If u have in any platform plz mail me


I will be very thankful to you.

Regards,
Muzammil
________


----- Original Message -----
From: "Lakshmikantha A.S" <a_k...@re...>
To: <jl...@mi...>
Cc: <mpl...@li...>; <mpl...@mp...>
Sent: Friday, February 01, 2002 6:17 PM
Subject: Hello Sir


>
> Hello,
>   I am a M.Sc(Computer Science ) student.Presently I am doing a project of
"Development of MPLS Based Router".
> I am working on Cyrix CPU with 128MB RAM on RedHat Linux7.1 on
Kernel-2.4.2-2.I am using mpls-linux-0.990 for mplsadm utility.Now I enabled
both the systems with mplsadm by adding the patch and compiling the kernel
and make mplsadm.
>
>     Before using the mplsadm , both the systems r pinging each other and i
was able to make FTP and telnet also.after I use mplsadm on both the system
, they r pinging each other.but when i give FTP or telnet to remote system ,
the system in which i gave the ftp or telnet will display the 1 to 2 pages
of error like below and will hang.
>
>   CPU:0
> EFLAGS:00010292
> eax:0000001c ebx:c085bfb0 ecx:c351c000 edx:c0322ce4
> esi:c085bfc7 edi:   some number       ebp:        esp:
>
> ds:0018  es :0018 ss:0018
>
> Process kapm-idled (pid:3,stackpage=c1157000)
> stack:c02f20cb
>
> Call trace:[<c02f20cb>]
>
>
>
>
> junk numbers
>
>
>
>
> code : 0f 0b 83 c4 0c c3 a1 4c .........
>
>
>
> Kernel panic:Aiee,killing interrupt handler!
> In interrupt handler-not syncing.
>
>
>
> -----------------------------------
>
> of course some more r there befor this page which has passed in prevous
screen while those errors occured.
>
> I tried for 5 or 6 times.I am getting the same problem.
> So what may be the reason.Please do suggest some solutions for this.I am
waiting for solution.because without this I  cant procced further.
>
> SO please ........please help me .
>
>
>
> With Regards,
> Kantha.
>
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

Re: [mpls-linux-general] BETA: mpls-linux 1.127

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

On Fri, Feb 01, 2002 at 06:08:05PM +0100, Olivier Dugeon wrote:
<snip>
> My trouble is that in the case of PRE_ROUTING nf_hook (ie. before the 
> packet is route) the dst field is not set for the packet. So, if you 
> would use the PRE_ROUTING netfilter hook, i think this scenario will 
> happen :
> 
>   - first packet arrive, dst field is null because no such flow raise 
> this Ingress node.
>   - PRE_ROUTING netfilter doesn't setup the mpls stuff because the dst 
> filed is null
>   - the packet continue its journey and get a dst field after calling 
> ip_route_input function. The skb->dst->output remain unchange to 
> ip_route_output, so this packet is process as usual and not labeled.
>   - second packet arrive, dst field is null, and the packet retrieve its 
> dst field from the route hash table.
> 
> In the case of PRE_ROUTING netfilter setup, (iptables -A INPUT) the 
> packets is never labeled.
> 
> If it's not a bug, it's preferable to avoid setting mpls-key with 
> iptable for the PRE_ROUTING nf_hook.

I had not planned on the MPLS target to be used with the PRE_ROUTING hook.

> Second trouble, and i think it's more serious. You can't make difference
> 
> for two flows with same IP src and dst address but with different port 
> src and/or dst number. PRE_ROUTING dosen't work, so 2 packets comming 
> from the same machine to the same machine get the same dst field :-(
> The ip_route_input function use IP src, dst address, input/output 
> interface number, tos fied and optionnaly fwmark. So, you can't make any 
> difference based on the source or destination port number or protocol.

So are you saying that if the MPLS target worked with PRE_ROUTING
this problem would be solved?

> Solution: I'll follow the PRE_ROUTING trak. I think it's possible to 
> setup the dst field in netfilter mpls hook. So,

Each MOI can potentially have a dst (as part of the SET info).  So
the the packets hitting PRE_ROUTING could use that, or a dst could be built,
that has the necessary info to redirect the packet to the MPLS layer.
Another option is to ship the packet into the MPLS layer form inside the
NF_HOOK, and return that is was dropped.

> 1/ we can make difference between packet based on all field header
> 2/ we skipp low routing process
> 
> What do you think about this ? I am wrong ?

I think it is good that you brought this up (support for port/protocol based
redirection).  Although I'm not sure how often it will be used.  MPLS isn't
meant for microflow TE.

Until we figure out a better way to do this, you could use a combination
of iptables (do nfmark or dsmark based on protocol/port, making sure the
aggregate route points out a mpls tunnel interface) and a nffwd or dsfwd
instruction on the MOI which is attached to the mpls tunnel interface.

Jim

> 
> 
> Regards,
> 
> 
> Olivier
> 
> PS. Your L2CC stuff seems very great.
> -- 
>   FTR&D/DAC/CPN
>   Technopole Anticipa     | mailto:Oli...@fr...
>   2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
>   F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52

-- 
James R. Leu

Re: [mpls-linux-general] BETA: mpls-linux 1.127

[Olivier D. <Oli...@rd...>]

Hi Jim,

James R. Leu wrote:

> A new beta is availble for download via CVS (tag mpls-linux_1_127).
> 


I start looking at this new release (i'haven't any time before do look 
at previous release ie. 1.126 and 1.108).

I hope i've sufficient time next week to make some test. Meanwhile, can 
you explain me a little your iptable approach. If i'm right, iptables, 
in fact netfilter, look at all packet and mark it with a key.
In your code, you take the opportunities to setup the skb->dst->output 
to mpls_output. I see that the mplsinfo key has migrate from skbuff to 
dst structure. To be sure, (and it's normal) you test that the dst field 
is not null to do this and not previously setup.

My trouble is that in the case of PRE_ROUTING nf_hook (ie. before the 
packet is route) the dst field is not set for the packet. So, if you 
would use the PRE_ROUTING netfilter hook, i think this scenario will 
happen :

  - first packet arrive, dst field is null because no such flow raise 
this Ingress node.
  - PRE_ROUTING netfilter doesn't setup the mpls stuff because the dst 
filed is null
  - the packet continue its journey and get a dst field after calling 
ip_route_input function. The skb->dst->output remain unchange to 
ip_route_output, so this packet is process as usual and not labeled.
  - second packet arrive, dst field is null, and the packet retrieve its 
dst field from the route hash table.

In the case of PRE_ROUTING netfilter setup, (iptables -A INPUT) the 
packets is never labeled.

If it's not a bug, it's preferable to avoid setting mpls-key with 
iptable for the PRE_ROUTING nf_hook.

Second trouble, and i think it's more serious. You can't make difference

for two flows with same IP src and dst address but with different port 
src and/or dst number. PRE_ROUTING dosen't work, so 2 packets comming 
from the same machine to the same machine get the same dst field :-(
The ip_route_input function use IP src, dst address, input/output 
interface number, tos fied and optionnaly fwmark. So, you can't make any 
difference based on the source or destination port number or protocol.

Solution: I'll follow the PRE_ROUTING trak. I think it's possible to 
setup the dst field in netfilter mpls hook. So,

1/ we can make difference between packet based on all field header
2/ we skipp low routing process

What do you think about this ? I am wrong ?


Regards,


Olivier

PS. Your L2CC stuff seems very great.
-- 
  FTR&D/DAC/CPN
  Technopole Anticipa     | mailto:Oli...@fr...
  2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
  F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52

Re: [mpls-linux-general] Hello Sir

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

>     Before using the mplsadm , both the systems r pinging each other and i was able to make FTP and telnet also.after I use mplsadm on both the system , they r pinging each other.but when i give FTP or telnet to remote system , the system in which i gave the ftp or telnet will display the 1 to 2 pages of error like below and will hang.
> 
>   CPU:0
> EFLAGS:00010292
> eax:0000001c ebx:c085bfb0 ecx:c351c000 edx:c0322ce4
> esi:c085bfc7 edi:   some number       ebp:        esp:  
> 
> ds:0018  es :0018 ss:0018
> 
> Process kapm-idled (pid:3,stackpage=c1157000)
> stack:c02f20cb
> 
> Call trace:[<c02f20cb>]

THose junk number may help to fingure out where it is crashing.  Do you know
how to translate a "call trace" into the corresponding function names?

> of course some more r there befor this page which has passed in prevous screen while those errors occured.

Capture as much of it as possible.  Then translate the hex into function names.
If you don;t know hwo to do this, just sent me the System.map for the kernel
you are running.

> I tried for 5 or 6 times.I am getting the same problem.
> So what may be the reason.Please do suggest some solutions for this.I am waiting for solution.because without this I  cant procced further.

The crash with TCP is s known problem.  You may be able to help me fix it
with your debugging though.

> SO please ........please help me .

No.. Please help me ;-)

Jim
-- 
James R. Leu

Re: [mpls-linux-general] problems using netfilter

[Olivier D. <Oli...@rd...>]

Hi,

Ulrich D=FCrholz wrote:

>=20
> Hi all,
>=20
> we have encountered some problems using
> the mpls-iptables patch. We wanted to use
> netfilter at the ingress node to bind labels
> to specific ip traffic.
> Here's what we did:
> - first patched linux kernel 2.4.14 with mpls-linux-0.993
> - second applied mpls-iptables-0.3 patch (.full patch)
> - made menuconfig ("netfilter MPLS match support",
> "Packet mangling/MPLS target support" + the "normal"
> MPLS stuff)
> - patched and compiled iptables 1.2.2
>=20
> Excerpt from our configuration script:
>=20
> ...
> mplsadm -v -A -O gen:33:eth1:ipv4:192.168.2.3
>=20
> KEY3=3D`grep 'gen 33' /proc/net/mpls_out | cut -d' ' -f1`
>=20
> iptables -v -I PREROUTING -t mangle -d 192.168.6.1 \
> -s 192.168.5.2 -j MPLS --set-mpls 0x$KEY3
>=20


All seems correct. Can you send me the topology of the network ? Is=20
192.168.2.3 the Egress node ? Where do you perform this command ? on =
the=20
Ingress node ?

I post some month ago (look at the mailing list) a version 0.4 of our=20
patch which resolved some pb., add TC support and let the user use=20
directly the label for iptables instead of the key.


>=20
> This all works so far (giving no error messages
> from mplsadm or iptables), but the traffic seems
> to be forwarded normally using the ip routing table,
> although the packet counter of iptables shows that
> the rule matched.
>=20


Can activate the trace i.e. perform mplsadm -d then ping 192.168.6.2=20
from 192.168.5.2 and look at the console kernel log. Normally you'll =
can=20
see some mpls stuff and especially the rt_next_sethop message telling=20
that you match the iptable rules.


Hope you this help,


Olivier

PS. Like Jim suggest take a look at the recent mpls cvs version.=20
Unfortunately i haven't any time to try it, but it seems greet.
--=20
  FTR&D/DAC/CPN
  Technopole Anticipa     | mailto:Oli...@fr...
  2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
  F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52

[mpls-linux-general] Hello Sir

[Lakshmikantha A.S <a_k...@re...>]

Hello,=0A  I am a M.Sc(Computer Science ) student.Presently I am doing a pr=
oject of "Development of MPLS Based Router".=0AI am working on Cyrix CPU wi=
th 128MB RAM on RedHat Linux7.1 on Kernel-2.4.2-2.I am using mpls-linux-0.9=
90 for mplsadm utility.Now I enabled both the systems with mplsadm by addin=
g the patch and compiling the kernel and make mplsadm.=0A=0A    Before usin=
g the mplsadm , both the systems r pinging each other and i was able to mak=
e FTP and telnet also.after I use mplsadm on both the system , they r pingi=
ng each other.but when i give FTP or telnet to remote system , the system i=
n which i gave the ftp or telnet will display the 1 to 2 pages of error lik=
e below and will hang.=0A=0A  CPU:0=0AEFLAGS:00010292=0Aeax:0000001c ebx:c0=
85bfb0 ecx:c351c000 edx:c0322ce4=0Aesi:c085bfc7 edi:   some number       eb=
p:        esp:  =0A=0Ads:0018  es :0018 ss:0018=0A=0AProcess kapm-idled (pi=
d:3,stackpage=3Dc1157000)=0Astack:c02f20cb=0A=0ACall trace:[<c02f20cb>]=0A=
=0A=0A=0A=0Ajunk numbers=0A=0A=0A=0A=0Acode : 0f 0b 83 c4 0c c3 a1 4c .....=
....=0A=0A=0A=0AKernel panic:Aiee,killing interrupt handler!=0AIn interrupt=
 handler-not syncing.=0A=0A=0A=0A-----------------------------------=0A=0Ao=
f course some more r there befor this page which has passed in prevous scre=
en while those errors occured.=0A=0AI tried for 5 or 6 times.I am getting t=
he same problem.=0ASo what may be the reason.Please do suggest some solutio=
ns for this.I am waiting for solution.because without this I  cant procced =
further.=0A=0ASO please ........please help me .=0A=0A=0A=0AWith Regards,=
=0AKantha.=0A  =0A

Re: [mpls-linux-general] problems using netfilter

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

Are you trying to use the patches from Olivier Dugeon?

I'm only partially familiar with exactly how to get them to work. You
might want to try the BETA version of mpls-linux that integrates much of
Olivier's work.

Grab the latest mpls-linux (1.127) via CVS at:

http://sourceforge.net/cvs/?group_id=3D15443

It contains a patch for a the linux kernel, and for iptables.

I'll be posting directions how to use iptables and mplsadm2 to create
the 'standard' 2 pc LSP (from the README.example in mpls-linux)

Jim

On Thu, Jan 31, 2002 at 12:22:41PM +0100, Ulrich D=FCrholz wrote:
>=20
> Hi all,
>=20
> we have encountered some problems using
> the mpls-iptables patch. We wanted to use
> netfilter at the ingress node to bind labels
> to specific ip traffic.
> Here's what we did:
> - first patched linux kernel 2.4.14 with mpls-linux-0.993
> - second applied mpls-iptables-0.3 patch (.full patch)
> - made menuconfig ("netfilter MPLS match support",
> "Packet mangling/MPLS target support" + the "normal"
> MPLS stuff)
> - patched and compiled iptables 1.2.2
>=20
> Excerpt from our configuration script:
>=20
> ...
> mplsadm -v -A -O gen:33:eth1:ipv4:192.168.2.3
>=20
> KEY3=3D`grep 'gen 33' /proc/net/mpls_out | cut -d' ' -f1`
>=20
> iptables -v -I PREROUTING -t mangle -d 192.168.6.1 \
> -s 192.168.5.2 -j MPLS --set-mpls 0x$KEY3
>=20
>=20
> This all works so far (giving no error messages
> from mplsadm or iptables), but the traffic seems
> to be forwarded normally using the ip routing table,
> although the packet counter of iptables shows that
> the rule matched.
>=20
> Has anybody experienced similar problems?
> Which combination of the linux kernel/patches is known to be=20
> working best?
>=20
>=20
> Thanks,
>=20
> Uli & Daniel
>=20
>=20
>=20
>=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

Re: [mpls-linux-general] Binding to FEC.

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

Part 2 :-)

On Thu, Jan 31, 2002 at 12:13:52PM +0200, Asviyan, Anatoly wrote:
<snip>

> 2) 
> can somebody that has working mpls+iptables give exact instruction for
> mplsadm2 and iptables 
> how to connect 2 PCs (as in some famouse README :-) 
> Thanks

                          Manual LSP beteen 2 hosts
                         ---------------------------

Setup
-----
 ---------             ---------
 |   A   |             |   B   |
 ---------             ---------
     |eth0                 |eth0
     |17.130               |18.114
-----------------------------------
         128.104.16.0/22

Config
------
On A:
  mplsadm -A -O gen:16:eth0:ipv4:128.104.18.114
  iptables -A OUTPUT -d 128.104.18.114/32 -j MPLS --set-key KEY1
  mplsadm -A -I gen:17:0

  Where KEY1 is in the output from the previous 'mplsadm' command

On B:
  mplsadm -A -O gen:17:eth0:ipv4:128.104.17.130
  iptables -A OUTPUT -d 128.104.17.130/32 -j MPLS --set-key KEY2
  mplsadm -A -I gen:16:0

  Where KEY2 is in the output from the previous 'mplsadm' command

Now you need to set a label space on eth0 on both A and B.  Watch out!
if you do this remotely you could saw your leg off!

On both:
  mplsadm -L eth0:0

Now all traffic with destination address of A or B use the LSP.

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

-- 
James R. Leu

RE: [mpls-linux-general] Binding to FEC.

[Asviyan, A. <ana...@te...>]

thank you Jim. it helped. 
additionaly it was required to compile that stuff built in kernel. if these
options
were checked as modules I always have unresolved symbols at modprob time

Anatoly 

> -----Original Message-----
> From: James R. Leu [mailto:jl...@mi...]
> Sent: Thursday, January 31, 2002 8:02 PM
> To: Asviyan, Anatoly
> Cc: Mpls-Linux Mlist (E-mail)
> Subject: Re: [mpls-linux-general] Binding to FEC.
> 
> 
> On Thu, Jan 31, 2002 at 12:13:52PM +0200, Asviyan, Anatoly wrote:
> > 	Hi
> > 1)
> > I can't make latest MPLS work:
> > when I run this command
> > > iptables -A OUTPUT -d 192.168.1.0/24 -j MPLS --set-key 0x2
> > iptables complains about inkown chain/target/match or smth like that
> > I checked that it indeed loads extension/libipt_MPLS and 
> that 0x2 key does
> > exist in mpls_out
> 
> I could be that the kernel is rejecting the target (MPLS).  
> Double check
> your kenel config.  make sure you have:
> 
> Code maturity level options  --->
>   [*] Prompt for development and/or incomplete code/drivers
> Networking options  --->
>   [*] Network packet filtering (replaces ipchains)
>   [*] Multi Protocol Label Switching - MPLS
>   IP: Netfilter Configuration  --->
>     <*> IP tables support (required for filtering/masq/NAT)
>     <*>   Packet mangling
>     <*>     MPLS target support
> 
> NOTE!!! You need to turn on "Multi Protocol Label Switching" before
> you'll see "MPLS target support".
> 
> Jim
> 
> > 
> > my configurations is: patched iptables 1.2.4, patched 
> kernel 2.4.17 and
> > mpls-linux-1.126
> > 
> > Any ideas? Thanks
> > 
> > 2) 
> > can somebody that has working mpls+iptables give exact 
> instruction for
> > mplsadm2 and iptables 
> > how to connect 2 PCs (as in some famouse README :-) 
> > Thanks
> > 
> > -- 
> > Regards, Anatoly
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
>