mpls-linux-general Mailing List for MPLS for Linux (Page 62)
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: Louella G. <xgx...@p0...> - 2005-12-23 01:13:08
|
Explosive Sto ck Alert for Friday 12-23-05 Doll Technology Group Inc. Global Manufacturer and Marketer of "Clean & Green" Products and Technology Solutions(Source: News 12/6/05) OTC: DTGP Price: .16 Huge PR Campaign Underway For Fridays's Trad ing DTGP Can You Make Some Fast Money On This One? RECENT NEWS: Go Read The Full Stories Right Now 1)Doll Technology Group Begins U.S. Trials of AquaBoost(TM) 2)Doll Technology Group Announces Strategic Partnership With Land and Sea Development to Market BlazeTamer(TM) Fire Retardant Product- Initial Purchase Order Valued at Over $1.1 Million RedBrooks Laboratory, a DTGP subsidiary, is a full service independent facility that tests, qualifies and certifies all Doll Technology Group's products and services. The laboratory is one of the few government certified facilities for the testing of fire suppression systems for the aerospace, maritime, and general industries. (Source: News 12/2/05) Watch This One Trade on Thursday Radar it Right Now.. information within this email contains 4rward l00king statements within the m eaning of Sect ion twenty seven A of the Securities Act of nin eteen thirty three and Section twenty oneB of the Secu rities Exch ange Act of nineteen thirty four. Any statements that expr ess or involve discuss ions with respect to predi ctions, exp ectations, belie fs, pl ans, proj ections, objectives, g oals, assumpt ions or future events or perf ormance are not stat ements of his torical fact and may be 4 rward 1o0king statem ents. 4 rward looking stat ements are based on e xpectations, estimates and proj ections at the time the stat ements are made that in volve a nu mber of ri sks and uncer tainties wh ich could cause actual res ults or eve nts to dif fer mate rially from those p resently anticipa ted.Today's fea tured Compa ny is not a repr ting compan y und er the SEC Act of ninteen thirty four and theref ore there is limi ted inform tion availab le on the com pany. As with many micr ocap st=cks, today's company has dis closable material items you need to consider in order to make an informed and intelligent in_vestment decision. These items include: A nominal cash position. it is an operating Company. The company is going to need financing. if that financing does not occur, the company may not be able to continue as a going concern in which case you could lose your entire in-vestment. The publisher of this newsletter does not represent that the informa tion contained in this message states all ma terial facts or does not omit a mat erial fact neces sary to make the state ments therein not misle ading. All in formation provided within this e_ mail perta ining to in- vesting, st=cks, securities must be understood as informat ion provi ded and not in vest ment advice. Remember a tho rough due dilige nce effort, inc luding a review of a comp any's filings when available, should be compl eted prior to in_ vesting. The pu blisher of this newsletter advises all read ers and subs cribers to seek adv ice from a reg istered profe ssional secu rities re presentative before deciding to trade in st=cks featured within this e_ mail. None of the mat erial within this repo rt shall be co nstrued as any kind of in_vestment advice or solicitation. Many of these companies are on the verge of bankruptcy. You can lose all your mony by inv esting in this st=ck. The publisher of this newsletter is not a regis tered in- vestment advis0r. Subscribers should not view information herein as legal, t x, account ing or in vestment advice. in comp liance with the Secur ities Act of nineteen thirty three, Section seventeen(b),The pu blisher of this newslet ter is cont racted to receive twel ve th0us and d0l lars from a third party, not an officer, director or affiliate shareh 0lder for the circul ation of this re port. Be aware of an inher ent conf lict of int erest resu lting from su ch compen sation due to the fact that this is a paid a vertisement and is not with out b ias.The pa rty that pa ys us has a pos ition in the st=ck they will sell at any time wi hout notice. This could have a nega tive im pact on the price of the st0ck, causing you to lose mony.Their intent ion is to sell now. All fa ctual inf ormation in this report was gathered from public sources,including but not limited to Company Press Releases. Use of the info rmation in this email cons titutes your accep tance of these terms. |
|
From: Ajay R. <fo...@re...> - 2005-12-22 14:59:41
|
=A0=0A I am student, I have complile 2.4.20 kernel bu 2.6.9 with MPLS patc= h,=0A=0AI was successful in doing that but I haven't patched iproute2.diff = and other patches except kernel.diff. I tried to patched other patches=0Abu= t other patches asking for path to be patched, I doesn't which file path th= e other patch wants...=0A=0AAny help in this matter will be appreciated...= =0A=0AThanks in Advance.=0A=0AAjay |
|
From: James R. L. <jl...@mi...> - 2005-12-22 14:02:34
|
1.950 is not fully released yet. I decided to let people have access to the RPMs while I'm finalizing the release. I will be releasing a mpls-linux tar ball when I've updated the documentation inside of it. On Thu, Dec 22, 2005 at 12:46:34PM +0100, zzt wrote: > Hi, > why, in the new 1.950, there isn't a tarball with all the patches and lit= tle=20 > bit of documentation like: > mpls-linux-1.946a.tar.bz2 ? >=20 > Thanks. > S.P. >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2005-12-22 14:00:07
|
What did you change from the previous email to get it working? On Thu, Dec 22, 2005 at 08:05:58PM +0800, allen wrote: > Hi All: >=20 > I have succeeded. This configuration can be worked. It has succedded sen= d the "ping request" packet from HostA to Host B(label 1000)=20 > and receive the "ping reply" packets from HostB to HostA. To establish m= ulti LSP between LER1 and LER2 is my following test. >=20 > Thanks for your attention. >=20 > 192.168.101.0/24 192.168.103.0/24 > | | > | | > ------eth0 eth0------eth1 v eth1----eth0 eth0---eth1 v eth1---= --- > | HostA |--------| LER1 |---------| LSR |-----| LER2 |----------| Hos= tB | > ------.10 ^ 20-------20 30-----30 ^ 40-----40 50---= --- > | | > | |=20 > 192.168.100.0/24 192.168.102.0/24 >=20 >=20 > Configuration > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > HostA > ------ > ifconfig eth0 192.168.100.10 up > ip route add 192.168.103.0/24 via 192.168.100.20 >=20 > LER1 > ------ > ifconfig eth0 192.168.100.20 up > ifconfig eth1 192.168.101.20 up > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth1 ipv4 192.168= .101.30 > ip route add 192.168.103.0/24 via 192.168.101.30 spec_nh 0x8847 0x2 >=20 > mpls labelspace add dev eth1 labelspace 0 > mpls ilm add label gen 2000 labelspace 0 >=20 > LSR > ----- > ifconfig eth1 192.168.101.30 up > ifconfig eth0 192.168.102.30 up > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.168= .102.40 > mpls labelspace add dev eth1 labelspace 0 > mpls ilm add label gen 1000 labelspace > mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2 >=20 > mpls nhlfe add key 0 instructions push gen 2000 nexthop eth1 ipv4 192.168= .101.20 > mpls labelspace add dev eth0 labelspace 0 > mpls ilm add label gen 2000 labelspace > mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3 >=20 > LER2 > ----- > ifconfig eth0 192.168.102.40 up > ifconfig eth1 192.168.103.40 up > mpls labelspace add dev eth0 labelspace 0 > mpls ilm add label gen 1000 labelspace 0 >=20 > mpls nhlfe add key 0 instructions push gen 2000 nexthop eth0 ipv4 192.168= .102.30 > ip route add 192.168.100.0/24 via 192.168.102.30 spec_nh 0x8847 0x2 >=20 > HostB > ------ > ifconfig eth1 192.168.103.50 up > ip route add 192.168.100.0/24 via 192.168.103.40 >=20 --=20 James R. Leu jl...@mi... |
|
From: allen <as...@gm...> - 2005-12-22 12:06:54
|
Hi All:
I have succeeded. This configuration can be worked. It has succedded =
send the "ping request" packet from HostA to Host B(label 1000)=20
and receive the "ping reply" packets from HostB to HostA. To establish =
multi LSP between LER1 and LER2 is my following test.
Thanks for your attention.
192.168.101.0/24 192.168.103.0/24
| |
| |
------eth0 eth0------eth1 v eth1----eth0 eth0---eth1 v =
eth1------
| HostA |--------| LER1 |---------| LSR |-----| LER2 |----------| =
HostB |
------.10 ^ 20-------20 30-----30 ^ 40-----40 =
50------
| |
| |=20
192.168.100.0/24 192.168.102.0/24
Configuration
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
HostA
------
ifconfig eth0 192.168.100.10 up
ip route add 192.168.103.0/24 via 192.168.100.20
LER1
------
ifconfig eth0 192.168.100.20 up
ifconfig eth1 192.168.101.20 up
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth1 ipv4 =
192.168.101.30
ip route add 192.168.103.0/24 via 192.168.101.30 spec_nh 0x8847 0x2
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 2000 labelspace 0
LSR
-----
ifconfig eth1 192.168.101.30 up
ifconfig eth0 192.168.102.30 up
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 =
192.168.102.40
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1000 labelspace
mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
mpls nhlfe add key 0 instructions push gen 2000 nexthop eth1 ipv4 =
192.168.101.20
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 2000 labelspace
mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3
LER2
-----
ifconfig eth0 192.168.102.40 up
ifconfig eth1 192.168.103.40 up
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 1000 labelspace 0
mpls nhlfe add key 0 instructions push gen 2000 nexthop eth0 ipv4 =
192.168.102.30
ip route add 192.168.100.0/24 via 192.168.102.30 spec_nh 0x8847 0x2
HostB
------
ifconfig eth1 192.168.103.50 up
ip route add 192.168.100.0/24 via 192.168.103.40
|
|
From: zzt <ste...@gm...> - 2005-12-22 11:45:43
|
Hi, why, in the new 1.950, there isn't a tarball with all the patches and little bit of documentation like: mpls-linux-1.946a.tar.bz2 ? Thanks. S.P. |
|
From: allen <as...@gm...> - 2005-12-22 07:28:44
|
Hello:
I have already modified my configuration. But the question still exists.
When LER1 receives the "ping" packet from HostA. LER1 uses the label =
1000, but doesn't send to LSR. I saw the problem is LER1's and LER1's =
nhlfe table is=20
NHLFE entry key 0x00000003 mtu 1500 propagate_ttl
set eth0 ipv4 192.168.100.10 (0 bytes, 0 pkts, 0 dropped)
NHLFE entry key 0x00000002 mtu 1500 propagate_ttl
(1596 bytes, 19 pkts, 19 dropped)
the packets never leaves LER1. Please see my configuration once again, =
then tell me how should I do.
192.168.101.0/24 192.168.103.0/24
| |
| |
------eth0 eth0------eth1 v eth1----eth0 eth0---eth1 v =
eth1------
| HostA |--------| LER1 |---------| LSR |-----| LER2 |----------| =
HostB |
------.10 ^ 20-------20 30-----30 ^ 40-----40 =
50------
| |
| |=20
192.168.100.0/24 192.168.102.0/24
Configuration
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
HostA
------
ip route add 192.168.103.0/24 via 192.168.100.20
LER1
------
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 =
192.168.100.20
(key: 0x00000002)
ip route add 192.168.103.0/24 via 192.168.101.30 spec_nh 0x8847 0x2
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1002 labelspace 0
mpls nhlfe add key 0 instructions nexthop eth0 ipv4 192.168.100.10
(key: 0x00000003)
mpls xc add ilm_label gen 2002 ilm_labelspace 0 nhlfe_key 0x3
LSR
-----
mpls nhlfe add key 0 instructions push gen 2000 nexthop eth0 ipv4 =
192.168.102.40
(key: 0x00000002)
mpls nhlfe add key 0 instructions push gen 2002 nexthop eth1 ipv4 =
192.168.101.20
(key: 0x00000003)
mpls labelspace add dev eth0 labelspace 0
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1000 labelspace 0
mpls ilm add label gen 1002 labelspace 0=20
mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x3
LER2
-----
mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 =
192.168.103.40
(key: 0x00000002)
ip route add 192.168.100.0/24 via 192.168.103.40 spec_nh 0x8847 0x2
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 2000 labelspace 0
mpls nhlfe add key 0 instructions nexthop eth1 ipv4 192.168.103.50
(key: 0x00000003)
mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3
HostB
------
ip route add 192.168.100.0/24 via 192.168.103.40 |
|
From: James R. L. <jl...@mi...> - 2005-12-22 04:22:59
|
Hello,
I've had others mention something about this as well.
Right now my thinking is HW checksumming is invalid when using MPLS
linux due to a split brain syndrome: IPv4 thinks the hardware will do
the checksumming but by the time the HW gets the packets, the packets are
no longer IPv4 packets and therefore do not get checksummed.
To know if my thinking is correct I need someone to do additional
testing, but no one has stepped forward yet.
If you're willing to help (not just limited to
gui...@ya...), read on:
First off, I'm not sure your tcpdump is valid. There is a known problem
with doing packet captures on a machine with HW checksumming that
is involved in the TCP session.
http://www.ethereal.com/lists/ethereal-users/200507/msg00234.html
Ideally you should do the packet capture on a machine not involved in
the TCP session and with HW checksumming turned off. (you will probably
need a hub or will need to configure a monitor port on a switch). If
neither of these options are available, you could try inserting a LSR into
your network and do the packet capture on the LSR (LSRs do not touch the IP=
v4
header)
Once you have the ability to do valid packet captures then ideally
you should send me the raw pcap files (along with the MAC addresses of
the ethernet interfaces involved).
If you are unable to get valid packet capture then you can still help
me by trying some topologies/configuration options.
Before you do any testing, let me know what tools you have available
and I can help formalize some testing that will help me solve the issue.
On Wed, Dec 21, 2005 at 11:21:32PM +0000, guilhermemtorresbase-lista@yahoo.=
com.br wrote:
> Hello,
>=20
> I`m having some problems with MPLS when making tcp
> connections using MPLS (I`m trying to test with ssh
> and www. ICMP works fine.). I have two FC2 machines
> with rpm installations (I tryed to compile by hand and
> use KNOPPIX too, but I got the same erros).
>=20
> I did a simple testbed like:
>=20
> 1000
> Host A --------------- > Host B
> < ---------------
> 2000
>=20
> I used the following commands to configure:
>=20
> #########
> #Host A:#
> #########
>=20
> ifconfig eth2 192.168.0.1 netmask 255.255.255.0
> mpls nhlfe add key 0=20
> mpls nhlfe change key 0x00000002 instructions push gen
> 1000 nexthop eth2 ipv4 192.168.0.2
> ip route add 192.168.0.2/32 via 192.168.0.1 spec_nh
> 0x8847 0x0000002 advmss 1400
> mpls labelspace add dev eth2 labelspace 0
> mpls ilm add label gen 2000 labelspace 0
>=20
>=20
> #########
> #Host B:#
> #########
>=20
> ifconfig eth0 192.168.0.2 netmask 255.255.255.0
> mpls nhlfe add key 0=20
> mpls nhlfe change key 0x00000002 instructions push gen
> 2000 nexthop eth0 ipv4 192.168.0.1
> ip route add 192.168.0.1/32 via 192.168.0.2 spec_nh
> 0x8847 0x0000002 advmss 1400
> mpls labelspace add dev eth0 labelspace 0
> mpls ilm add label gen 1000 labelspace 0
>=20
> ----
>=20
> The ssh connection only works if I disable the tx/rx
> checksum with ethtool.
> I will copy a tcpdump of a ssh connection to help you
> understand the problem.
>=20
> -----
> 21:06:07.774317 MPLS (label 2000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 35448, offset 0,
> flags [DF], proto 6, length: 60) 192.168.0.2.32779 >
> 192.168.0.1.ssh: S [tcp sum ok]
> 1525719340:1525719340(0) win 5600 <mss
> 1400,sackOK,timestamp 5188436 0,nop,wscale 2>
> 0x0000: 007d 0140 4500 003c 8a78 4000 4006
> 2ef0 .}.@E..<.x@.@...
> 0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
> a12c ............Z..,
> 0x0020: 0000 0000 a002 15e0 092c 0000 0204
> 0578 .........,.....x
> 0x0030: 0402 080a 004f 2b54 0000 0000 0103
> 0302 .....O+T........
> 21:06:07.777745 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 0, offset 0, flags
> [DF], proto 6, length: 60) 192.168.0.1.ssh >
> 192.168.0.2.32779: S [tcp sum ok]
> 2714454171:2714454171(0) ack 1525719341 win 5552 <mss
> 1400,sackOK,timestamp 9334616 5188436,nop,wscale 2>
> 0x0000: 003e 8140 4500 003c 0000 4000 4006
> b968 .>.@E..<..@.@..h
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489b ..............H.
> 0x0020: 5af0 a12d a012 15b0 aefd 0000 0204
> 0578 Z..-...........x
> 0x0030: 0402 080a 008e 6f58 004f 2b54 0103
> 0302 ......oX.O+T....
> 21:06:07.774606 MPLS (label 2000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 35450, offset 0,
> flags [DF], proto 6, length: 52) 192.168.0.2.32779 >
> 192.168.0.1.ssh: . [tcp sum ok] ack 1 win 1400
> <nop,nop,timestamp 5188437 9334616>
> 0x0000: 007d 0140 4500 0034 8a7a 4000 4006
> 2ef6 .}.@E..4.z@.@...
> 0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
> a12d ............Z..-
> 0x0020: a1cb 489c 8010 0578 edbf 0000 0101
> 080a ..H....x........
> 0x0030: 004f 2b55 008e 6f58 =20
> .O+U..oX
> 21:06:07.776026 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10181, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->52a3)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9334618
> 5188437>
> 0x0000: 003e 8140 4500 004d 27c5 4000 4006
> 9192 .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 6f5a 004f 2b55 5353 482d 312e
> 3939 ..oZ.O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a
> 21:06:07.976486 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10183, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->51da)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9334819
> 5188437>
> 0x0000: 003e 8140 4500 004d 27c7 4000 4006
> 9190 .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 7023 004f 2b55 5353 482d 312e
> 3939 ..p#.O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:08.378424 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10185, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->5048)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9335221
> 5188437>
> 0x0000: 003e 8140 4500 004d 27c9 4000 4006
> 918e .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 71b5 004f 2b55 5353 482d 312e
> 3939 ..q..O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:09.182300 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10187, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->4d24)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9336025
> 5188437>
> 0x0000: 003e 8140 4500 004d 27cb 4000 4006
> 918c .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 74d9 004f 2b55 5353 482d 312e
> 3939 ..t..O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:10.790058 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10189, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->46dc)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9337633
> 5188437>
> 0x0000: 003e 8140 4500 004d 27cd 4000 4006
> 918a .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 7b21 004f 2b55 5353 482d 312e
> 3939 ..{!.O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:14.005571 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10191, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->3a4c)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9340849
> 5188437>
> 0x0000: 003e 8140 4500 004d 27cf 4000 4006
> 9188 .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e 87b1 004f 2b55 5353 482d 312e
> 3939 .....O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:20.436593 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10193, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->212c)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9347281
> 5188437>
> 0x0000: 003e 8140 4500 004d 27d1 4000 4006
> 9186 .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e a0d1 004f 2b55 5353 482d 312e
> 3939 .....O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:29.122144 arp who-has 192.168.0.2 tell
> 192.168.0.1
> 0x0000: 0001 0800 0604 0001 000c f16e e562
> c0a8 ...........n.b..
> 0x0010: 0001 0000 0000 0000 c0a8 0002 =20
> ............
> 21:06:29.122395 arp reply 192.168.0.2 is-at
> 00:12:3f:fc:ab:e9
> 0x0000: 0001 0800 0604 0002 0012 3ffc abe9
> c0a8 ..........?.....
> 0x0010: 0002 000c f16e e562 c0a8 0001 0000
> 0000 .....n.b........
> 0x0020: 0000 0000 0000 0000 0000 0000 0000 =20
> ..............
> 21:06:33.298637 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10195, offset 0,
> flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
> 192.168.0.2.32779: P [bad tcp cksum 8193 (->eeeb)!]
> 1:26(25) ack 1 win 1388 <nop,nop,timestamp 9360145
> 5188437>
> 0x0000: 003e 8140 4500 004d 27d3 4000 4006
> 9184 .>.@E..M'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 489c ..............H.
> 0x0020: 5af0 a12d 8018 056c 8193 0000 0101
> 080a Z..-...l........
> 0x0030: 008e d311 004f 2b55 5353 482d 312e
> 3939 .....O+USSH-1.99
> 0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
> 7032 -OpenSSH_3.6.1p2
> 0x0050: 0a =20
> .
> 21:06:42.916901 MPLS (label 2000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 35452, offset 0,
> flags [DF], proto 6, length: 52) 192.168.0.2.32779 >
> 192.168.0.1.ssh: F [tcp sum ok] 1:1(0) ack 1 win 1400
> <nop,nop,timestamp 5223582 9334616>
> 0x0000: 007d 0140 4500 0034 8a7c 4000 4006
> 2ef4 .}.@E..4.|@.@...
> 0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
> a12d ............Z..-
> 0x0020: a1cb 489c 8011 0578 6475 0000 0101
> 080a ..H....xdu......
> 0x0030: 004f b49e 008e 6f58 =20
> .O....oX
> 21:06:42.917406 MPLS (label 1000, exp 0, [S], ttl 64)
> IP (tos 0x0, ttl 64, id 10197, offset 0,
> flags [DF], proto 6, length: 52) 192.168.0.1.ssh >
> 192.168.0.2.32779: F [tcp sum ok] 26:26(0) ack 2 win
> 1388 <nop,nop,timestamp 9369765 5223582>
> 0x0000: 003e 8140 4500 0034 27d5 4000 4006
> 919b .>.@E..4'.@.@...
> 0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
> 48b5 ..............H.
> 0x0020: 5af0 a12e 8011 056c db19 0000 0101
> 080a Z......l........
> 0x0030: 008e f8a5 004f b49e =20
> .....O..
> --------------
>=20
> Best regards.
>=20
>=20
> =09
>=20
>=20
>=20
> =09
> =09
> _______________________________________________________=20
> Yahoo! doce lar. Fa?a do Yahoo! sua homepage.=20
> http://br.yahoo.com/homepageset.html=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
--=20
James R. Leu
jl...@mi...
|
|
From: <gui...@ya...> - 2005-12-21 23:21:45
|
Hello,
I`m having some problems with MPLS when making tcp
connections using MPLS (I`m trying to test with ssh
and www. ICMP works fine.). I have two FC2 machines
with rpm installations (I tryed to compile by hand and
use KNOPPIX too, but I got the same erros).
I did a simple testbed like:
1000
Host A --------------- > Host B
< ---------------
2000
I used the following commands to configure:
#########
#Host A:#
#########
ifconfig eth2 192.168.0.1 netmask 255.255.255.0
mpls nhlfe add key 0
mpls nhlfe change key 0x00000002 instructions push gen
1000 nexthop eth2 ipv4 192.168.0.2
ip route add 192.168.0.2/32 via 192.168.0.1 spec_nh
0x8847 0x0000002 advmss 1400
mpls labelspace add dev eth2 labelspace 0
mpls ilm add label gen 2000 labelspace 0
#########
#Host B:#
#########
ifconfig eth0 192.168.0.2 netmask 255.255.255.0
mpls nhlfe add key 0
mpls nhlfe change key 0x00000002 instructions push gen
2000 nexthop eth0 ipv4 192.168.0.1
ip route add 192.168.0.1/32 via 192.168.0.2 spec_nh
0x8847 0x0000002 advmss 1400
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 1000 labelspace 0
----
The ssh connection only works if I disable the tx/rx
checksum with ethtool.
I will copy a tcpdump of a ssh connection to help you
understand the problem.
-----
21:06:07.774317 MPLS (label 2000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 35448, offset 0,
flags [DF], proto 6, length: 60) 192.168.0.2.32779 >
192.168.0.1.ssh: S [tcp sum ok]
1525719340:1525719340(0) win 5600 <mss
1400,sackOK,timestamp 5188436 0,nop,wscale 2>
0x0000: 007d 0140 4500 003c 8a78 4000 4006
2ef0 .}.@E..<.x@.@...
0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
a12c ............Z..,
0x0020: 0000 0000 a002 15e0 092c 0000 0204
0578 .........,.....x
0x0030: 0402 080a 004f 2b54 0000 0000 0103
0302 .....O+T........
21:06:07.777745 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 0, offset 0, flags
[DF], proto 6, length: 60) 192.168.0.1.ssh >
192.168.0.2.32779: S [tcp sum ok]
2714454171:2714454171(0) ack 1525719341 win 5552 <mss
1400,sackOK,timestamp 9334616 5188436,nop,wscale 2>
0x0000: 003e 8140 4500 003c 0000 4000 4006
b968 .>.@E..<..@.@..h
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489b ..............H.
0x0020: 5af0 a12d a012 15b0 aefd 0000 0204
0578 Z..-...........x
0x0030: 0402 080a 008e 6f58 004f 2b54 0103
0302 ......oX.O+T....
21:06:07.774606 MPLS (label 2000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 35450, offset 0,
flags [DF], proto 6, length: 52) 192.168.0.2.32779 >
192.168.0.1.ssh: . [tcp sum ok] ack 1 win 1400
<nop,nop,timestamp 5188437 9334616>
0x0000: 007d 0140 4500 0034 8a7a 4000 4006
2ef6 .}.@E..4.z@.@...
0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
a12d ............Z..-
0x0020: a1cb 489c 8010 0578 edbf 0000 0101
080a ..H....x........
0x0030: 004f 2b55 008e 6f58
.O+U..oX
21:06:07.776026 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10181, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->52a3)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9334618
5188437>
0x0000: 003e 8140 4500 004d 27c5 4000 4006
9192 .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 6f5a 004f 2b55 5353 482d 312e
3939 ..oZ.O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
21:06:07.976486 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10183, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->51da)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9334819
5188437>
0x0000: 003e 8140 4500 004d 27c7 4000 4006
9190 .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 7023 004f 2b55 5353 482d 312e
3939 ..p#.O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:08.378424 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10185, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->5048)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9335221
5188437>
0x0000: 003e 8140 4500 004d 27c9 4000 4006
918e .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 71b5 004f 2b55 5353 482d 312e
3939 ..q..O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:09.182300 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10187, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->4d24)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9336025
5188437>
0x0000: 003e 8140 4500 004d 27cb 4000 4006
918c .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 74d9 004f 2b55 5353 482d 312e
3939 ..t..O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:10.790058 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10189, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->46dc)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9337633
5188437>
0x0000: 003e 8140 4500 004d 27cd 4000 4006
918a .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 7b21 004f 2b55 5353 482d 312e
3939 ..{!.O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:14.005571 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10191, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->3a4c)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9340849
5188437>
0x0000: 003e 8140 4500 004d 27cf 4000 4006
9188 .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e 87b1 004f 2b55 5353 482d 312e
3939 .....O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:20.436593 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10193, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->212c)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9347281
5188437>
0x0000: 003e 8140 4500 004d 27d1 4000 4006
9186 .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e a0d1 004f 2b55 5353 482d 312e
3939 .....O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:29.122144 arp who-has 192.168.0.2 tell
192.168.0.1
0x0000: 0001 0800 0604 0001 000c f16e e562
c0a8 ...........n.b..
0x0010: 0001 0000 0000 0000 c0a8 0002
............
21:06:29.122395 arp reply 192.168.0.2 is-at
00:12:3f:fc:ab:e9
0x0000: 0001 0800 0604 0002 0012 3ffc abe9
c0a8 ..........?.....
0x0010: 0002 000c f16e e562 c0a8 0001 0000
0000 .....n.b........
0x0020: 0000 0000 0000 0000 0000 0000 0000
..............
21:06:33.298637 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10195, offset 0,
flags [DF], proto 6, length: 77) 192.168.0.1.ssh >
192.168.0.2.32779: P [bad tcp cksum 8193 (->eeeb)!]
1:26(25) ack 1 win 1388 <nop,nop,timestamp 9360145
5188437>
0x0000: 003e 8140 4500 004d 27d3 4000 4006
9184 .>.@E..M'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
489c ..............H.
0x0020: 5af0 a12d 8018 056c 8193 0000 0101
080a Z..-...l........
0x0030: 008e d311 004f 2b55 5353 482d 312e
3939 .....O+USSH-1.99
0x0040: 2d4f 7065 6e53 5348 5f33 2e36 2e31
7032 -OpenSSH_3.6.1p2
0x0050: 0a
.
21:06:42.916901 MPLS (label 2000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 35452, offset 0,
flags [DF], proto 6, length: 52) 192.168.0.2.32779 >
192.168.0.1.ssh: F [tcp sum ok] 1:1(0) ack 1 win 1400
<nop,nop,timestamp 5223582 9334616>
0x0000: 007d 0140 4500 0034 8a7c 4000 4006
2ef4 .}.@E..4.|@.@...
0x0010: c0a8 0002 c0a8 0001 800b 0016 5af0
a12d ............Z..-
0x0020: a1cb 489c 8011 0578 6475 0000 0101
080a ..H....xdu......
0x0030: 004f b49e 008e 6f58
.O....oX
21:06:42.917406 MPLS (label 1000, exp 0, [S], ttl 64)
IP (tos 0x0, ttl 64, id 10197, offset 0,
flags [DF], proto 6, length: 52) 192.168.0.1.ssh >
192.168.0.2.32779: F [tcp sum ok] 26:26(0) ack 2 win
1388 <nop,nop,timestamp 9369765 5223582>
0x0000: 003e 8140 4500 0034 27d5 4000 4006
919b .>.@E..4'.@.@...
0x0010: c0a8 0001 c0a8 0002 0016 800b a1cb
48b5 ..............H.
0x0020: 5af0 a12e 8011 056c db19 0000 0101
080a Z......l........
0x0030: 008e f8a5 004f b49e
.....O..
--------------
Best regards.
_______________________________________________________
Yahoo! doce lar. Faça do Yahoo! sua homepage.
http://br.yahoo.com/homepageset.html
|
|
From: James R. L. <jl...@mi...> - 2005-12-21 14:51:34
|
Thinking back on this, in your config you created a loop! Packets get put on the LSP 1000 at LER1, they loop onto LSP 1002 at LER2, then LER1 loops them back onto LSP 1000. It would be interesting to see what the ILM/NHLFE counters looked like after sending one ping packet.... just throught I'd mention it. On Wed, Dec 21, 2005 at 08:43:44AM -0600, James R. Leu wrote: > First, you need to work on your ascii-art-foo a bit :-) > -don't use tabs > -use a 80 column, fixed font, text editor (vi, emacs) >=20 > I've cleaned up your drawing: > =20 > 192.168.101.0/24 192.168.103.0/24 > | | > | | > ------eth0 eth0------eth1 v eth1----eth0 eth0---eth1 v eth1---= --- > | HostA |--------| LER1 |---------| LSR |-----| LER2 |----------| Hos= tB | > ------.10 ^ 20-------20 30-----30 ^ 40-----40 50---= --- > | | > | |=20 > 192.168.100.0/24 192.168.102.0/24 >=20 >=20 > Comments in-line... >=20 > > Configuration > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > > HostA > > ------ > > ip route add 192.168.103.50/32 via 192.168.100.20 > >=20 > > LER1 > > ------ > > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.= 168.100.20 > > ip route add 192.168.103.50/32 via 192.168.101.30 spec_nh 0x8847 0x2 > > mpls labelspace add dev eth1 labelspace 0 > > mpls ilm add label gen 1002 labelspace 0 > > mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x2 >=20 > No XC required. At the simplest level XCs are used for > labelswaping, therefor they are not used on LERS. >=20 > > LSR > > ----- > > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.= 168.102.40 > > mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 192.= 168.101.20 > > ip route add 192.168.103.50/32 via 192.168.102.40 spec_nh 0x8847 0x2 > > ip route add 192.168.100.10/32 via 192.168.101.20 spec_nh 0x8847 0x3 > > mpls labelspace add dev eth0 labelspace 0 > > mpls labelspace add dev eth1 labelspace 0 > > mpls ilm add label gen 1000 labelspace 0 > > mpls ilm add label gen 1002 labelspace 0=20 > > mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2 > > mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x3 >=20 > No need for the 'ip route' statements. You're labelswaping here, the > packets will never leaves the MPLS stack, therefore they will never see > the IPv4 routing table. >=20 > > LER2 > > ----- > > mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 192.= 168.103.40 > > ip route add 192.168.100.10/32 via 192.168.103.40 spec_nh 0x8847 0x2 > > mpls labelspace add dev eth0 labelspace 0 > > mpls ilm add label gen 1000 labelspace 0 > > mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2 >=20 > Again no XCs on LERs. >=20 > > HostB > > ------ > > ip route add 192.168.100.10/32 via 192.168.103.40 > --=20 > James R. Leu > jl...@mi... --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2005-12-21 14:44:16
|
First, you need to work on your ascii-art-foo a bit :-)
-don't use tabs
-use a 80 column, fixed font, text editor (vi, emacs)
I've cleaned up your drawing:
=20
192.168.101.0/24 192.168.103.0/24
| |
| |
------eth0 eth0------eth1 v eth1----eth0 eth0---eth1 v eth1------
| HostA |--------| LER1 |---------| LSR |-----| LER2 |----------| HostB=
|
------.10 ^ 20-------20 30-----30 ^ 40-----40 50------
| |
| |=20
192.168.100.0/24 192.168.102.0/24
Comments in-line...
> Configuration
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> HostA
> ------
> ip route add 192.168.103.50/32 via 192.168.100.20
>=20
> LER1
> ------
> mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.16=
8.100.20
> ip route add 192.168.103.50/32 via 192.168.101.30 spec_nh 0x8847 0x2
> mpls labelspace add dev eth1 labelspace 0
> mpls ilm add label gen 1002 labelspace 0
> mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x2
No XC required. At the simplest level XCs are used for
labelswaping, therefor they are not used on LERS.
> LSR
> -----
> mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.16=
8.102.40
> mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 192.16=
8.101.20
> ip route add 192.168.103.50/32 via 192.168.102.40 spec_nh 0x8847 0x2
> ip route add 192.168.100.10/32 via 192.168.101.20 spec_nh 0x8847 0x3
> mpls labelspace add dev eth0 labelspace 0
> mpls labelspace add dev eth1 labelspace 0
> mpls ilm add label gen 1000 labelspace 0
> mpls ilm add label gen 1002 labelspace 0=20
> mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
> mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x3
No need for the 'ip route' statements. You're labelswaping here, the
packets will never leaves the MPLS stack, therefore they will never see
the IPv4 routing table.
> LER2
> -----
> mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 192.16=
8.103.40
> ip route add 192.168.100.10/32 via 192.168.103.40 spec_nh 0x8847 0x2
> mpls labelspace add dev eth0 labelspace 0
> mpls ilm add label gen 1000 labelspace 0
> mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
Again no XCs on LERs.
> HostB
> ------
> ip route add 192.168.100.10/32 via 192.168.103.40
--=20
James R. Leu
jl...@mi...
|
|
From: allen <as...@gm...> - 2005-12-21 06:53:41
|
Hi All,
I want to continue trying another example as follows. Similarly to =
establish two way LSP(from HostA to HostB using label 1000, and HostB to =
HostA using label 1002). then use "ping" to test(from HostA to HostB). =
But failed again. Please tell me the problem of configuration and how to =
modify. thanks
=20
192.168.101.0/24 =
192.168.103.0/24 =20
| =
|
| =
|
------eth0 eth0------eth1 v eth1----eth0 =
eth0---eth1 v eth1------
| HostA |---------| LER1 |-------------| LSR |----------| LER2 =
|------------| HostB |
------.10 ^ 20-------20 30-----30 ^ =
40-----40 50------
| =
| =20
| =
|=20
192.168.100.0/24 192.168.102.0/24
=20
=20
Configuration
=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
HostA
------
ip route add 192.168.103.50/32 via 192.168.100.20
LER1
------
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 =
192.168.100.20
ip route add 192.168.103.50/32 via 192.168.101.30 spec_nh 0x8847 0x2
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1002 labelspace 0
mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x2
=20
LSR
-----
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 =
192.168.102.40
mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 =
192.168.101.20
ip route add 192.168.103.50/32 via 192.168.102.40 spec_nh 0x8847 0x2
ip route add 192.168.100.10/32 via 192.168.101.20 spec_nh 0x8847 0x3
mpls labelspace add dev eth0 labelspace 0
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1000 labelspace 0
mpls ilm add label gen 1002 labelspace 0=20
mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x3
LER2
-----
mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 =
192.168.103.40
ip route add 192.168.100.10/32 via 192.168.103.40 spec_nh 0x8847 0x2
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 1000 labelspace 0
mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
HostB
------
ip route add 192.168.100.10/32 via 192.168.103.40 |
|
From: James R. L. <jl...@mi...> - 2005-12-20 02:45:01
|
Do you have mpls4 loaded? I have tried to make everything with mpls-linux 1.950 modular (I may have gone over board :-). The layer controlling L3 -> MPLS is called the shim layer and could be made into a module (don't threaten me or I'll do it ;-). The layer controlling MPLS to IPv4 is a module (mpls4). There is a module for the tunnel interface (mpls_tunnel), which if loaded multiple time (with different names) will create multiple mpls tunnel interfaces. And of course MPLS itself is a module now. The MPLS -> IPv6 module is called mpls6 and there is a module the handles MPLS -> ethernet called mplsbr (for EoMPLS). Finally there are IPtables and ebtables target modules for mapping iptables or ebtables rules to MPLS. Do a 'modprobe mpls4' this will load the protocol driver for IPv4 which handle the ipv4 part of the nexthop creation and handles delivery of MPLS packets to IPv4 on the egress LER. I have found an error with unloading the mpls4 module and when creating an ilm (mpls command appears to segfault) These are related to locking issues that popped up when compiling the FC4 RPM. I'm working on fixes. Once I have all of the bugs worked out, I'll make a formal announcement. In the meantime I'll continue to update SF with my incremental changes. (make sure you have iproute 1.950c) On Mon, Dec 19, 2005 at 08:22:40PM -0500, Siddhardha N. Garige wrote: > Hi, > I am trying to setup a simple LSP between two linux boxes and i am having > some trouble. > Here is the trace. >=20 >=20 > -bash-3.00# cat /sys/mpls/version > 1.950 >=20 > -bash-3.00# mpls nhlfe add key 0 > NHLFE entry key 0x00000003 mtu 0 propagate_ttl > (0 bytes, 0 pkts) >=20 > -bash-3.00# mpls nhlfe change key 0x3 instructions push gen 1000 nexthop > eth0 ipv4 172.16.88.2 > RTNETLINK answers: Operation not permitted >=20 > Debug messages: > -bash-3.00# tail /var/log/debug > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:89:mpls_instrs_free: enter > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:65:mpls_instr_release: enter > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:73:mpls_instr_release: exit > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:65:mpls_instr_release: enter > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:73:mpls_instr_release: exit > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_instr.c:95:mpls_instrs_free: exit > Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG > net/mpls/mpls_netlink.c:339:genl_mpls_nhlfe_new: Exit: -1 >=20 > Any help?.. >=20 > Regards, > Sid --=20 James R. Leu jl...@mi... |
|
From: Siddhardha N. G. <ga...@gm...> - 2005-12-20 01:22:46
|
Hi,
I am trying to setup a simple LSP between two linux boxes and i am having
some trouble.
Here is the trace.
-bash-3.00# cat /sys/mpls/version
1.950
-bash-3.00# mpls nhlfe add key 0
NHLFE entry key 0x00000003 mtu 0 propagate_ttl
(0 bytes, 0 pkts)
-bash-3.00# mpls nhlfe change key 0x3 instructions push gen 1000 nexthop
eth0 ipv4 172.16.88.2
RTNETLINK answers: Operation not permitted
Debug messages:
-bash-3.00# tail /var/log/debug
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:89:mpls_instrs_free: enter
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:65:mpls_instr_release: enter
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:73:mpls_instr_release: exit
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:65:mpls_instr_release: enter
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:73:mpls_instr_release: exit
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_instr.c:95:mpls_instrs_free: exit
Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
net/mpls/mpls_netlink.c:339:genl_mpls_nhlfe_new: Exit: -1
Any help?..
Regards,
Sid
|
|
From: James R. L. <jl...@mi...> - 2005-12-19 14:17:51
|
I just started working on porting quagga-mpls to the new netlink interface. Hopefully you will start to see submission to the tree this evening. On Mon, Dec 19, 2005 at 11:10:46AM +0100, Joan Ruiz wrote: > Hi all, >=20 > =20 >=20 > I've been testing the new release these days and it looks promising. >=20 > I've been able to build and run the new kernel, ebtables, iptables and > iproute both from the rpm package in sf and compiling the sources from > Perforce. >=20 > =20 >=20 > I've also tested latest version of quagga-mpls / ldp-portable in Perforce > but this appears not to be working. >=20 > =20 >=20 > I try to build it following this steps: >=20 > =20 >=20 > Edit and run ./create-links in the ldp folder >=20 > ./configure --enable-user=3Droot --enable-group=3Droot >=20 > make >=20 > make install >=20 > =20 >=20 > With the latests patches from Hasso now quagga builds OK. >=20 > =20 >=20 > Finally I edit a simple zebra.conf script and atempt to run zebra with > "zebra -d"=20 >=20 > zebra.conf contains: >=20 > ----- >=20 > hostname Router >=20 > password zebra >=20 > enable password zebra >=20 > ------ >=20 > =20 >=20 > I obtain the message "Aborted" >=20 > =20 >=20 > My development equipment is a Fedora Core 4. >=20 > =20 >=20 > Has anybody found the same problem? >=20 > =20 >=20 > Joan=20 >=20 --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2005-12-19 14:16:35
|
LSR is the problem. Instead of adding routes you need to add cross connect= s. mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2 mpls xc add ilm_label gen 1002 ilm_labelspace 0 nhlfe_key 0x3 On Mon, Dec 19, 2005 at 03:03:13PM +0800, Allen wrote: > Hello: > I try to test a example as follows. I want to establish two way L= SP(from LER1 to LER2 using label 1000, and LER2 to LER1 using label 1002). = When I finish the configuration and using "ping" (from LER1 to LER2) to tes= t. I can't see the "ping reply". I guess the LSR's configuration has proble= m. Please tell me my configuration of LSR is correct or not? Furthermore te= ll me how to modify the configuration...thanks=20 >=20 > ps. Thanks for your attention and sorry about my poor English. >=20 > 192.168.101.0/24 > | =20 > | =20 > | =20 > ------eth0 eth0------eth1 v eth1------ =20 > | LER1 |---------| LSR |-------------| LER2 | > ------.10 ^ 20-----20 30------ =20 > | =20 > | =20 > 192.168.100.0/24 =20 > Configuration > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D >=20 > LER1 > ------ > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 192.168= .100.20 > ip route add 192.168.101.30/32 via 192.168.100.20 spec_nh 0x8847 0x2 > mpls labelspace add dev eth0 labelspace 0 > mpls ilm add label gen 1002 labelspace 0 >=20 > LSR > ----- > mpls nhlfe add key 0 instructions push gen 1000 nexthop eth1 ipv4 192.168= .101.30 > mpls nhlfe add key 0 instructions push gen 1002 nexthop eth0 ipv4 192.168= .100.10 > ip route add 192.168.101.30/32 via 192.168.101.30 spec_nh 0x8847 0x2 > ip route add 192.168.100.10/32 via 192.168.100.10 spec_nh 0x8847 0x3 > mpls labelspace add dev eth0 labelspace 0 > mpls labelspace add dev eth1 labelspace 0 > mpls ilm add label gen 1000 labelspace 0 > mpls ilm add label gen 1002 labelspace 0=20 >=20 > LER2 > ----- > mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 192.168= .101.20 > ip route add 192.168.100.10/32 via 192.168.101.20 spec_nh 0x8847 0x2 > mpls labelspace add dev eth0 labelspace 0 > mpls ilm add label gen 1000 labelspace 0 --=20 James R. Leu jl...@mi... |
|
From: Joan R. <jr...@sa...> - 2005-12-19 10:11:57
|
Hi all, I've been testing the new release these days and it looks promising. I've been able to build and run the new kernel, ebtables, iptables and iproute both from the rpm package in sf and compiling the sources from Perforce. I've also tested latest version of quagga-mpls / ldp-portable in Perforce but this appears not to be working. I try to build it following this steps: Edit and run ./create-links in the ldp folder ./configure --enable-user=root --enable-group=root make make install With the latests patches from Hasso now quagga builds OK. Finally I edit a simple zebra.conf script and atempt to run zebra with "zebra -d" zebra.conf contains: ----- hostname Router password zebra enable password zebra ------ I obtain the message "Aborted" My development equipment is a Fedora Core 4. Has anybody found the same problem? Joan |
|
From: Allen <as...@gm...> - 2005-12-19 07:03:28
|
Hello:
I try to test a example as follows. I want to establish two way =
LSP(from LER1 to LER2 using label 1000, and LER2 to LER1 using label =
1002). When I finish the configuration and using "ping" (from LER1 to =
LER2) to test. I can't see the "ping reply". I guess the LSR's =
configuration has problem. Please tell me my configuration of LSR is =
correct or not? Furthermore tell me how to modify the =
configuration...thanks=20
ps. Thanks for your attention and sorry about my poor English.
192.168.101.0/24
| =20
| =20
| =20
------eth0 eth0------eth1 v eth1------ =20
| LER1 |---------| LSR |-------------| LER2 |
------.10 ^ 20-----20 30------ =20
| =20
| =20
192.168.100.0/24 =20
Configuration
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
LER1
------
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth0 ipv4 =
192.168.100.20
ip route add 192.168.101.30/32 via 192.168.100.20 spec_nh 0x8847 0x2
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 1002 labelspace 0
LSR
-----
mpls nhlfe add key 0 instructions push gen 1000 nexthop eth1 ipv4 =
192.168.101.30
mpls nhlfe add key 0 instructions push gen 1002 nexthop eth0 ipv4 =
192.168.100.10
ip route add 192.168.101.30/32 via 192.168.101.30 spec_nh 0x8847 0x2
ip route add 192.168.100.10/32 via 192.168.100.10 spec_nh 0x8847 0x3
mpls labelspace add dev eth0 labelspace 0
mpls labelspace add dev eth1 labelspace 0
mpls ilm add label gen 1000 labelspace 0
mpls ilm add label gen 1002 labelspace 0=20
LER2
-----
mpls nhlfe add key 0 instructions push gen 1002 nexthop eth1 ipv4 =
192.168.101.20
ip route add 192.168.100.10/32 via 192.168.101.20 spec_nh 0x8847 0x2
mpls labelspace add dev eth0 labelspace 0
mpls ilm add label gen 1000 labelspace 0
|
|
From: James R. L. <jl...@mi...> - 2005-12-18 15:05:15
|
MPLS linux no longer supports the 2.4.x kernel tree. Please switch to a 2.6.9 kernel and use 1.946 or wait until the pending release of mpls-linux 1.950 with will support the 2.6.15-rc5 kernel. On Sun, Dec 18, 2005 at 11:38:30AM +0000, ashish verma wrote: > hi all.. > i'm not able to find mpls-linux patch for kernel 2.4.20-8 > help me if someone knows abt it.. > thanks in advance >=20 > Send instant messages to your online friends http://in.messenger.yahoo.co= m=20 --=20 James R. Leu jl...@mi... |
|
From: ashish v. <ash...@ya...> - 2005-12-18 11:38:50
|
hi all.. i'm not able to find mpls-linux patch for kernel 2.4.20-8 help me if someone knows abt it.. thanks in advance Send instant messages to your online friends http://in.messenger.yahoo.com |
|
From: cyb3rbyt3 <111...@st...> - 2005-12-14 05:43:24
|
OK i will try to installing iproute2, are anyone in this forum have
documentation about MPLS? i need it to do my final task... thanks
http://pinguin.stttelkom.ac.id
|
|
From: Siddhardha N. G. <ga...@gm...> - 2005-12-14 04:27:24
|
Yes i think you are right. I got little confused with RSVP-TE tunnels. I will do little more study on this. Any update on tunnel command ? On 12/9/05, James R. Leu <jl...@mi...> wrote: > > I think you are talking about RSVP-TE signaled 'tunnels' MPLS Linux does > not yet have a RSVP-TE implementation. > > On Fri, Dec 09, 2005 at 03:39:19PM -0500, Siddhardha N. Garige wrote: > > Hi, > > I am trying to understand MPLS tunnel concept and according to RFC > 3812, an > > explicitly routed LSP (ERLSP) is referred to as an MPLS tunnel. I am > > planning to connecting my router (CE) to a PE on a T1 link using MPLS > > tunnel. I have only source and destination nodes and i am setting up a > LSP > > in between them. I dont have any intermediate nodes. Destination node i= s > in > > one hop reach. If i make this LSP into a tunnel will it be conceptually > > right? > > > > My understanding of Explicit routing is you have various paths availabl= e > > from source to destination and you specify a specific path. Since i hav= e > > only one path here, it is no different from regular LSP. Can someone > explain > > to me PLs? > > > > Also, I compiled and installed MPLS kernel and i was able to setup LSP > in > > between two linux boxes. I am trying to create a tunnel using mpls > tunnel > > command and i am having some trouble. Here is a screen shot.. > > > > root@darkstar:/home/sid# mplsversion > > 1.950 > > > > root@darkstar:/usr/sbin# mpls nhlfe add key 0 > > NHLFE entry key 0x00000003 mtu 0 propagate_ttl > > (0 bytes, 0 pkts) > > root@darkstar:/usr/sbin# mpls tunnel add dev eth0 nhlfe 0x3 > > Option "add" is unknown, try "mpls -help". > > > > any help? > > > > > > Thanks, > > Sid > > -- > James R. Leu > jl...@mi... > > > |
|
From: James R. L. <jl...@mi...> - 2005-12-13 02:19:22
|
I finally fixed the 'show' commands. Update your iproute2-mpls tree
and you will have the fix. I did update the usage info to show how to
delete a labelspace, I didn't use your method, but thanks for pointing
out that I needed to include that info.
On Fri, Dec 09, 2005 at 01:34:19AM -0600, James R. Leu wrote:
> OK. I was able to duplicate your issue and I think I submitted a fix
> for the add/delete/change/set commands not returnning. I still need
> to figure out the show commands. Basically my tree was out of sync with =
the
> repository, so you didn't have the same code as me.
>=20
> Update you iproute-mpls tree and you will get my fix. One thing to note
> is I changed the syntax of the labelspace command:
>=20
> mpls labelspace set dev eth0 labelspace 0
> ^
> |
> no add or delete
> To delete, set the
> labelspace to -1
>=20
> On Thu, Dec 08, 2005 at 09:35:27AM -0500, Bob Beers wrote:
> > On 12/7/05, James R. Leu <jl...@mi...> wrote:
> > > Could you send me the kernel debug from running the labelspace command
> > > that hangs?
> >=20
> > How about also an strace:
> >=20
> > root@beedril:~# strace mpls labelspace add dev eth0 labelspace 0
> > execve("/usr/sbin/mpls", ["mpls", "labelspace", "add", "dev", "eth0",
> > "labelspace", "0"], [/* 30 vars */]) =3D 0
> > uname({sys=3D"Linux", node=3D"beedril", ...}) =3D 0
> > brk(0) =3D 0x8053000
> > access("/etc/ld.so.preload", R_OK) =3D -1 ENOENT (No such file or =
directory)
> > open("/etc/ld.so.cache", O_RDONLY) =3D 3
> > fstat64(3, {st_mode=3DS_IFREG|0644, st_size=3D111746, ...}) =3D 0
> > mmap2(NULL, 111746, PROT_READ, MAP_PRIVATE, 3, 0) =3D 0xb7fc7000
> > close(3) =3D 0
> > open("/lib/tls/libm.so.6", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P3\0\000"..., 5=
12) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D176352, ...}) =3D 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> > 0) =3D 0xb7fc6000
> > mmap2(NULL, 139424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> > 0) =3D 0xb7fa3000
> > mmap2(0xb7fc4000, 8192, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20) =3D 0xb7fc4000
> > close(3) =3D 0
> > open("/lib/tls/libresolv.so.2", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200$\0"..., 51=
2) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D73805, ...}) =3D 0
> > mmap2(NULL, 75976, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> > 0) =3D 0xb7f90000
> > mprotect(0xb7f9e000, 18632, PROT_NONE) =3D 0
> > mmap2(0xb7f9f000, 8192, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe) =3D 0xb7f9f000
> > mmap2(0xb7fa1000, 6344, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7fa1000
> > close(3) =3D 0
> > open("/lib/tls/libc.so.6", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300P\1"..., 51=
2) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D1366940, ...}) =3D 0
> > mmap2(NULL, 1162428, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
> > 3, 0) =3D 0xb7e74000
> > mprotect(0xb7f89000, 27836, PROT_NONE) =3D 0
> > mmap2(0xb7f8a000, 16384, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x115) =3D 0xb7f8a000
> > mmap2(0xb7f8e000, 7356, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7f8e000
> > close(3) =3D 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> > 0) =3D 0xb7e73000
> > mprotect(0xb7f8a000, 4096, PROT_READ) =3D 0
> > set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e736c0,
> > limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
> > limit_in_pages:1, seg_not_present:0, useable:1}) =3D 0
> > munmap(0xb7fc7000, 111746) =3D 0
> > socket(PF_NETLINK, SOCK_RAW, 0) =3D 3
> > setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> > setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> > bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 0
> > getsockname(3, {sa_family=3DAF_NETLINK, pid=3D3110, groups=3D00000000},=
[12]) =3D 0
> > time(NULL) =3D 1134051713
> > sendto(3, "\24\0\0\0\22\0\1\3\202A\230C\0\0\0\0\0\200\0\0", 20, 0,
> > {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 20
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000},
> > msg_iov(1)=3D[{"\344\0\0\0\20\0\2\0\202A\230C&\f\0\0\0\0\4\3\1\0\0\0I\0=
"...,
> > 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 912
> > brk(0) =3D 0x8053000
> > brk(0x8074000) =3D 0x8074000
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000},
> > msg_iov(1)=3D[{"\24\0\0\0\3\0\2\0\202A\230C&\f\0\0\0\0\0\0\1\0\0\0I\0\0=
"...,
> > 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 20
> > close(3) =3D 0
> > socket(PF_NETLINK, SOCK_RAW, 16) =3D 3
> > setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> > setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> > bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D0000ffff}, 12) =3D 0
> > getsockname(3, {sa_family=3DAF_NETLINK, pid=3D3110, groups=3D0000ffff},=
[12]) =3D 0
> > time(NULL) =3D 1134051713
> > sendmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000}, msg_iov(1)=3D[{"
> > \0\0\0\36\0\5\4\202A\230C\0\0\0\0\n\0\0\0\f\0\4\0\4\0"..., 32}],
> > msg_controllen=3D0, msg_flags=3D0}, 0) =3D 32
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000080}, msg_iov(1)=3D[{"
> > \0\0\0\36\0\0\0\0\0\0\0\0\0\0\0\n\1\0\0\f\0\4\0\4\0\0"..., 16384}],
> > msg_controllen=3D0, msg_flags=3D0}, 0) =3D 32
> >=20
> >=20
> > and the debug messages:
> >=20
> >=20
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:650:genl_mpls_labelspace_set: enter
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_if.c:175:__mpls_set_labelspace: enter
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_if.c:189:__mpls_set_labelspace: Set labelspace for eth0
> > to 0
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:628:mpls_labelspace_event: enter
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:615:mpls_fill_labelspace: Exit: length
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:642:mpls_labelspace_event: exit
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_if.c:203:__mpls_set_labelspace: exit
> > Dec 8 09:21:53 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:654:genl_mpls_labelspace_set: Exit: 0
> >=20
> >=20
> >=20
> >=20
> >=20
> > >
> > > Do you see this problem with 'mpls ilm show'?
> > >
> >=20
> > yes: seems only 'mpls nhlfe [add|change]' return to command line prompt.
> >=20
> > root@beedril:~# strace mpls ilm show
> > execve("/usr/sbin/mpls", ["mpls", "ilm", "show"], [/* 30 vars */]) =3D 0
> > uname({sys=3D"Linux", node=3D"beedril", ...}) =3D 0
> > brk(0) =3D 0x8053000
> > access("/etc/ld.so.preload", R_OK) =3D -1 ENOENT (No such file or =
directory)
> > open("/etc/ld.so.cache", O_RDONLY) =3D 3
> > fstat64(3, {st_mode=3DS_IFREG|0644, st_size=3D111746, ...}) =3D 0
> > mmap2(NULL, 111746, PROT_READ, MAP_PRIVATE, 3, 0) =3D 0xb7ee4000
> > close(3) =3D 0
> > open("/lib/tls/libm.so.6", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P3\0\000"..., 5=
12) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D176352, ...}) =3D 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> > 0) =3D 0xb7ee3000
> > mmap2(NULL, 139424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> > 0) =3D 0xb7ec0000
> > mmap2(0xb7ee1000, 8192, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20) =3D 0xb7ee1000
> > close(3) =3D 0
> > open("/lib/tls/libresolv.so.2", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200$\0"..., 51=
2) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D73805, ...}) =3D 0
> > mmap2(NULL, 75976, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> > 0) =3D 0xb7ead000
> > mprotect(0xb7ebb000, 18632, PROT_NONE) =3D 0
> > mmap2(0xb7ebc000, 8192, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe) =3D 0xb7ebc000
> > mmap2(0xb7ebe000, 6344, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7ebe000
> > close(3) =3D 0
> > open("/lib/tls/libc.so.6", O_RDONLY) =3D 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300P\1"..., 51=
2) =3D 512
> > fstat64(3, {st_mode=3DS_IFREG|0755, st_size=3D1366940, ...}) =3D 0
> > mmap2(NULL, 1162428, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
> > 3, 0) =3D 0xb7d91000
> > mprotect(0xb7ea6000, 27836, PROT_NONE) =3D 0
> > mmap2(0xb7ea7000, 16384, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x115) =3D 0xb7ea7000
> > mmap2(0xb7eab000, 7356, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7eab000
> > close(3) =3D 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> > 0) =3D 0xb7d90000
> > mprotect(0xb7ea7000, 4096, PROT_READ) =3D 0
> > set_thread_area({entry_number:-1 -> 6, base_addr:0xb7d906c0,
> > limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
> > limit_in_pages:1, seg_not_present:0, useable:1}) =3D 0
> > munmap(0xb7ee4000, 111746) =3D 0
> > socket(PF_NETLINK, SOCK_RAW, 0) =3D 3
> > setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> > setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> > bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 0
> > getsockname(3, {sa_family=3DAF_NETLINK, pid=3D3147, groups=3D00000000},=
[12]) =3D 0
> > time(NULL) =3D 1134052385
> > sendto(3, "\24\0\0\0\22\0\1\3\"D\230C\0\0\0\0\0\200\0\0", 20, 0,
> > {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 20
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000},
> > msg_iov(1)=3D[{"\344\0\0\0\20\0\2\0\"D\230CK\f\0\0\0\0\4\3\1\0\0\0I\0\0=
"...,
> > 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 912
> > brk(0) =3D 0x8053000
> > brk(0x8074000) =3D 0x8074000
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000},
> > msg_iov(1)=3D[{"\24\0\0\0\3\0\2\0\"D\230CK\f\0\0\0\0\0\0\1\0\0\0I\0\0\0=
"...,
> > 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 20
> > close(3) =3D 0
> > socket(PF_NETLINK, SOCK_RAW, 16) =3D 3
> > setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> > setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> > bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D0000ffff}, 12) =3D 0
> > getsockname(3, {sa_family=3DAF_NETLINK, pid=3D3147, groups=3D0000ffff},=
[12]) =3D 0
> > time(NULL) =3D 1134052385
> > sendto(3, "\24\0\0\0\36\0\1\3\0\0\0\0\0\0\0\0\3\0\0\0", 20, 0,
> > {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 20
> > recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0,
> > groups=3D00000000},
> > msg_iov(1)=3D[{"\24\0\0\0\3\0\2\0\0\0\0\0K\f\0\0\0\0\0\0\0\0\0\0\0\0\0"=
...,
> > 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 20
> > recvmsg(3,
> >=20
> >=20
> > debug log:
> >=20
> > Dec 8 09:33:05 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:217:genl_mpls_ilm_dump: Enter: entry 0
> > Dec 8 09:33:05 beedril kernel: MPLS DEBUG
> > net/mpls/mpls_netlink.c:235:genl_mpls_ilm_dump: Exit: entry 0
> >=20
> >=20
> > --
> > -Bob
>=20
> --=20
> James R. Leu
> jl...@mi...
--=20
James R. Leu
jl...@mi...
|
|
From: Joan R. <jr...@sa...> - 2005-12-12 18:42:53
|
Hi all, I've been able to successfully build latests versions of: * mpls-kernel-1.1 * iproute2-mpls-1.1 * ebtables-mpls But, on the other hand i've been unable to build ldp-portable/quagga-mpls obtained from perforce. I've followed these steps: * Downloaded ldp-portable and quagga-mpls from the perforce repository * Modified and run the create-links script in the ldpd * Configured quagga-mpls using : ./configure --enable-user=root --enable-group=root * Tried to build with make and obtained the following error: ----------------------------------- In file included from ospf_lsdb.c:29: ../ospfd/ospfd.h:510: error: array type has incomplete element type ../ospfd/ospfd.h:511: error: array type has incomplete element type ../ospfd/ospfd.h:512: error: array type has incomplete element type ../ospfd/ospfd.h:513: error: array type has incomplete element type ../ospfd/ospfd.h:514: error: array type has incomplete element type ../ospfd/ospfd.h:515: error: array type has incomplete element type make[2]: *** [ospf_lsdb.lo] Error 1 make[2]: Leaving directory `/root/devel/quagga-mpls/ospfd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/devel/quagga-mpls' make: *** [all] Error 2 -------------------------------------- the lines in the ospfd.h file that cause the error are: --------------------------------------- extern struct message ospf_ism_state_msg[]; extern struct message ospf_nsm_state_msg[]; extern struct message ospf_lsa_type_msg[]; extern struct message ospf_link_state_id_type_msg[]; extern struct message ospf_redistributed_proto[]; extern struct message ospf_network_type_msg[]; ---------------------------------------- Any idea? |
|
From: James R. L. <jl...@mi...> - 2005-12-12 16:06:11
|
On Mon, Dec 12, 2005 at 04:53:59PM +0100, Joan Ruiz wrote: > =20 > Hi all, >=20 > I figure out that the latest version of quagga with mpls support in the > Perforce repository is quagga-mpls / ldp-portable. Isn't it? > Are you currently working on that (i see that the last changes were made = on > july)? I have not made any changes to quagga-mpls/ldp-portable since july. > I wonder if quagga-mpls is ready to be built with the latest kernel heade= rs. > Have you tried to build it lately? No. > Joan. --=20 James R. Leu jl...@mi... |
533 messages has been excluded from this view by a project administrator.
