Thread: RE: [mpls-linux-general] (no subject)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Sanjeev C. <Sa...@co...> - 2001-10-01 18:16:42
|
Hi Jens, Also check your kernel version. It should be at least 2.4.5 Sanjeev -----Original Message----- From: Jens Kuehlberg [mailto:jen...@gm...] Sent: Monday, October 01, 2001 5:58 AM To: mpl...@li... Subject: [mpls-linux-general] (no subject) Hallo, I have Red Hat Linux 7.1 and the linux-mpls (v0.993) Patch. Did Linux-mpls Patch support dynamic label distribution between PC? Or I must install fixed label for MPLS? Bye Jens -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net _______________________________________________ mpls-linux-general mailing list mpl...@li... https://lists.sourceforge.net/lists/listinfo/mpls-linux-general |
|
From: Sumeet A. <sum...@ho...> - 2002-07-01 01:23:41
|
James, Javier and all members of mpls group, Regarding my previous message to this group about 'Network card not getting detected in the new linux kernel'. Well...it was a wild goose chase (for me atleast :) ) but I was finally able to nail the problem mylsef. Solution to the question posted by myself, is to enable the "network device support --> (whatever your ethernaet card is)" in "make menuconfig". Having tackled that problem, there is this new one that has come up. I have mplsadm(ver 1.0) installed on linux-rh-2.4.18. I am making some test with 2 pcs acting as lsr, and with mpls support enabled, and all the tools compiled and working (mplsadm). I set up 1 label in each computer, and add the IN entry on both with each label , i mean THE 2 machines were configured by: AT 192.168.1.35 --------------- route add -host 192.168.1.23 gw 192.168.1.23 ifconfig eth0 192.168.1.35 netmask 255.255.255.0 broadcast 192.168.1.255 up mplsadm -d mplsadm -v -A -B -O gen:2614:eth0:ipv4:192.168.1.23 -f 192.168.1.23/32 mplsadm -v -A -I gen:1234:0 mplsadm -v -L eth0:0 AT 192.168.1.23 --------------- route add -host 192.168.1.35 gw 192.168.1.35 ifconfig eth0 192.168.1.23 netmask 255.255.255.0 broadcast 192.168.1.255 up mplsadm -d mplsadm -v -A -B -O gen:1234:eth0:ipv4:192.168.1.35 -f 192.168.1.35/32 mplsadm -v -A -I gen:2614:0 mplsadm -v -L eth0:0 BUT..the results that I get from 'dmesg' was (tail of it): MPLS version 0.996 11/21/2001 jl...@mi... MPLS Tunnel interface ds: no socket drivers loaded! VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 244k freed Adding Swap: 266072k swap-space (priority -1) mpls_set_labelspace: enter mpls_set_labelspace: labelspace(0) mpls_set_labelspace: exit -------------------------------------- Now: 2 Questions. Q1: Is 'ds: no socket drivers loaded!' doing (any harm)?? Q2. Why are my /proc/net/mpls_* files show nothing but : lo 0 eth0 0 HELP ME...PLEASE Thank you -Sumeet _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx |
|
From: a a <dre...@ho...> - 2003-06-19 10:37:18
|
Hi!
I have checked the output from the commands you recommended me, and found
some strange stuff...
#show ldp database
192.168.0.0/24 local binding: label: gen 10000
192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.101:0
I have the following hardware setup:
snowcrash-mpls pennywise-mpls
192.168.0.101 192.168.0.100
| |
| eth0 | eth0
+-----------------------------------------------+
192.168.0.0/24
How do I get the mplsd to assign an outgoing label to the other machine?
I have included my conf-files and all output from the show ... stuff.
Thanks in advance,
Andreas
>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: a a <dre...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] (no subject)
>Date: Tue, 17 Jun 2003 10:54:11 -0500
>
>On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote:
> > Hi again!
> >
> > How do I use the labels given by the zebra-ldp? I have investigated some
> > pkts with tethereal and found that the pkts are not mpls pkts...
> > Do I have to use mplsadm in order to use the lsp:s?
>
>Check the output from the 'ldp' related show commands. From the mplsd
>command line:
>
> show ldp discovery
> show ldp neighbor
> show ldp database
>
>Also look at the MPLS show commands:
>
> show mpls forwarding
> show mpls ftn
>
>Also, check the:
>
> show ip route
>
>output from the zebra command line.
>
>If everything is running correctly mplsd will create the MPLS forwarding
>entites in the kernel for you and bind the LSPs to route entries.
>
> >
> > Sincerly,
> > Drew
> >
> > _________________________________________________________________
> > Hitta rätt på nätet med MSN Sök http://search.msn.se/
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>--
>James R. Leu
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
_________________________________________________________________
Hitta rätt på nätet med MSN Sök http://search.msn.se/
|
|
From: James R. L. <jl...@mi...> - 2003-06-19 14:23:56
|
I would create a 'dummy0' interface on each device (as I describe in my zebra sample on http://mpls-linux.sf.net/). Also you will never get traffic between just two boxes to be labeled (there is no reason, they would both be LERs). You need a 3rd device to make it interesting. Take a look at user-mode-linux (http://user-mode-linux.sf.net/) for a 'easy' way to simulate a multi node network on one device. On Thu, Jun 19, 2003 at 12:37:07PM +0200, a a wrote: > Hi! >=20 > I have checked the output from the commands you recommended me, and fou= nd=20 > some strange stuff... >=20 > #show ldp database > 192.168.0.0/24 local binding: label: gen 10000 > 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.101:0 >=20 > I have the following hardware setup: >=20 > snowcrash-mpls pennywise-mpls > 192.168.0.101 192.168.0.100 > | | > | eth0 | eth0 > +-----------------------------------------------+ > 192.168.0.0/24 >=20 > How do I get the mplsd to assign an outgoing label to the other machine= ? > I have included my conf-files and all output from the show ... stuff. >=20 > Thanks in advance, > Andreas >=20 > >From: "James R. Leu" <jl...@mi...> > >Reply-To: jl...@mi... > >To: a a <dre...@ho...> > >CC: mpl...@li... > >Subject: Re: [mpls-linux-general] (no subject) > >Date: Tue, 17 Jun 2003 10:54:11 -0500 > > > >On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote: > > > Hi again! > > > > > > How do I use the labels given by the zebra-ldp? I have investigated= some > > > pkts with tethereal and found that the pkts are not mpls pkts... > > > Do I have to use mplsadm in order to use the lsp:s? > > > >Check the output from the 'ldp' related show commands. From the mplsd > >command line: > > > > show ldp discovery > > show ldp neighbor > > show ldp database > > > >Also look at the MPLS show commands: > > > > show mpls forwarding > > show mpls ftn > > > >Also, check the: > > > > show ip route > > > >output from the zebra command line. > > > >If everything is running correctly mplsd will create the MPLS forwardi= ng > >entites in the kernel for you and bind the LSPs to route entries. > > > > > > > > Sincerly, > > > Drew > > > > > > _________________________________________________________________ > > > Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/ > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: INetU > > > Attention Web Developers & Consultants: Become An INetU Hosting Par= tner. > > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commis= sion! > > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.= php > > > _______________________________________________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > >-- > >James R. Leu > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: INetU > >Attention Web Developers & Consultants: Become An INetU Hosting Partne= r. > >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commissio= n! > >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > >_______________________________________________ > >mpls-linux-general mailing list > >mpl...@li... > >https://lists.sourceforge.net/lists/listinfo/mpls-linux-general >=20 > _________________________________________________________________ > Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/ > ! > ! Zebra configuration saved from vty > ! 2002/03/23 17:07:30 > ! > hostname snowcrash-mplsd > password zebra > enable password zebra > ! > mpls ldp > ! > interface lo > ! > interface eth0 > mpls ldp > ! > interface dummy0 > ! > line vty > exec-timeout 0 0 > ! >=20 > ! -*- ospf -*- > ! > ! OSPFd sample configuration file > ! > ! > hostname snowcrash-ospfd > password zebra > enable password zebra > interface lo > interface eth0 > interface dummy0 > interface teql0 > router ospf > passive-interface lo > network 10.0.0.0/24 area 0 > network 192.168.0.0/24 area 0 > ! network 192.168.0.2/32 area 0 > line vty > exec-timeout 0 0 >=20 > log stdout >=20 > ! -*- zebra -*- > ! > ! zebra sample configuration file > ! > ! $Id: zebra.conf.sample,v 1.14 1999/02/19 17:26:38 developer Exp $ > ! > hostname snowcrash-zebra > password zebra > enable password zebra > ! > ! Interface's description. > ! > interface lo > description Loopback > ! > interface dummy0 > ip address 192.168.0.250/32 > ! > interface eth0 > ! > !interface sit0 > ! multicast >=20 > interface teql0 > ! > ! Static default route sample. > ! > !ip route 0.0.0.0/0 203.181.89.241 > ! >=20 > !log file zebra.log >=20 > snowcrash-mplsd> show ldp database > 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.100:0 > 192.168.0.0/24 local binding: label: gen 10000 >=20 > snowcrash-mplsd> show ldp discovery >=20 > Local LSR Identifier: 192.168.0.101 >=20 > Interface Discovery Sources: > eth0: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > snowcrash-mplsd> show ldp neighbor > Peer LDP Ident: 192.168.0.100:0; Local LDP Ident: 192.168.0.101:0 > TCP connection: 0.0.0.0.646 - 192.168.0.100.646 > State: OPERATIONAL; Msgs sent/recv: 25/73; UNSOLICITED > Up time: 00:05:22 > LDP discovery sources: > eth0 > Addresses bound to peer: > 192.168.0.100 >=20 >=20 > snowcrash-mplsd> show ldp session > 2 192.168.0.100 45 OPERATIONAL > 192.168.0.100 > snowcrash-mplsd> show mpls forw > snowcrash-mplsd> show mpls forwarding > Insegments: > Lbl Spc Label Owner > 0 10000 LDP > Total 1 >=20 > Outsegments: >=20 > Total 0 >=20 > Cross Connects: >=20 > Total 0 >=20 > snowcrash-mplsd> show mpls ftn > FTNs: >=20 > Total 0 >=20 > snowcrash-zebra# show ip route > C>* 127.0.0.0/8 is directly connected, lo > O 192.168.0.0/24 [110/10] is directly connected, eth0, 00:18:41 > C>* 192.168.0.0/24 is directly connect, eth0 >=20 --=20 James R. Leu |
|
From: Levisse M. <le...@en...> - 2003-06-30 16:44:27
|
Hi,
It seems we are stuck at the same point as "a a".
Here is our topology :
xxx.xxx.214.5 xxx.xxx.214.6
xxx.xxx.214.9 xxx.xxx.214.10
|
| |
|
| eth1 eth1 |
| eth2 eth1 |
+-----------------------------------------------+
+-----------------------------------------------+
xxx.xxx.214.4/30
xxx.xxx.214.8/30
Here are our initial config files :
|
|
From: Ranald <jf...@ne...> - 2007-06-14 09:11:19
|
When you start to realize that you need to change your size, tr |
|
From: juergen l. <ev...@st...> - 2007-10-12 21:51:25
|
Hello! We are so sure you are going to love our games that we are giving you up to 500 $ free just for trying our program. Look at www.yourprogaming.com Thanks! |
|
From: Adrian P. <adr...@gm...> - 2008-01-28 08:55:03
|
Hello Rachid, Thanks for the attachement and sorry I didn't manage to reply this weekend (I didn't get close to the computer...). Looking into the examples, here's what you need to do: - from e1/scripts/network2/qos/e-lsp.sh: echo 'A3->A2' #do the following mapping: # DSCP EXP TCINDEX # 0x1E 3 1 # 0x00 0 3 #and push label 2000 for both of them var1=`mpls nhlfe add key 0 instructions ds2exp 0xf 0x1e 0x3 0x0 0x0 exp2tc 0x3 0x1 0x0 0x3 push gen 2000 nexthop eth3 ipv4 10.0.5.3 | grep key |cut -c 17-26` You need to create a label path with a key mapping your desired DSCP to a desired EXP. In this command, I mapped DSCP 0x1E to EXP 0x3 AND DSCP 0x00(best effort) to EXP 0x0. Furthermore, mapping DSCP to EXP is not enough - even if your packets will leave with the desired EXP values, Linux tc will not differentiate the traffic. You need to add exp2tc mapping so that packets with EXP 0x3 follow a specific tc rule and benefit from a specific bandwidth. In my case packets with EXP 0x3 have tcindex 1 (tcindex is just a number that has to be the same in the mpls command and in the tc commands) and packets with EXP 3 have tcindex 3: mpls nhlfe add key 0 instructions ds2exp 0xf 0x1e 0x3 0x0 0x0 exp2tc 0x3 0x1 0x0 0x3 push gen 2000 nexthop eth3 ipv4 10.0.5.3 The rest of the command is standard - add a new label (2000) and specify the nexthop interface (eth3) and nexthop ip (10.0.5.3). If you don't need to allocate bandwidth, you don't need the exp2tc 0x3 0x1 0x0 0x3 part. Oh, I nearly forgot - In the command ds2exp 0xf 0x1e 0x3 0x0 0x0, the 0xf is just a bit mask that is applied on the DSCP value (a logical OR), so that multiple DSCP values will be linked to a single EXP. If you want one-to-one mapping, you can set this mask to 0xf and forget about it. The new key generated by this command has to be linked with the forwarding plane by means of iptables: #create a FEC: packets with DSCP=0x1E and DSCP=0x00 go to nhlfe $var1 iptables -A FORWARD -m dscp --dscp 0x1e -j mpls --nhlfe $var1 iptables -A FORWARD -m dscp --dscp 0x0 -j mpls --nhlfe $var1 If you need to apply special bandwidth guarantees (per DSCP), you can do so with tc: #on output interface eth3, for MPLS traffic, map TCINDEX 1 to class 1:11 and TCINDEX 3 to class 1:13 tc qdisc add dev eth3 root handle 1: htb tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 tcindex mask 0xf shift 0 pass_on tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 handle 1 tcindex classid 1:11 tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 handle 3 tcindex classid 1:13 #limit the output interface to 7200kbit and guarantee 2400kbit to EXP=3 traffic and 400kbit to EXP=0 traffic tc class add dev eth3 parent 1:0 classid 1:10 htb rate 7200kbit tc class add dev eth3 parent 1:10 classid 1:11 htb rate 2400kbit ceil 7200kbit tc class add dev eth3 parent 1:10 classid 1:13 htb rate 400kbit ceil 7200kbit tc qdisc add dev eth3 parent 1:11 handle 110: pfifo limit 10 tc qdisc add dev eth3 parent 1:13 handle 130: pfifo limit 10 You can find a very good tc and DSCP tutorial here: http://opalsoft.net/qos/DS.htm Now, you need to add these commands on the edge nodes of your MPLS network - both at ingress and at egress (because MPLS paths are unidirectional), and you should map them to the interface toward your MPLS cloud (in this example, eth3 goes to the P router). On the P routers you should only use exp2tc to make sure you have bandwidth guarantees for your EXP values (and also add the necessary tc rules). See e3/scripts/network2/qos/e-lsp.sh for details. Hope this helps, and good luck! On Jan 25, 2008 8:42 PM, rachid rachid <rac...@ho...> wrote: > > Hello Adrian, > I have already save your examples, you can find it attached in this mail. > > Thanks && BR, > R.Benbrahim > > ------------------------------ > Date: Fri, 25 Jan 2008 14:43:24 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Hello Rachid, > > Sorry to dissapoint you, but it seems that the server where I hosted the > tutorials hasn't recovered yet (although the administrator had promissed me > it would be up by friday), so I don't have access to my examples. I'll look > into it this weekend and send you a reply. Sorry for the delay. > > Adrian > > On Jan 25, 2008 11:31 AM, rachid rachid <rac...@ho...> wrote: > > Hello Adrian, > Sorry to disturb you, did you remember me, i'am waiting to your response > and i can't progress, thanks to give feedback as soon as you can. > > Best regards, > R.Benbahim > > > ------------------------------ > Date: Wed, 23 Jan 2008 14:07:41 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Hello Rachid, > > Sorry I didn't reply earlier, but it's a busy period for me. Unfortunately > I don't have access to my examples (the server they were hosted on has > crashed and is under recovery), but Thursday or Friday I should have access > to the examples, and show you what you must do. > > Adrian > > On Jan 20, 2008 2:42 PM, rachid rachid <rac...@ho...> wrote: > > Hello Adrian, > I want to make an experimentation MPLS-WIFI, the mpls clouds is composed > of three machines(R1=LER, R2=LSR, R3=LER) with Fedora 5, i have installed > the MPLS Kernel as described in your experimentation 'mpls-linux 1.950', > there is two other machine (windwosXP) wich dialog althought this mpls > clouds. > > PC1 Windows XP server---WIFI------------R1-R2-R3-------------WIFI---PC2 > Windows XP client > > I want to make an ftp tranfert from PC1 to PC2 using E-LSP, could you show > me the configuration of mapping DSCP-EXP to do. > > THANKS && BEST REGARDS, > Rachid. > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > |
|
From: Adrian P. <adr...@gm...> - 2008-02-10 15:08:50
|
Hello Rachid, About a year and a half ago I experimented with LDP, but it was too instable to be of any use (it crashed when setting up a LPD adjacency). Now, I've heard on the mailing list that it is more stable and should work. You should download the quagga binary (or source) from sourceforge and install/compile it. You should configure ospf routing first (and make sure it works) and after that start ldp. Configuring LDP is easy, something like: #conf t (config)# mpls ldp (config-ldp)#lsr-id *one.of.the.ips.from.this.router* (config-ldp)#transport-address *one.of.the.ips.from.this.router *(config-ldp)#address-mode ldp (config-ldp)#exit (config)#interface eth1 (config-if)#mpls ip (config-if)#distribution-mode du (config-if)#end #show ldp Not all the parameters are necessary. The minimum are mpls ldp in global config mode and mpls ip on the interfaces with mpls. Ask for more details on the mailing list, in case of trouble. Adrian On Feb 9, 2008 12:00 AM, rachid rachid <rac...@ho...> wrote: > Hello Adrian, > i'm in france now, i will continue investigation since i come back,so i > have a questio : is it possible to make a dynamic routing LDP > in experimentation, have any idea, document site, i have serched without > succes. > > Thanks && BR, > R.Benbrahim > > > ------------------------------ > Date: Sun, 3 Feb 2008 18:39:08 +0200 > > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Good to see it's finally forwarding MPLS packets. Now, it seems to me that > you're trying to send traffic from PC2 to PC1 and it almost arrives in PC1. > However R1 doesn't output the traffic. Run mpls ilm show and mpls nhlfe show > on R1, and please give me again the current configuration on R1. And output > from > ip route show > mpls ilm show > > As you can see, currently FTP traffic is not marked, but this is because > the marking is done only from reverse traffic (from PC1 to PC2). So, as soon > as we get R1 to route packets to PC1, it should work. > > The changes that you made (with iptables) should have had no effect until > now. Something else must have changed in the mean time (on R3) and this is > why it's almost working. > > On Feb 2, 2008 8:49 PM, rachid rachid <rac...@ho...> wrote: > > > Hello Adrian, > i have tried to do the modification again by replacing , > > iptables -t mangle -F > iptables -t mangle -A PREROUTING -p udp --dport 1235 -j DSCP --set-dscp 26 > iptables -t mangle -A PREROUTING -p udp --dport 1236 -j DSCP --set-dscp 46 > by > iptables -t mangle -A PREROUTING -p tcp --sport 20 -j DSCP --set-dscp 26 > iptables -t mangle -A PREROUTING -p tcp --sport 21 -j DSCP --set-dscp 26 > > just to verify, so i have some output unlike the last time.i have just > tried to make > ping to every machine in my lab before doing tcpdump i don't understand > why this time i have some > output.YOu can find in the atachment all output that i got. > > BR, > Rachid > > ------------------------------ > Date: Mon, 28 Jan 2008 12:00:13 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Ok, I see that you want to prioritize FTP, but when you mark your traffic, > you just mark UDP traffic: > > iptables -t mangle -F > iptables -t mangle -A PREROUTING -p udp --dport 1235 -j DSCP --set-dscp 26 > > iptables -t mangle -A PREROUTING -p udp --dport 1236 -j DSCP --set-dscp 46 > > You should change this to : > iptables -t mangle -A PREROUTING -p tcp --sport 20 -j DSCP --set-dscp 26 > iptables -t mangle -A PREROUTING -p tcp --sport 21 -j DSCP --set-dscp 26 > > If it still doesn't work, try to send marked traffic directly from your host (this means that your host > > runs linux - try a live cd), and mark the traffic with iptables in the same way. > > At first look, your example seems to work (if marking is done ok), but only traffic from the server > to the client will be marked and travel through MPLS - the return traffic will be IP. > > My sugestion is to try the marking first - make sure the packets from the ftp server leave with the > desired dscp value, and after that, make sure the nhlfe receives the interesting traffic (with mpls nhlfe show). > > Other than that it should work. Let me know if I can help. > > Cheers, > Adrian > > > > > On Jan 28, 2008 11:17 AM, rachid rachid <rac...@ho...> wrote: > > > Hello Adrain, > Think you for your answer, but ididn't see in your explanation the way to > allow the FTP flow, i have tried to add the FTP port = 21, but without > success. > find the attachment my configuration for R1 and R2 and R3, by the way i > don't have router, see bellow my configuration : > > PC1 Windows XP server------->(Access > point)WIFI------------>R1-R2-R3------------->(Access > point)WIFI---------->PC2 Windows XP client > > Thanks for your help. > > ------------------------------ > Date: Mon, 28 Jan 2008 10:54:55 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > CC: mpl...@li... > > Hello Rachid, > > Thanks for the attachement and sorry I didn't manage to reply this weekend > (I didn't get close to the computer...). > > Looking into the examples, here's what you need to do: > > - from e1/scripts/network2/qos/e-lsp.sh: > > echo > 'A3->A2' > > #do the following > mapping: > > # DSCP EXP > TCINDEX > > # 0x1E 3 > 1 > > # 0x00 0 3 > #and push label 2000 for both of them > var1=`mpls nhlfe add key 0 instructions ds2exp 0xf 0x1e 0x3 0x0 0x0 > exp2tc 0x3 0x1 0x0 0x3 push gen 2000 nexthop eth3 ipv4 10.0.5.3 | grep > key |cut -c 17-26` > > You need to create a label path with a key mapping your desired DSCP to a > desired EXP. In this command, I mapped DSCP 0x1E to EXP 0x3 AND DSCP 0x00(best effort) to EXP 0x0. > Furthermore, mapping DSCP to EXP is not enough - even if your packets will > leave with the desired EXP values, Linux tc will not differentiate the > traffic. You need to add exp2tc mapping so that packets with EXP 0x3 follow > a specific tc rule and benefit from a specific bandwidth. In my case > packets with EXP 0x3 have tcindex 1 (tcindex is just a number that has to be > the same in the mpls command and in the tc commands) and packets with EXP 3 > have tcindex 3: > > mpls nhlfe add key 0 instructions ds2exp 0xf 0x1e 0x3 0x0 0x0 exp2tc 0x3 > 0x1 0x0 0x3 push gen 2000 nexthop eth3 ipv4 10.0.5.3 > > The rest of the command is standard - add a new label (2000) and specify > the nexthop interface (eth3) and nexthop ip (10.0.5.3). > If you don't need to allocate bandwidth, you don't need the exp2tc 0x3 0x1 > 0x0 0x3 part. > > Oh, I nearly forgot - In the command ds2exp 0xf 0x1e 0x3 0x0 0x0, the 0xf > is just a bit mask that is applied on the DSCP value (a logical OR), so that > multiple DSCP values will be linked to a single EXP. If you want one-to-one > mapping, you can set this mask to 0xf and forget about it. > > The new key generated by this command has to be linked with the forwarding > plane by means of iptables: > > #create a FEC: packets with DSCP=0x1E and DSCP=0x00 go to nhlfe > $var1 > iptables -A FORWARD -m dscp --dscp 0x1e -j mpls --nhlfe $var1 > iptables -A FORWARD -m dscp --dscp 0x0 -j mpls --nhlfe $var1 > > If you need to apply special bandwidth guarantees (per DSCP), you can do > so with tc: > > #on output interface eth3, for MPLS traffic, map TCINDEX 1 to class 1:11 > and TCINDEX 3 to class 1:13 > tc qdisc add dev eth3 root handle 1: > htb > tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 tcindex mask 0xf > shift 0 pass_on > tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 handle 1 tcindex > classid 1:11 > tc filter add dev eth3 parent 1:0 protocol 0x8847 prio 1 handle 3 tcindex > classid 1:13 > > > #limit the output interface to 7200kbit and guarantee 2400kbit to EXP=3 > traffic and 400kbit to EXP=0 traffic > tc class add dev eth3 parent 1:0 classid 1:10 htb rate 7200kbit > tc class add dev eth3 parent 1:10 classid 1:11 htb rate 2400kbit ceil > 7200kbit > tc class add dev eth3 parent 1:10 classid 1:13 htb rate 400kbit ceil > 7200kbit > tc qdisc add dev eth3 parent 1:11 handle 110: pfifo limit > 10 > tc qdisc add dev eth3 parent 1:13 handle 130: pfifo limit > 10 > > You can find a very good tc and DSCP tutorial here: > http://opalsoft.net/qos/DS.htm > > Now, you need to add these commands on the edge nodes of your MPLS network > - both at ingress and at egress (because MPLS paths are unidirectional), and > you should map them to the interface toward your MPLS cloud (in this > example, eth3 goes to the P router). > > On the P routers you should only use exp2tc to make sure you have > bandwidth guarantees for your EXP values (and also add the necessary tc > rules). See e3/scripts/network2/qos/e-lsp.sh for details. > > Hope this helps, and good luck! > > On Jan 25, 2008 8:42 PM, rachid rachid <rac...@ho...> wrote: > > > Hello Adrian, > I have already save your examples, you can find it attached in this mail. > > Thanks && BR, > R.Benbrahim > > ------------------------------ > Date: Fri, 25 Jan 2008 14:43:24 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Hello Rachid, > > Sorry to dissapoint you, but it seems that the server where I hosted the > tutorials hasn't recovered yet (although the administrator had promissed me > it would be up by friday), so I don't have access to my examples. I'll look > into it this weekend and send you a reply. Sorry for the delay. > > Adrian > > On Jan 25, 2008 11:31 AM, rachid rachid <rac...@ho...> wrote: > > Hello Adrian, > Sorry to disturb you, did you remember me, i'am waiting to your response > and i can't progress, thanks to give feedback as soon as you can. > > Best regards, > R.Benbahim > > > ------------------------------ > Date: Wed, 23 Jan 2008 14:07:41 +0200 > From: adr...@gm... > To: rac...@ho... > Subject: Re: > > Hello Rachid, > > Sorry I didn't reply earlier, but it's a busy period for me. Unfortunately > I don't have access to my examples (the server they were hosted on has > crashed and is under recovery), but Thursday or Friday I should have access > to the examples, and show you what you must do. > > Adrian > > On Jan 20, 2008 2:42 PM, rachid rachid <rac...@ho...> wrote: > > Hello Adrian, > I want to make an experimentation MPLS-WIFI, the mpls clouds is composed > of three machines(R1=LER, R2=LSR, R3=LER) with Fedora 5, i have installed > the MPLS Kernel as described in your experimentation 'mpls-linux 1.950', > there is two other machine (windwosXP) wich dialog althought this mpls > clouds. > > PC1 Windows XP server---WIFI------------R1-R2-R3-------------WIFI---PC2 > Windows XP client > > I want to make an ftp tranfert from PC1 to PC2 using E-LSP, could you show > me the configuration of mapping DSCP-EXP to do. > > THANKS && BEST REGARDS, > Rachid. > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger<http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X