Thread: [mpls-linux-general] (no subject) (Page 2)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: anish v. <ani...@re...> - 2002-03-22 09:11:50
|
hi,
i am working on MPLS regarding that i want to open a file from
kernel to store ip address of the destination of forwarded pkt..
for which i am using the code below in mpls_ouput function ..
char *buffer = kmalloc(4096,GFP_KERNEL);
oldfs = get_fs();
set_fs(KERNEL_DS);
fd=open("/dev/test",O_RDWR,0);
if(fd){
read(fd,buffer,BUFFSIZE);
}
close(fd);
set_fs(oldfs);
but as soon as i ping another m/c my PC hangs..
can u please tell what is wrong with the above code..
whether i should use some lock... or is there any other method of
opening a file from kernel
thanx in advance
anish
|
|
From: James R. L. <jl...@mi...> - 2002-03-22 15:59:29
|
I have never tried to do this. Why do you want to?
Jim
On Fri, Mar 22, 2002 at 09:06:30AM -0000, anish verma wrote:
> hi,
> i am working on MPLS regarding that i want to open a file from=20
> kernel to store ip address of the destination of forwarded pkt..
> for which i am using the code below in mpls_ouput function ..
>=20
> char *buffer =3D kmalloc(4096,GFP_KERNEL);
> oldfs =3D get_fs();
> set_fs(KERNEL_DS);
> fd=3Dopen("/dev/test",O_RDWR,0);
> if(fd){
> =A0 read(fd,buffer,BUFFSIZE);
> }
> close(fd);
> set_fs(oldfs);
>=20
> but as soon as i ping another m/c my PC hangs..
> can u please tell what is wrong with the above code..
> whether i should use some lock... or is there any other method of=20
> opening a file from kernel
> thanx in advance
> anish
>=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
--=20
James R. Leu
|
|
From: anish v. <ani...@re...> - 2002-03-28 08:26:46
|
hi jim, i am using the latest ldp from CVS.. ------- ------------ |router 1| | router3 | -------- ---------- eth0 7.2\ / 9.3 eth0 \ / \ eth1 / eth0 7.3 --------- 9.2 / |router 2 |----- --------- all ip 192.168.* configuration router 1 ---------- mplsadm -L eth0:0 add respective routes m/c can ping each other ./ldp_linux add global 192.168.7.2 add interface eth0 router 2 ---------- mplsadm -L eth0:0 mplsadm -L eth1:0 add respective routes m/c can ping each other ./ldp_linux add global 192.168.7.3 add interface eth0 add interface eth1 router 3 ----------- mplsadm -L eth0:0 add respective routes m/c can ping each other ./ldp_linux add global 192.168.9.3 add interface eth0 but after that entries for router1 is not there in router3 but entry for router2 is there. also after quitting from ldp_linux entries from router3 are all gone and also some entries of router2. sometimes my machine hang up if i quit from one of the machine in the network. i have one more query is it neccessary to give diffrent ip address to all the ethernets in a single pc to get ldp working.. thanx in advace anish |
|
From: farahmand z. <z_c...@ya...> - 2002-04-27 09:12:59
|
Hi Jim, Thank you for your response,but I don't underestand what do you mean by do a allmulti,it's not a command!, how can I know that multicast is enabled on the interface? Thanks for your attention.do you have any other suggestion for this matter? I really need to solve this problem. Best regards, Zahra. --------------------------------- Do You Yahoo!? Yahoo! Health - your guide to health and wellness |
|
From: James R. L. <jl...@mi...> - 2002-04-29 00:19:16
|
ifconfig eth0 allmulti On Sat, Apr 27, 2002 at 02:12:59AM -0700, farahmand zahra wrote: > > Hi Jim, > > Thank you for your response,but I don't underestand what do you mean by do a allmulti,it's not a command!, how can I know that multicast is enabled on the interface? > > Thanks for your attention.do you have any other suggestion for this matter? > > I really need to solve this problem. > > Best regards, > > Zahra. > > > > --------------------------------- > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness -- James R. Leu |
|
From: Hariharan K. <hku...@ho...> - 2002-05-06 18:03:41
|
<html><div style='background-color:'><DIV>Hi , </DIV>
<DIV></DIV>We have patched the kernel for MPLS.
<DIV></DIV>The ldp-poprtable compiles with warnings(runs to one page...),but the ldp_linux gets created succesfully.
<DIV></DIV>{ Note : The Makefile in port directory has -DMPLS_LINUX enabled)
<DIV></DIV>
<DIV></DIV>The warnings generated during compilation of ldp_linux. <BR>Is this a known problem ?
<P> Also does the ldp-portable update the <STRONG>proc/net/mpls_* </STRONG>directories.... <BR>The ldp portable code does not contain any code-refernce to the proc directories. </P>Or am i missing something ?
<DIV></DIV>
<DIV></DIV>
<P>Any help will be greatly appreciated. </P>Thanks,
<DIV></DIV>Hari.</div><br clear=all><hr>MSN Photos is the easiest way to share and print your photos: <a href='http://g.msn.com/1HM103401/39'>Click Here</a><br></html>
|
|
From: senthil a. <mpl...@ya...> - 2002-06-16 03:46:48
|
U have requested for subscription to linuxmpls yahoo group.But,I am little reluctant to approve for two reasons: - you have a filter feature that will never allow the yahoo group mails . - this list is of low volume and doesnt have intersecting goals with sourceforge mpls linux list. If some one wants to subscribe ..they can join as individual members . thanks, -moderator ===== Ayyasamy Senthilkumar M.S.(Computer Networking) UMKC,MO. ----------------------------- An expert is a man who has made all the mistakes that can be made in a very narrow field. --Niels Bohr. __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: Sumeet A. <sum...@ho...> - 2002-06-29 22:52:38
|
To James and all who have had a problem of network card not getting detected (and knows a solution to it): A similar post was posted as "Re: network card 2002-03-07 04:58 ". I am trying to install mpls-linux 1.0 in my linux box-RH-2.4.18. I could add the patch and compile properly. My 'old kernel' still detects the network card (I have only 1), but when I boot in the new mpls kernel, my network card fails at boot time, with error 'Bringing up interface eth0: eth0 initialization delay [FAILED]'. And yes....I did do 1. 'make menuconfig' 2. "make dep; make clean; make bzImage; make modules; make modules_install" 3. Copy the new kernal image(bzImage) into /boot directory 4. Modify the /etc/lilo.conf file and run 'lilo' on command prompt. I got this piece of information from http://www.ibiblio.org/mdw/HOWTO/Kernel-HOWTO-2.html#ss2.4 which says: -------------------------------------- " If the kernel fails to load a module (say loadable module for network card or other devices), then you may want to try to build the driver for device right into the kernel. Sometimes loadable module will NOT work and the driver needs to be built right inside the kernel. For example - some network cards do not support loadable module feature - you MUST build the driver of the network card right into linux kernel. Hence, in 'make xconfig' you MUST not select loadable module for this device." -------------------------------------- I even disabled "Loadable module support" (based on information above), but could not get any favorable results. HELP NEEDED VERY BADLY!! Thank you -Sumeet. _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com |
|
From: Gilles N. <gno...@ee...> - 2002-09-17 11:37:16
|
|
From: deepak <dxb...@wi...> - 2003-02-14 21:31:02
|
hi all i have compiled and installed MPLS-linux now while testing i saw this problem i am using 2 PC's as my LSR's and when i gave these commands i got the following output i also have given the same key as i got in the mplsout file as shown below but im getting this error that either to is dupli............. when i give a ip route add commd also how do i test that the traffic is following the LSP if this works ofcrs root@localhost root]# cat /proc/net/mpls_out 0x00000004 0/0/0 1 PUSH(gen 17) SET(eth0,192.168.6.60) [root@localhost root]# ip route add 192.168.6.60/32 lsp 0x00000004 Error: either "to" is duplicate, or "lsp" is a garbage. |
|
From: Mattias P. <mat...@op...> - 2003-04-30 08:50:40
|
The following setup results in a segmentation fault of mplsd: .105 .106 .10 .9 X----10.1.0.104/29------A---10.7.2.8/29----B Router A is a Cisco 3620 and router B is a linux machine. Both run OSPF, BGP and MPLS. A and B are bgp peers. They are in the same BGP AS and in the same BGP and OSPF areas. Router X runs BGP. It is in another BGP AS and peers with router A. mplsd on B crashes when it receives some routes from the bgp protocol. I have traced the problem and it occurs because of the way bgp announces it routes: Router A tells router B that network 10.1.0.8/29 can be reached on nexthop 10.1.0.105. mplsd on Router B however, can not handle this because it does not have a direct connection to 10.1.0.105. This results in a seg fault in mplsd (if_handle is null for the nexthop). /Mattias Persson |
|
From: James R. L. <jl...@mi...> - 2003-05-06 03:46:13
|
What version of ldp-portable and can you get a stack trace or trace output from 'mplsd' Enable trace output: uml1-mpls# conf t uml1-mpls(config)# mpls ldp uml1-mpls(config-ldp)# tr uml1-mpls(config-ldp)# trace all uml1-mpls(config-ldp)# trace all uml1-mpls(config-ldp)# The tracing info is sent to standard out of the mplsd program (don't use -d and make sure to redirect the output someplace) Getting a stack trace: [jleu jleu-laptop 10:45pm] ~-> gdb /usr/sbin/mplsd core <snip> (gdb) where <stack trace> On Wed, Apr 30, 2003 at 10:49:43AM +0200, Mattias Persson wrote: > The following setup results in a segmentation fault of mplsd: > > .105 .106 .10 .9 > X----10.1.0.104/29------A---10.7.2.8/29----B > > Router A is a Cisco 3620 and router B is a linux machine. > Both run OSPF, BGP and MPLS. A and B are bgp peers. They are in the same > BGP AS and in the same BGP and OSPF areas. > > Router X runs BGP. It is in another BGP AS and peers with router A. > > mplsd on B crashes when it receives some routes from > the bgp protocol. I have traced the problem and it > occurs because of the way bgp announces it routes: > Router A tells router B that network 10.1.0.8/29 can be > reached on nexthop 10.1.0.105. mplsd on Router B > however, can not handle this because it > does not have a direct connection to 10.1.0.105. > > This results in a seg fault in mplsd (if_handle is null for the nexthop). > > /Mattias Persson > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
|
From: Fredrik P. <Fre...@op...> - 2003-05-06 09:17:38
|
I work on the same project as Mattias, and here are some more details.
On Tuesday 06 May 2003 07.36, James R. Leu wrote:
> What version of ldp-portable and can you get a stack trace or trace output
> from 'mplsd'
ldp-portable is version 0.310.
Zebra, ospfd and bgpd are all up and running. BGP is peering with a router
which does not redistribute the external routes in OSPF, the intention is to
distribute those by using BGP. When mplsd is started it will crash with the
following backtrace.
(gdb) bt
#0 0x0804c66b in mpls_zebra_read_ipv4 (command=7, client=0x80cf7d8,
length=22) at mpls_zebra.c:282
#1 0x0809caf7 in zclient_read (thread=0xbffffaa0) at zclient.c:867
#2 0x08095100 in thread_call (thread=0xbffffaa0) at thread.c:647
#3 0x0804cba7 in main (argc=3, argv=0xbffffb84) at mpls_main.c:223
#4 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
The segfault is from a debug print which tries to access a pointer without
checking to see if it is NULL. The simple fix is to add a check for NULL,
with the following patch.
--- mpls_zebra.c.orig Tue May 6 11:02:19 2003
+++ mpls_zebra.c Tue May 6 11:02:41 2003
@@ -279,7 +279,9 @@
zlog_info("\tnexthop %s", inet_ntoa(tmp));
}
if (nexthop.type & MPLS_NH_IF) {
- zlog_info("\tifindex %d", nexthop.if_handle->ifindex);
+ if (nexthop.if_handle != NULL) {
+ zlog_info("\tifindex %d", nexthop.if_handle->ifindex);
+ }
}
if (command == ZEBRA_IPV4_ROUTE_ADD) {
This allows mplsd to survive for several seconds longer, but it will segfault
again, with this stacktrace.
Program received signal SIGSEGV, Segmentation fault.
0x080839dd in mpls_nexthop_compare (nh1=0x81b05b0, nh2=0xbffff97c) at
mpls_compare.c:38
38 if ((retval = mpls_if_handle_compare(nh1->if_handle,
nh2->if_handle))) {
(gdb) bt
#0 0x080839dd in mpls_nexthop_compare (nh1=0x81b05b0, nh2=0xbffff97c) at
mpls_compare.c:38
#1 0x08049cf1 in mpls_fib_getnext_route (handle=0x80d1e08, dest=0xbffff960)
at impl_fib.c:154
#2 0x08069940 in ldp_label_mapping_initial_callback (timer=0x81fdff0,
extra=0x81f8dc8, handle=0x80d1ec8) at ldp_label_mapping.c:523
#3 0x0804b82c in mpls_timer (thread=0xbffffaa0) at impl_timer.c:28
#4 0x08095108 in thread_call (thread=0xbffffaa0) at thread.c:647
#5 0x0804cbaf in main (argc=3, argv=0xbffffb84) at mpls_main.c:223
#6 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) print nh1->if_handle
$8 = (struct interface *) 0x0
(gdb) print nh2->if_handle
$9 = (struct interface *) 0x0
I don't know if I would gain anything by fixing this segfault, even if it is
simple to check for NULL in mpls_nexthop_compare as well. The basic problem
seems to be that the if_handle should be something other than NULL. As
Mattias mentioned, the reason for the error is that BGP reports the gateway
for external routes to be an interface which the Linux machine is not
directly connected to. A possible fix is for mplsd to recognize this
situation and find the route towards the gateway, and use the interface
related to that route instead, but that is only a guess from my side. In the
image below which Mattias made, the mplsd at B should replace gateway
10.1.0.105 with 10.7.2.10. Let us know if there is any other information you
need.
/Fredrik Pettersson
> On Wed, Apr 30, 2003 at 10:49:43AM +0200, Mattias Persson wrote:
> > The following setup results in a segmentation fault of mplsd:
> >
> > .105 .106 .10 .9
> > X----10.1.0.104/29------A---10.7.2.8/29----B
> >
> > Router A is a Cisco 3620 and router B is a linux machine.
> > Both run OSPF, BGP and MPLS. A and B are bgp peers. They are in the same
> > BGP AS and in the same BGP and OSPF areas.
> >
> > Router X runs BGP. It is in another BGP AS and peers with router A.
> >
> > mplsd on B crashes when it receives some routes from
> > the bgp protocol. I have traced the problem and it
> > occurs because of the way bgp announces it routes:
> > Router A tells router B that network 10.1.0.8/29 can be
> > reached on nexthop 10.1.0.105. mplsd on Router B
> > however, can not handle this because it
> > does not have a direct connection to 10.1.0.105.
> >
> > This results in a seg fault in mplsd (if_handle is null for the nexthop).
> >
> > /Mattias Persson
--
Fredrik Pettersson (Fre...@op...)
Operax AB (www.operax.com)
Aurorum 8, 977 75 Luleå
+46 920 75502
|
|
From: James R. L. <jl...@mi...> - 2003-05-06 13:30:00
|
Excellent debugging. During my last re-write of the nexthop handling
I forgot yo take into consideration BGP routes whose nexthop is an
IP address which is not in a directly connected subnet. I should be able
to come up with a quick fix.
Are you using 'p4' to get access to my development tree? If so I can
just tell you when the fix is in and you can just sync your client
at that time.
On Tue, May 06, 2003 at 11:17:07AM +0200, Fredrik Pettersson wrote:
> I work on the same project as Mattias, and here are some more details.
>=20
> On Tuesday 06 May 2003 07.36, James R. Leu wrote:
> > What version of ldp-portable and can you get a stack trace or trace o=
utput
> > from 'mplsd'
>=20
> ldp-portable is version 0.310.
>=20
> Zebra, ospfd and bgpd are all up and running. BGP is peering with a rou=
ter=20
> which does not redistribute the external routes in OSPF, the intention =
is to=20
> distribute those by using BGP. When mplsd is started it will crash with=
the=20
> following backtrace.
>=20
> (gdb) bt
> #0 0x0804c66b in mpls_zebra_read_ipv4 (command=3D7, client=3D0x80cf7d8=
,=20
> length=3D22) at mpls_zebra.c:282
> #1 0x0809caf7 in zclient_read (thread=3D0xbffffaa0) at zclient.c:867
> #2 0x08095100 in thread_call (thread=3D0xbffffaa0) at thread.c:647
> #3 0x0804cba7 in main (argc=3D3, argv=3D0xbffffb84) at mpls_main.c:223
> #4 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
>=20
> The segfault is from a debug print which tries to access a pointer with=
out=20
> checking to see if it is NULL. The simple fix is to add a check for NUL=
L,=20
> with the following patch.
>=20
> --- mpls_zebra.c.orig Tue May 6 11:02:19 2003
> +++ mpls_zebra.c Tue May 6 11:02:41 2003
> @@ -279,7 +279,9 @@
> zlog_info("\tnexthop %s", inet_ntoa(tmp));
> }
> if (nexthop.type & MPLS_NH_IF) {
> - zlog_info("\tifindex %d", nexthop.if_handle->ifindex);
> + if (nexthop.if_handle !=3D NULL) {
> + zlog_info("\tifindex %d", nexthop.if_handle->ifindex);
> + }
> }
>=20
> if (command =3D=3D ZEBRA_IPV4_ROUTE_ADD) {
>=20
> This allows mplsd to survive for several seconds longer, but it will se=
gfault=20
> again, with this stacktrace.
>=20
> Program received signal SIGSEGV, Segmentation fault.
> 0x080839dd in mpls_nexthop_compare (nh1=3D0x81b05b0, nh2=3D0xbffff97c) =
at=20
> mpls_compare.c:38
> 38 if ((retval =3D mpls_if_handle_compare(nh1->if_handle,=20
> nh2->if_handle))) {
> (gdb) bt
> #0 0x080839dd in mpls_nexthop_compare (nh1=3D0x81b05b0, nh2=3D0xbffff9=
7c) at=20
> mpls_compare.c:38
> #1 0x08049cf1 in mpls_fib_getnext_route (handle=3D0x80d1e08, dest=3D0x=
bffff960)=20
> at impl_fib.c:154
> #2 0x08069940 in ldp_label_mapping_initial_callback (timer=3D0x81fdff0=
,=20
> extra=3D0x81f8dc8, handle=3D0x80d1ec8) at ldp_label_mapping.c:523
> #3 0x0804b82c in mpls_timer (thread=3D0xbffffaa0) at impl_timer.c:28
> #4 0x08095108 in thread_call (thread=3D0xbffffaa0) at thread.c:647
> #5 0x0804cbaf in main (argc=3D3, argv=3D0xbffffb84) at mpls_main.c:223
> #6 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
> (gdb) print nh1->if_handle
> $8 =3D (struct interface *) 0x0
> (gdb) print nh2->if_handle
> $9 =3D (struct interface *) 0x0
>=20
> I don't know if I would gain anything by fixing this segfault, even if =
it is=20
> simple to check for NULL in mpls_nexthop_compare as well. The basic pro=
blem=20
> seems to be that the if_handle should be something other than NULL. As=20
> Mattias mentioned, the reason for the error is that BGP reports the gat=
eway=20
> for external routes to be an interface which the Linux machine is not=20
> directly connected to. A possible fix is for mplsd to recognize this=20
> situation and find the route towards the gateway, and use the interface=
=20
> related to that route instead, but that is only a guess from my side. I=
n the=20
> image below which Mattias made, the mplsd at B should replace gateway=20
> 10.1.0.105 with 10.7.2.10. Let us know if there is any other informatio=
n you=20
> need.
>=20
> /Fredrik Pettersson
>=20
> > On Wed, Apr 30, 2003 at 10:49:43AM +0200, Mattias Persson wrote:
> > > The following setup results in a segmentation fault of mplsd:
> > >
> > > .105 .106 .10 .9
> > > X----10.1.0.104/29------A---10.7.2.8/29----B
> > >
> > > Router A is a Cisco 3620 and router B is a linux machine.
> > > Both run OSPF, BGP and MPLS. A and B are bgp peers. They are in the=
same
> > > BGP AS and in the same BGP and OSPF areas.
> > >
> > > Router X runs BGP. It is in another BGP AS and peers with router A.
> > >
> > > mplsd on B crashes when it receives some routes from
> > > the bgp protocol. I have traced the problem and it
> > > occurs because of the way bgp announces it routes:
> > > Router A tells router B that network 10.1.0.8/29 can be
> > > reached on nexthop 10.1.0.105. mplsd on Router B
> > > however, can not handle this because it
> > > does not have a direct connection to 10.1.0.105.
> > >
> > > This results in a seg fault in mplsd (if_handle is null for the nex=
thop).
> > >
> > > /Mattias Persson
>=20
> --=20
> Fredrik Pettersson (Fre...@op...)
> Operax AB (www.operax.com)
> Aurorum 8, 977 75 Lule=E5
> +46 920 75502
--=20
James R. Leu
|
|
From: Fredrik P. <Fre...@op...> - 2003-05-06 13:55:26
|
On Tuesday 06 May 2003 17.19, James R. Leu wrote: > Excellent debugging. During my last re-write of the nexthop handling > I forgot yo take into consideration BGP routes whose nexthop is an > IP address which is not in a directly connected subnet. I should be able > to come up with a quick fix. > > Are you using 'p4' to get access to my development tree? If so I can > just tell you when the fix is in and you can just sync your client > at that time. p4 seems quite easy to use, let us know when there is a fix available and we will test it. Thanks for the quick reply. -- Fredrik Pettersson (Fre...@op...) Operax AB (www.operax.com) Aurorum 8, 977 75 Luleå +46 920 75502 |
|
From: <bi...@so...> - 2003-05-12 01:57:20
|
Ｎow I am running zebra and mplsd on two virtual machines,the virtual machines software is vmware workstation 4.004. The IP address is 172.26.12.148 and 172.26.12.151.
I use Linux-2.4.18-14、mpls-linux-1.172、zebra-0.93a、ldp-portable-0.305。
And the enviroment is:
Zebra -P 1000 -d
Bgpd -P 1001 -d
Mplsd -P 1002
First problem:
When do as follows:
Telnet 172.26.12.148 1002
The output is as follows:
Hello, this is zebra (version 0.93a).
Copyright 1996-2002 Kunihiro Ishiguro.
User Access Verification
Password:
Ldp1>
Ldp1> show ldp
LSR-ID: ac1a0c97 Admin State: ENABLED
Transport Address: 00000000
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
Ldp1> show ldp neighbor
Peer LDP Ident: 172.26.12.148:0; Local LDP Ident: 172.26.12.151:0
TCP connection: n/a
State: OPERATIONAL; Msgs sent/recv: 1370/1369; UNSOLICITED
Up time: n/a
LDP discovery sources:
eth0
Addresses bound to peer:
172.26.12.148
Ldp1> show mpls forward
Insegments:
Lbl Spc Label Owner
0 10001 LDP
Total 1
Outsegments:
Total 0
Cross Connects:
Total 0
Ldp1>
Ldp1> show ldp database
172.26.0.0/16 local binding: label: gen 10001
172.26.0.0/16 remote binding: no outlabel lsr: 172.26.12.148:0
why no outsegments?
Second problem :
This problem is about mplsadm when I want to manually set up labels.
#mplsadm -L eth0:0
Label Space:Invalid argument
#mplsadm -A -O 0
Key:0x00000000
Out Segment add:Invalid argument
And there’s no file named mpls_out in the directory /proc/net
It seemed that I cannot use mplsadm.what’s the problem?
Can you give me some suggestions?
|
|
From: James R. L. <jl...@mi...> - 2003-05-14 15:47:49
|
Did you turn on ospf? Is OSPF propogating reachbility info about the router-id? On Mon, May 12, 2003 at 09:57:12AM +0800, bi...@so... wrote: > =A3=CEow I am running zebra and mplsd on two virtual machines,the virtu= al machines software is vmware workstation 4.004. The IP address is 172.2= 6.12.148 and 172.26.12.151. > I use Linux-2.4.18-14=A1=A2mpls-linux-1.172=A1=A2zebra-0.93a=A1=A2ldp-p= ortable-0.305=A1=A3 > And the enviroment is: > Zebra -P 1000 -d > Bgpd -P 1001 -d > Mplsd -P 1002 >=20 > First problem: > When do as follows: > Telnet 172.26.12.148 1002 >=20 > The output is as follows: > Hello, this is zebra (version 0.93a). > Copyright 1996-2002 Kunihiro Ishiguro. >=20 > User Access Verification >=20 > Password: > Ldp1> > Ldp1> show ldp > LSR-ID: ac1a0c97 Admin State: ENABLED > Transport Address: 00000000 > 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 > Ldp1> show ldp neighbor > Peer LDP Ident: 172.26.12.148:0; Local LDP Ident: 172.26.12.151:0 > TCP connection: n/a > State: OPERATIONAL; Msgs sent/recv: 1370/1369; UNSOLICITED > Up time: n/a > LDP discovery sources: > eth0 > Addresses bound to peer: > 172.26.12.148 >=20 > Ldp1> show mpls forward > Insegments: > Lbl Spc Label Owner > 0 10001 LDP > Total 1 >=20 > Outsegments: >=20 > Total 0 >=20 > Cross Connects: >=20 > Total 0 >=20 > Ldp1> > Ldp1> show ldp database > 172.26.0.0/16 local binding: label: gen 10001 > 172.26.0.0/16 remote binding: no outlabel lsr: 172.26.12.148:0 >=20 > why no outsegments? >=20 > Second problem : > This problem is about mplsadm when I want to manually set up labels. > #mplsadm -L eth0:0 > Label Space:Invalid argument > #mplsadm -A -O 0 > Key:0x00000000 > Out Segment add:Invalid argument > And there=A1=AFs no file named mpls_out in the directory /proc/net > It seemed that I cannot use mplsadm.what=A1=AFs the problem? > Can you give me some suggestions? > =20 > =20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solution= s > www.enterpriselinuxforum.com >=20 > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu |
|
From: <bi...@so...> - 2003-05-12 01:57:32
|
Ｎow I am running zebra and mplsd on two virtual machines,the virtual machines software is vmware workstation 4.004. The IP address is 172.26.12.148 and 172.26.12.151.
I use Linux-2.4.18-14、mpls-linux-1.172、zebra-0.93a、ldp-portable-0.305。
And the enviroment is:
Zebra -P 1000 -d
Bgpd -P 1001 -d
Mplsd -P 1002
First problem:
When do as follows:
Telnet 172.26.12.148 1002
The output is as follows:
Hello, this is zebra (version 0.93a).
Copyright 1996-2002 Kunihiro Ishiguro.
User Access Verification
Password:
Ldp1>
Ldp1> show ldp
LSR-ID: ac1a0c97 Admin State: ENABLED
Transport Address: 00000000
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
Ldp1> show ldp neighbor
Peer LDP Ident: 172.26.12.148:0; Local LDP Ident: 172.26.12.151:0
TCP connection: n/a
State: OPERATIONAL; Msgs sent/recv: 1370/1369; UNSOLICITED
Up time: n/a
LDP discovery sources:
eth0
Addresses bound to peer:
172.26.12.148
Ldp1> show mpls forward
Insegments:
Lbl Spc Label Owner
0 10001 LDP
Total 1
Outsegments:
Total 0
Cross Connects:
Total 0
Ldp1>
Ldp1> show ldp database
172.26.0.0/16 local binding: label: gen 10001
172.26.0.0/16 remote binding: no outlabel lsr: 172.26.12.148:0
why no outsegments?
Second problem :
This problem is about mplsadm when I want to manually set up labels.
#mplsadm -L eth0:0
Label Space:Invalid argument
#mplsadm -A -O 0
Key:0x00000000
Out Segment add:Invalid argument
And there’s no file named mpls_out in the directory /proc/net
It seemed that I cannot use mplsadm.what’s the problem?
Can you give me some suggestions?
|
|
From: James R. L. <jl...@mi...> - 2003-05-14 15:50:33
|
>=20 > Second problem : > This problem is about mplsadm when I want to manually set up labels. > #mplsadm -L eth0:0 > Label Space:Invalid argument > #mplsadm -A -O 0 > Key:0x00000000 > Out Segment add:Invalid argument > And there=A1=AFs no file named mpls_out in the directory /proc/net > It seemed that I cannot use mplsadm.what=A1=AFs the problem? > Can you give me some suggestions? You are not running an MPLS enabled kernel. YOu can grab a redhat 8.0 RPM with a MPLS enabled kernel from: http://sf.net/projects/mpls-linux/ in the files section > =20 > =20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solution= s > www.enterpriselinuxforum.com >=20 > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu |
|
From: a a <dre...@ho...> - 2003-05-26 16:57:53
|
Hi! There is a bug when patching the dst.c file... patching file net/core/dst.c Hunk #1 succeeded at 18 (offset -1 lines). Hunk #2 FAILED at 161. 1 out of 2 hunks FAILED -- saving rejects to file net/core/dst.c.rej patching file net/core/neighbour.c patching file net/ipv4/af_inet.c patching file net/ipv4/fib_semantics.c It's easy to fix, just thought you would like to know... //Andreas Westling _________________________________________________________________ Hitta rätt på nätet med MSN Sök http://search.msn.se/ |
|
From: James R. L. <jl...@mi...> - 2003-05-27 13:33:56
|
Which version of the kernel are you patching? On Mon, May 26, 2003 at 06:57:47PM +0200, a a wrote: > Hi! >=20 > There is a bug when patching the dst.c file... >=20 > patching file net/core/dst.c > Hunk #1 succeeded at 18 (offset -1 lines). > Hunk #2 FAILED at 161. > 1 out of 2 hunks FAILED -- saving rejects to file net/core/dst.c.rej > patching file net/core/neighbour.c > patching file net/ipv4/af_inet.c > patching file net/ipv4/fib_semantics.c >=20 > It's easy to fix, just thought you would like to know... >=20 > //Andreas Westling >=20 > _________________________________________________________________ > Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/ >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu |
|
From: a a <dre...@ho...> - 2003-06-17 11:44:34
|
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? Sincerly, Drew _________________________________________________________________ Hitta rätt på nätet med MSN Sök http://search.msn.se/ |
|
From: James R. L. <jl...@mi...> - 2003-06-17 14:08:01
|
On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote:
> Hi again!
>=20
> How do I use the labels given by the zebra-ldp? I have investigated som=
e=20
> 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.
>=20
> Sincerly,
> Drew
>=20
> _________________________________________________________________
> Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/
>=20
>=20
>=20
> -------------------------------------------------------
> 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
--=20
James R. Leu
|
|
From: Saeed S. <sbs...@ci...> - 2003-10-12 08:50:13
|
|
From: <lis...@op...> - 2003-11-14 06:06:18
|
您好!
我是“呜哩嘛哩卡通大集合”店的小店主。小店新开张，东西不多，但价钱优惠。零售带批发的。
来看看吧。不买没关系。生意不做还可以做朋友的。
请点击http://www.eachnet.com/fu/shop/myshop.php?user_id=10984029
：）笑脸相迎哦！！
呜哩嘛哩敬上
<<---以上邮件内容与中资源网络及软件开发商无关--->>
-----------------------------------------------
中资源网络--域名先注册后付款;主机先开通后收费。
申请100M虚拟主机350元/年，送国际域名+5个信箱
http://www.263nic.com/
-----------------------------------------------
欢迎使用亿虎Email系列软件
下载地址: http://www.ehoosoft.com
定向邮箱搜索: 亿虎Email搜索大师
邮件群发特快: 亿虎Email邮差
病毒邮件克星: 亿虎Email安全大师
......
|
×
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