Thread: [mpls-linux-devel] New MPLS-Linux code
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel
|
From: <gsr...@al...> - 2007-02-12 10:05:54
|
Hi James! Now that I've finished my exams I wish to take up working with your = MPLS-Linux project. I had some problems with the software from your = repository. If you could remember I work with FC4 and teh following = RPMs: [root@PE2 ~]# rpm -qa | grep mpls iproute-2.6.11-1_mpls_90.1162552079 quagga-0.99.6-2007010801_mpls_0.1168246002 iptables-1.3.0-2_mpls_1.950d kernel-2.6.15-1.1831_FC4mpls_1.950 glibc-kernheaders-3.0-5.2_mpls0.1162999872 quagga-devel-0.99.6-2007010801_mpls_0.1168246002 quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 kernel-devel-2.6.15-1.1831_FC4mpls_1.950 quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 Now that you have released new versions at Source Forge I wonder if I = should keep on working with my current scenario or begin even installing = the new kernel. However, it seems that the new kernel RPMs are only for = AMD64 while I have Intel(R) Pentium(R) D CPU 3.00GHz. I've only seen one = kernel RPM for "none" architecture but none kernel .src.rpm to get the = source code. What should I do? Thanks in advance, Gonzalo. |
|
From: James R. L. <jl...@mi...> - 2007-02-12 13:43:27
|
The AMD classification is incorrrect. I will fix this. On Mon, Feb 12, 2007 at 11:03:12AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James! >=20 > Now that I've finished my exams I wish to take up working with your MPLS-= Linux project. I had some problems with the software from your repository. = If you could remember I work with FC4 and teh following RPMs: >=20 > [root@PE2 ~]# rpm -qa | grep mpls > iproute-2.6.11-1_mpls_90.1162552079 > quagga-0.99.6-2007010801_mpls_0.1168246002 > iptables-1.3.0-2_mpls_1.950d > kernel-2.6.15-1.1831_FC4mpls_1.950 > glibc-kernheaders-3.0-5.2_mpls0.1162999872 > quagga-devel-0.99.6-2007010801_mpls_0.1168246002 > quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 > kernel-devel-2.6.15-1.1831_FC4mpls_1.950 > quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 >=20 > Now that you have released new versions at Source Forge I wonder if I sho= uld keep on working with my current scenario or begin even installing the n= ew kernel. However, it seems that the new kernel RPMs are only for AMD64 wh= ile I have Intel(R) Pentium(R) D CPU 3.00GHz. I've only seen one kernel RPM= for "none" architecture but none kernel .src.rpm to get the source code. W= hat should I do? >=20 > Thanks in advance, >=20 > Gonzalo. >=20 > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-08 11:24:16
|
Hi James!
I've just installed FC5 and all the MPLS-Linux-1.955 RPMs for this OS:
[root@PE1 ~]# rpm -qa | grep mpls | sort
ebtables-2.0.8-0.6.rc2.fc5.mpls.1.955
glibc-kernheaders-3.0-5.2.fc5.mpls.1.955
iproute-2.6.16-1.fc5.mpls.1.955
iptables-1.3.5-1.2.fc5.mpls.1.955
kernel-devel-2.6.18-1.2257.fc5.mpls.1.955
kernel-smp-2.6.18-1.2257.fc5.mpls.1.955
kernel-smp-devel-2.6.18-1.2257.fc5.mpls.1.955
quagga-0.99.6-01.fc5.mpls.1.955
[root@PE1 ~]# lsmod | grep mpls
mpls4 10240 0
I try a simple environment with 2 LSRs:
=20
eth0 eth1 eth1 eth0
12.0.0.1-------PE1---------------------PE2-------172.29.17.60
.1 10.0.0.0/24 .2
This is the configuration I made on PE1 by vtysh:
PE1# sh run
Building configuration...
Current configuration:
!
hostname PE1
!
password root
enable password root
!
interface eth0
ipv6 nd suppress-ra
!
interface eth1
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
ip forwarding
!
line vty
!
And the outputs of the commands relative to LDP:
PE1# sh ldp
LSR-ID: 12.0.0.1 Admin State: ENABLED
Transport Address: 0.0.0.0
Control Mode: ORDERED Repair Mode: GLOBAL
Propogate Release: TRUE Label Merge: TRUE
Retention Mode: LIBERAL Loop Detection Mode: NONE
TTL-less-domain: FALSE
Local TCP Port: 646 Local UDP Port: 646
Keep-alive Time: 45 Keep-alive Interval: 15
Hello Time: 15 Hello Interval: 5
PE1# sh ldp data
10.0.0.0/24 local binding: label: gen 10002
10.0.0.0/24 remote binding: no outlabel lsr: 10.0.0.2:0
172.29.16.0/22 remote binding: no outlabel lsr: 10.0.0.2:0
PE1# sh ldp dis
Local LSR Identifier: 12.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 10.0.0.2:0
Targeted Discovery Sources:
No configured peers
PE1# sh ldp fec
FEC: 1 10.0.0.0/24
1 0.0.0.0 1
FEC: 4 172.29.16.0/22
PE1# sh ldp neigh
Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0
TCP connection: 10.0.0.1.34306 - 10.0.0.2.36479
State: OPERATIONAL; Msgs sent/recv: 63/191; UNSOLICITED
Up time: 00:14:38
LDP discovery sources:
eth1
Addresses bound to peer:
172.29.17.60 10.0.0.2
PE1# sh ldp ses
4 10.0.0.2 45 OPERATIONAL
172.29.17.60
10.0.0.2
PE1# sh mpls har
MPLS-Linux: 1.955 netlink control
[root@PE1 ~]# mpls nhlfe
[root@PE1 ~]# mpls ilm
ILM entry label gen 10002 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
What I want to do is to send labelled packets while they are crossing =
10.0.0.0/24. The problem is that LDP doesn't associate the labels that =
are discovered to the routes.
Where could I look at?
Thanks,
Gonzalo.
|
|
From: James R. L. <jl...@mi...> - 2007-03-09 05:08:06
|
Please include the output of: sho ip route from vtysh and: ip route show from the command line. On Thu, Mar 08, 2007 at 12:20:43PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James! >=20 > I've just installed FC5 and all the MPLS-Linux-1.955 RPMs for this OS: >=20 > [root@PE1 ~]# rpm -qa | grep mpls | sort > ebtables-2.0.8-0.6.rc2.fc5.mpls.1.955 > glibc-kernheaders-3.0-5.2.fc5.mpls.1.955 > iproute-2.6.16-1.fc5.mpls.1.955 > iptables-1.3.5-1.2.fc5.mpls.1.955 > kernel-devel-2.6.18-1.2257.fc5.mpls.1.955 > kernel-smp-2.6.18-1.2257.fc5.mpls.1.955 > kernel-smp-devel-2.6.18-1.2257.fc5.mpls.1.955 > quagga-0.99.6-01.fc5.mpls.1.955 >=20 > [root@PE1 ~]# lsmod | grep mpls > mpls4 10240 0 >=20 > I try a simple environment with 2 LSRs: > =20 > eth0 eth1 eth1 eth0 > 12.0.0.1-------PE1---------------------PE2-------172.29.17.60 > .1 10.0.0.0/24 .2 >=20 > This is the configuration I made on PE1 by vtysh: >=20 > PE1# sh run > Building configuration... >=20 > Current configuration: > ! > hostname PE1 > ! > password root > enable password root > ! > interface eth0 > ipv6 nd suppress-ra > ! > interface eth1 > ipv6 nd suppress-ra > mpls ip > mpls labelspace 0 > ! > interface lo > ! > interface sit0 > ipv6 nd suppress-ra > ! > mpls ldp > egress connected > ! > ip forwarding > ! > line vty > ! >=20 > And the outputs of the commands relative to LDP: >=20 > PE1# sh ldp > LSR-ID: 12.0.0.1 Admin State: ENABLED > Transport Address: 0.0.0.0 > Control Mode: ORDERED Repair Mode: GLOBAL > Propogate Release: TRUE Label Merge: TRUE > Retention Mode: LIBERAL Loop Detection Mode: NONE > TTL-less-domain: FALSE > Local TCP Port: 646 Local UDP Port: 646 > Keep-alive Time: 45 Keep-alive Interval: 15 > Hello Time: 15 Hello Interval: 5 >=20 > PE1# sh ldp data > 10.0.0.0/24 local binding: label: gen 10002 > 10.0.0.0/24 remote binding: no outlabel lsr: 10.0.0.2:0 > 172.29.16.0/22 remote binding: no outlabel lsr: 10.0.0.2:0 > PE1# sh ldp dis >=20 > Local LSR Identifier: 12.0.0.1 >=20 > Interface Discovery Sources: > eth1: xmit/recv > LDP Id: 10.0.0.2:0 >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE1# sh ldp fec > FEC: 1 10.0.0.0/24 > 1 0.0.0.0 1 > FEC: 4 172.29.16.0/22 >=20 > PE1# sh ldp neigh > Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0 > TCP connection: 10.0.0.1.34306 - 10.0.0.2.36479 > State: OPERATIONAL; Msgs sent/recv: 63/191; UNSOLICITED > Up time: 00:14:38 > LDP discovery sources: > eth1 > Addresses bound to peer: > 172.29.17.60 10.0.0.2 >=20 > PE1# sh ldp ses > 4 10.0.0.2 45 OPERATIONAL > 172.29.17.60 > 10.0.0.2 >=20 > PE1# sh mpls har > MPLS-Linux: 1.955 netlink control >=20 > [root@PE1 ~]# mpls nhlfe > [root@PE1 ~]# mpls ilm > ILM entry label gen 10002 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) >=20 > What I want to do is to send labelled packets while they are crossing 10.= 0.0.0/24. The problem is that LDP doesn't associate the labels that are dis= covered to the routes. >=20 > Where could I look at? >=20 > Thanks, >=20 > Gonzalo. >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
×
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