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

[mpls-linux-general] Utility compilation problem

[Nanda, D. <DN...@ne...>]

Hi James,
I downloaded the latest version of mpls (mpls-linux-0.700.tar.gz ) .I am
using Red Hat Linux 7.0 and Kernel 2.4.0 test11 .
I patched linux kernel 2.4.0 test 11 with the patch file provided and
compiled it . It compiled fine and I am able to boot with the mpls enabled
kernel .
But while compiling the user space application , the utilities, with the new
kernel , I get a compilation error

cc -g -Wall   -c -o netlink.o netlink.c
netlink.c:9:24: linux/mpls.h: No such file or directory
make: *** [netlink.o] Error 1

Then I put a copy of "mpls.h" in the local directory and changed the
inclusions accordingly in netlink.c and mplsadm.c .

The compiler shouted with the following errors ..

cc -g -Wall   -c -o mplsadm.o mplsadm.c
mplsadm.c: In function `main':
mplsadm.c:355: `RTM_DELILM' undeclared (first use in this function)
mplsadm.c:355: (Each undeclared identifier is reported only once
mplsadm.c:355: for each function it appears in.)
mplsadm.c:358: `RTM_NEWILM' undeclared (first use in this function)
mplsadm.c:374: `RTM_DELNHLFE' undeclared (first use in this function)
mplsadm.c:381: `RTM_NEWNHLFE' undeclared (first use in this function)
mplsadm.c:415: `RTM_NEWFTN' undeclared (first use in this function)
mplsadm.c:418: `RTM_DELFTN' undeclared (first use in this function)
mplsadm.c:432: `RTM_SETININSTR' undeclared (first use in this function)
mplsadm.c:447: `RTM_SETOUTINSTR' undeclared (first use in this function)
mplsadm.c:483: `RTM_NEWXC' undeclared (first use in this function)
mplsadm.c:486: `RTM_DELXC' undeclared (first use in this function)
make: *** [mplsadm.o] Error 1



Please help.

Regards
Debasis

RE: [mpls-linux-general] MPLS+Diffserv patches and kernel 2.4.0

[Jonathan E. <je...@no...>]

Hi Steven,

I'll look forward to that.  This week I encountered a kernel oops in
2.4.0-test9 (ksymoops points out rt_set_nexthop as the offending function)
under moderately heavy traffic loads, which is what I'm hoping is fixed by
later MPLS and kernel revisions.

Cheers!
Jon

> I was thinking to get them ready by last monday, but there 
> still seems to
> be a small but nasty bug in it. Since i'm having full time 
> meetings next
> week, it will probably be delayed untill after that 
> (although, i'm still
> trying to get a linux portable, in order to get some work 
> done during the
> meetings).
> 
> Anyway, you'll be hearing from me soon.
> 
> Cheers,
> Steven
> 
> Jonathan Earle wrote:
> 
> > Hi Jim,
> >
> > Do you know if Steven Van den Berghe's mpls+diffserv 
> patches have been
> > updated to post test9 (preferably release 2.4.0) kernels?

Re: [mpls-linux-general] MPLS+Diffserv patches and kernel 2.4.0

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

Well Jonathan,

I was thinking to get them ready by last monday, but there still seems to
be a small but nasty bug in it. Since i'm having full time meetings next
week, it will probably be delayed untill after that (although, i'm still
trying to get a linux portable, in order to get some work done during the
meetings).

Anyway, you'll be hearing from me soon.

Cheers,
Steven

Jonathan Earle wrote:

> Hi Jim,
>
> Do you know if Steven Van den Berghe's mpls+diffserv patches have been
> updated to post test9 (preferably release 2.4.0) kernels?
>
> Cheers!
> Jon
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

[mpls-linux-general] MPLS+Diffserv patches and kernel 2.4.0

[Jonathan E. <je...@no...>]

Hi Jim, 

Do you know if Steven Van den Berghe's mpls+diffserv patches have been
updated to post test9 (preferably release 2.4.0) kernels?

Cheers!
Jon

Re: [mpls-linux-general] Re: [MPLS-Linux] any backports?

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

Hello,

On Wed, Jan 17, 2001 at 03:01:13PM +0100, yal wrote:
> 
> 
> > Has anyone to your knowledge backported your mpls stuff to a
> > 2.2.x kernel?
> 
> Hello Chip,
> I tried to port mpls to kernel 2.2.17 some month ago, so
> if you are interested in it I'll send you patch.
> 
> A month ago I sent the same patch to Jim with petition
> to put it in yours ftp site, but probably my letter was loosed.

I must have deleted it by accident, because I do not have th patch.
If you re-send it I'll post it to the ftp site, eventually integrate
it into the mpls-linux package.

Jim

-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] any backports?

[yal <ya...@iw...>]

> Has anyone to your knowledge backported your mpls stuff to a
> 2.2.x kernel?

Hello Chip,
I tried to port mpls to kernel 2.2.17 some month ago, so
if you are interested in it I'll send you patch.

A month ago I sent the same patch to Jim with petition
to put it in yours ftp site, but probably my letter was loosed.

Jordan.

[mpls-linux-general] Re: [MPLS-Linux] any backports?

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

On Tue, Jan 16, 2001 at 04:54:47PM -0000, Chip Rodden wrote:
> James,
> 
> Has anyone to your knowledge backported your mpls stuff to a
> 2.2.x kernel?

I think I heard of one person trying to backport it, but nothing ever came
of it.

If your interested in giving it a try, I can try to answer any questions for
you.

Jim

BTW mpl...@li... is the new mailing list.
http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
-- 
James R. Leu

Re: [mpls-linux-general] Compilation errors in mplsadm 0.700

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

Hello Tom,

All of the following errors are about structes and defines that are inclu=
ded
in the kernel patch.  Did you patch the kernel?  Beyond just patching it =
will
need to configure the kernel and turn on the MPLS features before mplsadm
will compile cleanly.

Jim

On Tue, Jan 16, 2001 at 01:14:27PM +0000, Tom wrote:
> Hi!
>=20
> I=B4ve got a little problem here in compiling mplsadm 0.700. Compilatio=
n
> of netlink.c works fine, but in mplsadm.c I got a few compiler errors:
>=20
> In file included from mplsadm.c:19:
> netlink.h:6: warning: `struct mpls_out_label_req' declared inside
> parameter list
> netlink.h:6: warning: its scope is only this definition or declaration,
> which is probably not what you want.
> netlink.h:7: warning: `struct mpls_in_label_req' declared inside
> parameter list
> netlink.h:8: warning: `struct mpls_bind_fec_req' declared inside
> parameter list
> netlink.h:9: warning: `struct mpls_xconnect_req' declared inside
> parameter list
> netlink.h:10: warning: `struct mpls_instruction_req' declared inside
> parameter list
> mplsadm.c: In function `main':
> mplsadm.c:538: `RTM_DELILM' undeclared (first use in this function)
> mplsadm.c:538: (Each undeclared identifier is reported only once
> mplsadm.c:538: for each function it appears in.)
> mplsadm.c:538: warning: passing arg 2 of `send_ilm' from incompatible
> pointer type
> mplsadm.c:541: `RTM_NEWILM' undeclared (first use in this function)
> mplsadm.c:541: warning: passing arg 2 of `send_ilm' from incompatible
> pointer type
> mplsadm.c:557: `RTM_DELNHLFE' undeclared (first use in this function)
> mplsadm.c:557: warning: passing arg 2 of `send_nhlfe' from incompatible
> pointer type
> mplsadm.c:564: `RTM_NEWNHLFE' undeclared (first use in this function)
> mplsadm.c:564: warning: passing arg 2 of `send_nhlfe' from incompatible
> pointer type
> mplsadm.c:598: `RTM_NEWFTN' undeclared (first use in this function)
> mplsadm.c:598: warning: passing arg 2 of `send_ftn' from incompatible
> pointer type
> mplsadm.c:601: `RTM_DELFTN' undeclared (first use in this function)
> mplsadm.c:601: warning: passing arg 2 of `send_ftn' from incompatible
> pointer type
> mplsadm.c:615: `RTM_SETININSTR' undeclared (first use in this function)
> mplsadm.c:615: warning: passing arg 2 of `send_instr' from incompatible
> pointer type
> mplsadm.c:630: `RTM_SETOUTINSTR' undeclared (first use in this function=
)
>=20
> mplsadm.c:630: warning: passing arg 2 of `send_instr' from incompatible
> pointer type
> mplsadm.c:666: `RTM_NEWXC' undeclared (first use in this function)
> mplsadm.c:666: warning: passing arg 2 of `send_xc' from incompatible
> pointer type
> mplsadm.c:669: `RTM_DELXC' undeclared (first use in this function)
> mplsadm.c:669: warning: passing arg 2 of `send_xc' from incompatible
> pointer type
> make: *** [mplsadm.o] Error 1
>=20
> I hope someone can help me out with this. Thanx a lot.
>=20
> bye,
> tom
>=20
>=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

[mpls-linux-general] Compilation errors in mplsadm 0.700

[Tom <to...@gm...>]

Hi!

I=B4ve got a little problem here in compiling mplsadm 0.700. Compilation
of netlink.c works fine, but in mplsadm.c I got a few compiler errors:

In file included from mplsadm.c:19:
netlink.h:6: warning: `struct mpls_out_label_req' declared inside
parameter list
netlink.h:6: warning: its scope is only this definition or declaration,
which is probably not what you want.
netlink.h:7: warning: `struct mpls_in_label_req' declared inside
parameter list
netlink.h:8: warning: `struct mpls_bind_fec_req' declared inside
parameter list
netlink.h:9: warning: `struct mpls_xconnect_req' declared inside
parameter list
netlink.h:10: warning: `struct mpls_instruction_req' declared inside
parameter list
mplsadm.c: In function `main':
mplsadm.c:538: `RTM_DELILM' undeclared (first use in this function)
mplsadm.c:538: (Each undeclared identifier is reported only once
mplsadm.c:538: for each function it appears in.)
mplsadm.c:538: warning: passing arg 2 of `send_ilm' from incompatible
pointer type
mplsadm.c:541: `RTM_NEWILM' undeclared (first use in this function)
mplsadm.c:541: warning: passing arg 2 of `send_ilm' from incompatible
pointer type
mplsadm.c:557: `RTM_DELNHLFE' undeclared (first use in this function)
mplsadm.c:557: warning: passing arg 2 of `send_nhlfe' from incompatible
pointer type
mplsadm.c:564: `RTM_NEWNHLFE' undeclared (first use in this function)
mplsadm.c:564: warning: passing arg 2 of `send_nhlfe' from incompatible
pointer type
mplsadm.c:598: `RTM_NEWFTN' undeclared (first use in this function)
mplsadm.c:598: warning: passing arg 2 of `send_ftn' from incompatible
pointer type
mplsadm.c:601: `RTM_DELFTN' undeclared (first use in this function)
mplsadm.c:601: warning: passing arg 2 of `send_ftn' from incompatible
pointer type
mplsadm.c:615: `RTM_SETININSTR' undeclared (first use in this function)
mplsadm.c:615: warning: passing arg 2 of `send_instr' from incompatible
pointer type
mplsadm.c:630: `RTM_SETOUTINSTR' undeclared (first use in this function)

mplsadm.c:630: warning: passing arg 2 of `send_instr' from incompatible
pointer type
mplsadm.c:666: `RTM_NEWXC' undeclared (first use in this function)
mplsadm.c:666: warning: passing arg 2 of `send_xc' from incompatible
pointer type
mplsadm.c:669: `RTM_DELXC' undeclared (first use in this function)
mplsadm.c:669: warning: passing arg 2 of `send_xc' from incompatible
pointer type
make: *** [mplsadm.o] Error 1

I hope someone can help me out with this. Thanx a lot.

bye,
tom

Re: [mpls-linux-general] Bug in mpls-linux?

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

Hello Yordan,

On Thu, Jan 04, 2001 at 04:20:43PM +0100, yal wrote:
> Hello everyone,
> 
> I find something strange in mpls-linux code.
> 
> In 'mpls_output' function is labeled every packet,
> independent from the protocol including the
> ARP request or replay packets.
> I think this is error because we can not update
> ARP table and ....

I'm not sure I follow you.  Are you reporting that you have seen
ARP packets with a label on them, or are you reporting that you think
the code will allow for ARP packet to be labeled.

If you are reporting seeing labeled arp packet please describe how
you were able to accomplish this, because it certainly would be a bug.

If you are saying that the code would allow ARP packets to be labeled, I would
disagree. The only way a packet gets to mpls_output is via mpls_input or
via the output function pointer in a dst_entry.  A dst_entry is what gets
created from the info return in a ARP reply.  Right now the only protocol that
sets the dst_entry output function to be mpls_output is IPv4 
(route.c:rt_set_nexthop())

> I'm sorry if I've misunderstood something!

Maybe your seeing the output message (mpls_output: unknown protocol ....)
This is not what your thinking.  What has happened is that an sk_buff has been
re-used. The IPv4 stack is lazy and didn't set skb->protocol.  So the value
is left over from the last protocol that used the sk_buff.
> 
> Yordan.

Jim
-- 
James R. Leu

[mpls-linux-general] Bug in mpls-linux?

[yal <ya...@iw...>]

Hello everyone,

I find something strange in mpls-linux code.

In 'mpls_output' function is labeled every packet,
independent from the protocol including the
ARP request or replay packets.
I think this is error because we can not update
ARP table and ....

I'm sorry if I've misunderstood something!

Yordan.

[mpls-linux-general] tcpdump/ethereal shows hosed MPLS packets

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

Hello everyone,

If you run tcpdump or ethereal on one of the LERs that are part of an
LSP you will most likely see screwed up packets.  What you see is one of the
intermediate steps that a packet goes through inside of the linux NET stack
while being processed by the MPLS code.

I will see if I can fix this, it would be nice to be able to run tcpdump and
ethereal on the hosts involved in the LSP.

Jim
-- 
James R. Leu

[mpls-linux-general] Strange Behaviour with LER<--->LER LSP and mpls-linux 0.700

[Jordan H. <jo...@br...>]

Hey James,

	I have been playing with mpls-linux for awhile now and recently I
re-compiled and patched the test11 kernel so I could try version 0.700
of your mpls-linux package.  So far, I am seeing some strange behaviors.
Here is the topology:


        |----------|     |----------|
        |  LER A   |     |  LER B   |
        |     eth1 |     | eth0     |
        |----------|     |----------|
          |      | .1   .2 |
-----------      -----------
 172.16.x.x       10.0.0.x

    (All connections are 100 Mb/s Ethernet)

On LER A:

	# route add -host 10.0.0.2 dev eth1
	# mplsadm -L eth1:0
	# mplsadm -A -B -O gen:16:eth1:ipv4:10.0.0.1 -f 10.0.0.2/32
	# mplsadm -A -I gen:17:0

On LER B:

	# route add -host 10.0.0.1 dev eth0
	# mplsadm -L eth0:0
	# mplsadm -A -B -O gen:17:eth0:ipv4:10.0.0.2 -f 10.0.0.1/32
	# mplsadm -A -I gen:16:0

	The first thing that I see, when I do I ping from LER A to LER B
is this (according to both tcpdump and ethereal):

18:16:05.140992 > arp who-has 10.0.0.1 tell 10.0.0.1 (0:20:78:11:8:63)

	That ARP is /originating/ from LER A!  Why does it need to know its
own MAC?  Weird, huh??  I tried to pry myself around whatever problem
that is by creating a static arp entry.  Then, according to ethereal a
properly formed MPLS tagged ICMP packet goes out the door.  The story on
LER B is the same thing, I must add a static ARP entry for the local
interface before it will start to send MPLS tagged packets.  However, not
all is well after that.

	I started a ping from LER B to LER A and the packet looks badly
mangled from LER A's perspective.  The packet from from ethereal looks
like:

0000  00 a0 cc 62 8e 49 00 a0  cc 62 8e 49 88 47 45 00   ..=CCb.I.. =CCb.=
I.GE.
0010  00 54 00 00 40 00 ff 01  67 a6 0a 00 00 02 0a 00   .T..@.=FF. g=A6.=
.....
0020  00 01 08 00 d6 84 c9 03  00 00 23 fd 43 3a fa 3c   ....=D6.=C9. ..#=
=FDC:=FA<
0030  0c 00 08 09 0a 0b 0c 0d  0e 0f 10 11 12 13 14 15   ........ ........
0040  16 17 18 19 1a 1b 1c 1d  1e 1f 20 21 22 23 24 25   ........ .. !"#$=
%
0050  26 27 28 29 2a 2b 2c 2d  2e 2f 30 31 32 33 34 35   &'()*+,- ./01234=
5
0060  36 37 34 35 36 37                                  674567

	To to the ethereal layer view this looks like:

	Frame #x
	Ethernet II
	MultiProtocol Label Switching Header
	MultiProtocol Label Switching Header
	MultiProtocol Label Switching Header
	IP
		[Malformed Frame: IP]

	Whereas a proper packet looks like:

0000  00 20 78 11 08 63 00 20  78 11 08 63 88 47 00 01   . x..c.  x..c.G..
0010  01 40 45 00 00 54 00 00  40 00 40 01 26 a7 0a 00   .@E..T.. @.@.&=A7=
..
0020  00 01 0a 00 00 02 08 00  cf e7 70 04 0e 00 ff ee   ........ =CF=E7p=
...=FF=EE
0030  43 3a 70 e7 0b 00 08 09  0a 0b 0c 0d 0e 0f 10 11   C:p=E7.... .....=
...
0040  12 13 14 15 16 17 18 19  1a 1b 1c 1d 1e 1f 20 21   ........ ...... =
!
0050  22 23 24 25 26 27 28 29  2a 2b 2c 2d 2e 2f 30 31   "#$%&'() *+,-./0=
1
0060  32 33 34 35 36 37                                  234567

	To ethereal this correctly appears as:

	Frame #x
	Ethernet II
	MultiProtocol Label Switching Header
	Internet Protocol
	Internet Control Message Protocol


	I am not sure exactly at which stage things are breaking down here,
but this is a config that used to work with the 0.6xx mpls-linux code.
If there is something you would like me to try, or can point me toward th=
e
right place to start poking around I would be most appreciative!


Anyway, thank you very much!

Jordan.

--=20
  *------=3D=3D=3D=3D=3D=3D=3D=3D=3D------*
  | Jordan Husney       |
  I Software Engineer   I
  I Bravida Corporation I
  | (651) 698-4611      |
  *------=3D=3D=3D=3D=3D=3D=3D=3D=3D------*

[mpls-linux-general] Question on Notification message

[Murali K. P. <mur...@mi...>]

Hi all,
         I have question on NOTIFICATION message in LDP protocol.

The question is notification message does not carry FEC tlv. So how does
the receiving LSR find out for which FEC the notification message is
meant for? Say if a no route notification message is received then how
does one correlate it to the correct FEC for which the notif message is
meant for?=20


	Is it that one has to include the FEC tlv in the notification
message? if this is true then can some body give me pointers where this
is discussed in the ldp-draft.

thanks in advace

murali krishna P.

[mpls-linux-general] RE: Label Mapping Initial call back

[Murali K. P. <mur...@mi...>]

Hi jim,
         I have question regarding the reply you had given me earlier.

Now saying this, there are many ways an LSR running LDP will fit into an

MPLS network.  Currently Juniper runs "the smart mans LDP" which means
that
it only distributes a label for the LSR id in unsolicited mode.  The
result is
instead of distributing labels for every route in the internet routing
table (~90,000) each LSR will only initiate one label mapping.  After
all of
the LSRs in the network have done this, the result will be the minimal
full
mesh of LSPs proving reachability across the MPLS core.  Using BGP or
other means allows you to map the entries in the routing table to these
LSPs.

Cisco runs in vanilla LDP mode, which means it distributes label (in
either
unsolocited OR on demond) for every entry in its forwarding tabel which
is
is willing to act an ingress for.



My understanding of the smart mans LDP is :

If each LSR sends label mapping only  for its own LSR ID. Then the label
table will have two columns FEC and OUTLABEL at each LSR. If LSP is
setup then there will be INLABEL column also included.
	Now if a packet is received then LSR will look up the routing
table get the next hop for the destination and then try to map the
destination address to the FEC and then get the OUTLABEL and do the
necessary modification to the packet.
so the flow will be some thing like this. Correct me if i am wrong.

DEST ->   FEC -> OUTLABEL=20

can you give me some pointers to "the smart man's LDP"



another question :

setup for testing ldp_linux

            eth0 connected via intranet                           eth0
 	LSRA
-------------------------------------------------------------  LSR B
  (ip address of A is 172.20.22.151)
(ip address of A is 172.20.22.58)


  Routing Table at A
Routing table at B is also similar to A
Dest           gateway        mask                 interface=20
172.20.22.58  172.20.22.58   255.255.255.255  UGH   eth0
172.20.22.151 172.20.22.151  255.255.255.255  UGH   eth0


So now i have run the above setup with the following sequence of CLI
commands

set trace 0xffffffff
add debug
add global 172.20.22.151 (correspoding 172.20.22.58 on B)
add interface eth0

Now my problem is that i am receivng label mapping for LSR B . But at
LSR A end it sends no route notifcation to LSR B saying that it cannot
send the label mapping for 172.20.22.151. Both sides are not exchanging
label mappings and it is happening only from one side.

I am attaching the output file stored at LSR A end. kindly help me out.

thanks in advance=20

murali krishna P.






 <<jlieu.ouput.txt>>=20

Re: [mpls-linux-general] examples not working

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

Hello,

On Sat, Dec 09, 2000 at 06:00:34PM +0100, Mudra Peter wrote:
> Hi!
> 
> It seems, that my problem is solved - partially.
> I can now run the tests came with mpls-linux0.700, but it seems that
> when doing ftp fom hostA to hostB, the traffic does not take the 
> LSPs established. Altought ftp was working.

Before setting up the test again execute mplsadm -d.
Setup the test again and then dump the contents of /proc/net/mpls_*.
Also do a 'dmesg' from your shell prompt.

Send all of the outputs to me.

With that info I should be able to see why it's not working for you.

Jim
-- 
James R. Leu

Re: [mpls-linux-general] examples not working

[Jordan H. <jo...@br...>]

Go and grab yourself Ethereal, quite possibly the best traffic sniffer
available for Linux (arguably).  It requires X11, but it is quite cool.

http://www.ethereal.com/

The analizer is able to detect many types of packets, including (but in
no means limited to) MPLS, LDP, and RSVP.


Jordan.

Mudra Peter wrote:
> Hi!
> 
> It seems, that my problem is solved - partially.
> I can now run the tests came with mpls-linux0.700, but it seems that
> when doing ftp fom hostA to hostB, the traffic does not take the 
> LSPs established. Altought ftp was working.
> 
> We've tcpdumped the traffic, and we couldn't see whether ftp uses the LSP or 
> the good old tcp connection.
> 
> How do i know when mpls is working? Maybe i`m just missing the point.
> 
> Thanks in advance
> 
> Peter
> 
> 
> 
> ---------------------------------------------------------------------
> http://www.netposta.net NetPosta, E-m@il ingyen!
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/mailman/listinfo/mpls-linux-general

-- 
  *------=========------*
  | Jordan Husney       |
  I Software Engineer   I
  I Bravida Corporation I
  | (651) 698-4611      |
  *------=========------*

Re: [mpls-linux-general] examples not working

[Mudra P. <mpl...@ne...>]

Hi!

It seems, that my problem is solved - partially.
I can now run the tests came with mpls-linux0.700, but it seems that
when doing ftp fom hostA to hostB, the traffic does not take the 
LSPs established. Altought ftp was working.

We've tcpdumped the traffic, and we couldn't see whether ftp uses the LSP or 
the good old tcp connection.

How do i know when mpls is working? Maybe i`m just missing the point.

Thanks in advance

Peter



---------------------------------------------------------------------
http://www.netposta.net NetPosta, E-m@il ingyen!

Re: [mpls-linux-general] examples not working

[Mudra P. <mpl...@ne...>]

You probably don't have Netlink support in your kernel.  Compile in Netlink 
support (under Networking Options) and you should be set to go.

Jim
-- 
James R. Leu



Indeed, i did compile the kernel that way:

Kernel/user netlink socket
   routing messages
   netlink device emulation

these are all compiled in the kernel as "embedded".

Is there anything else?

But thanks for the answer anyway.

Peter



---------------------------------------------------------------------
http://www.netposta.net NetPosta, E-m@il ingyen!

Re: [mpls-linux-general] examples not working

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

On Fri, Dec 08, 2000 at 10:27:57PM +0100, Mudra Peter wrote:
> Hi!
> 
> I tried out the examples come with mpls-linux0.700, but they don't work.
> I tried the manual LSP setup (README.example) and the ingress configuration,
> but i get Connection refused when adding outlabel
> (Out Label Add: Connection refused
> FTN add: Connection refused)

You probably don't have Netlink support in your kernel.  Compile in Netlink 
support (under Networking Options) and you should be set to go.

Jim
-- 
James R. Leu

[mpls-linux-general] examples not working

[Mudra P. <mpl...@ne...>]

Hi!

I tried out the examples come with mpls-linux0.700, but they don't work.
I tried the manual LSP setup (README.example) and the ingress configuration,
but i get Connection refused when adding outlabel
(Out Label Add: Connection refused
FTN add: Connection refused)

The network topology is the same (of course other network addresses)
The nodes (not mpls aware) see through the network
(i can ping from hostA to hostB and versa)

Thanks in advance

Peter

i use test11 kernel too.


---------------------------------------------------------------------
http://www.netposta.net NetPosta, E-m@il ingyen!

Re: [mpls-linux-general] Hierarchical LSP set up

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

I saw your post to the IETF mailing list.

Have you read the draft:

ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-lsp-hierarchy-01.txt

It explains the notion of a Forwarding Adacency (FA).  When you establish
an LSP between two LSRs, you can consider them to have a FA, thus making the
LSP a FA-LSP.  The FA-LSP has an identifier associated with it (IP address
of some sort)  When signalling a LSP that should tunnel through the
FA-LSP, you signify this by contructing an ERO that has the IP address
assocaited with the FA-LSP as one hop.

RSVP-TE needs to then know how to send PATH and RESV messages to the far end
of a FA-LSP (I'm not sure how this works).

I hope this point you in the right direction.

Jim

PS When asking question to the IETF mailing list, the shorter
the question the better. :-)  Many of the people on the list
will not take the time to answer long questions.

On Wed, Dec 06, 2000 at 05:17:03PM +0530, Ramanjaneyulu Y T wrote:
> Hi,
> 
>    I have questions on how to establish LSPs . pls go through following
> mail and answer to those.
> 
>        Thanks in advance,
> 
> 
> 
> 
>   The following is the scenarios to establish hierarchial LSps.
> 
> Method1
> -------
> 
> 
> 
> 
> 
>     ---------						 ---------
>    |	     |						|	  |
>    | LER11   |						|  LER12  |
>    |	     |						|	  |
>     ---------					 	 ---------
> 	|						     |
> 	.       	  Y		      Z	   	     .
> 	.       --------       -------		  ------   T .
>         |__X___|        |     |       |          |      |____|
> 	       | LER1   |-----|       |-----.....|LER2  |
> 	       |	|     |       |          |      |
> 		--------       -------	          ------
>             
> at LER1                                       at LER2
> label look up table 				label look up table
>   		
>  X -- FWD Y					Z - FWD T
> 
> NHLFE    					NHLFE 	
> 
>  Y -- PUSH Y 					T -- PUSH T
> 
> 
> 
> 
> 
> Note:
> ----
>  PUSH y  -- PUSH label Y
>  FWD  y  -- check entry 'Y'
>             at NHLFE table    
> 
>   The output entry it having separate  operations. In this case it just
> forwads to soecified interface in table.
>                   
> 
>    ---
>     Initially there is no LSP existing between LER1 and LER2. When request
> comes from LER11 , PATH message is sent to LER12 . When LER12 responds
> with
> RESV message with label for previous hop.When RESV message reaches from
> upstream LSR to LER2 , it allocates new label and binds with label from
> upstream LSR and propagates RESV message to previous hop. The same process
> is
> repeated at all LSRS and LER1 also. Now LSP is established between from
> LER11
> to LER12 through LER1 and LER2. Note that this is not hierarchical LSP. 
> 
>   In this case , all data transfers occurs normally. 
> 
> Consider the following scenario.
> 
>   
> 
> 
>     --------						 ---------
>    |	     |						|	  |
>    | LER11   |						|  LER12  |
>    |	     |						|	  |
>     ---------					 	 ---------
> 	|						     |
> 	. 		  Y		  Z		     .
> 	.       --------       -------		  ------     .
>         |__X___|        |     |       |          |      |__T_|
> 	       | LER1   |-----|       |-----.....|LER2  |
> 	 ______|	|     |       |          |      |_____
> 	|A	--------       -------	          ------      | 	
> 	|						   B  |
> 	. 						      .	
> 	.						      .
> 							      |	
> 	|						 ----------
>      --------						|	   |
>     |	     |						|  LER 22  |
>     | LER 21 |						|	   |
>     |	     |						 ----------
>      -------- 					
> 
> 
> 
> In this scenario, we want to set up an LSP between LER21 and LER 22
> through
> LER1 and LER 2 which is a heirarchical LSP (in the sense that the same LSP
> wil
> be used by both the traffic flows from LER 11 and LER 21)
> 					
> Note:
> ----
>   LER2 generates label 'C' and informs to LER1 for LER21.  
> 
> 
> 
> at LER1                                       at LER2
> 
> label look up table 				label look up table
>   		
>  X -- FWD Y					Z - FWD T
>  A -- PUSH C , FWD Y                            C - FWD B
> 
> NHLFE    					NHLFE 	
> 
>  Y -- PUSH Y 					T -- PUSH T
> 						B -- PUSH B	
> 
> 
> 
> 
> 
> 
> 
>    If LER21 wants to establish LSP to LER22. It sends PATH request to
> LER22.
> LER22 responds to PATH message with RESV message with label for previous
> hop.
> when RESV message reaches to LER2 , it generates a new label for LER1 ,
> LSP
> is already existing between LER1 and LER2. In core LSRS between LER1 and
> LER2
> , just bypasses this message. At LER1 , it generates a new label and
> places
> PUSH LER2 label operation in newly generated label and forwards it to
> previous hop.
> 
> 
>     My question is , how LER2 differentiate MPLS data packets whether to
> forward
> to LER12 or LER22 by seeing on top label ( here 'Z'). 
> 
> Method2
> -------
>     If we establish one LSP between LER1 and LER2, then we can use this
> LSP to
> establish LER11 and LER12 as hierarchical LSPs. same way for LER21 and
> LER22.
> If this is the case at LER2 , data packet contains label stack of depth 2
> .
> So POP top label at LER2 and based on next label one can forward the
> packet. 
> But for this one is required to establish LSPs statically and those 2
> nodes
> should  know each other. But this approach is not suitable, i think , due
> to
> these constraints.
> 
> 
>        During LSP establishment between LER11 and LER12 , the LER2
> generates
> new label and informs to LER1. This is same for second LSP also.
> 
>     suppose LER2 generates M for LER12. The table update is as follows.
> 
> at LER1                                       at LER2
> 
> label look up table 				label look up table
>   		
>     						Z - POP
>  A -- PUSH C , FWD Y                            C - FWD B
>  X -- PUSH M , FWD Y  				M - FWD T
> 
> NHLFE    					NHLFE 	
> 
>  Y -- PUSH Y 					T -- PUSH T
> 						B -- PUSH B
> 								
> 
> 
>   So at LER2 , the MPLS pkt conatins M,Z or C,Z. So by looking on tables ,
> it
> learns POP top label and looks on next label. This is works fine in
> hierarchical environmant , but it has constraints.
> 
> Questions:
> ---------
> 
> 1. Is above methods are correct ?
> 
> 2.    Other than these 2 methods any other methods avaialble to achieve
> hierarchial LSPs ?.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>                                          
>                                          Regards
>                                         Ramanjaneyulu Y.T. 
> --  
>  " A real friend is one who walks in when the rest of the world walks
>  out."
>  ------------------------------------------------------------------------------ 
> Y.T.RAMANJANEYULU                        |   My other mail Ids:
> E-70,INDIAN INSTITUTE OF SCIENCE         |         yt...@12...
> BANGALORE - 560012                       |         ki...@ex...
> PH: 91 - 80 - 3092622 ( HOSTEL )         |
>     91 - 80 - 3092658 ( HFCL LAB )       |
>                    visit my home page:www2.csa.iisc.ernet.in/~ytr
> --------------------------------------------------------------------------------
> 
> 
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/mailman/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Hierarchical LSPs and RSVP-TE

[Ramanjaneyulu Y T <yt...@cs...>]

HI,
   If this issue has already been discussed please provide pointers to
mail archives.  


The question here is the establishment of Hierarchal LSPs by using
RSVP-TE signalling.

We consider the following scenario.

                         (virtual pipe of LSP)
LER1-----LSR2-----LSR3-.-.-.-.-.-.-.-.-.-.-.-.LSR4-----LSR5-------LER2
                    \                        /
                     \                      /
                      \____lsr11.....lsr1n-/



We have the above topology of the network. We want to establish an LSP
between LER1 and LER2.

Note that we don't have a direct path between LSR3 and LSR4 . But  they
are
connected through  lsr11 .... lsr1n.(which are opaque to the endpoints
LER1
and LER2)

LER1 initiates a PATH message with ERO Object as:
     LSR2  LSR3  LSR4  LSR5 LER2

So as Path message propagates and comes to LSR3 it will find that it does
not
have a direct path to LSR4. so it will add more sub objects to ERO
specifying
the nodes lsr11 ... lsr1n so that the Path message traverses through these
routers and finally comes at LSR4. Now LSR4 will forward the message to
LER2
through LSR5. and Resv message will appropriately flow backwards and
complete the LSP setup.


Now if there are more requests for LSPs which have paths through LSR3 and
LSR4
then each time LSR3 will be generating independent labels which will
perhaps
use a lot of labels. Since the path between LSR3 and LSR4 is common for
many
LSPs we can setup a single LSP between LSR3 and LSR4 on which we can build
hierarchical LSPs through this LSP. 

There is also an issue of Management of LSPs.
   Since now we have a point to point LSP between LER1 and LER2  we would
not
like these two endpoints to know about the actual route traversed between
the
two routers LSR3 and LSR4. So even if anything happens to the Path between
LSR3 and LSR4, It will be automatically rerouted by LSR3 (if alternative
path is
available) without the actual endpoints (LER1 and LER2) being aware of
such a
change. 
But for this we require to have a common LSP between LSR3 and LSR4.

Now this will require an LSP  to be either already present between LSR3
and
LSR4  which is installed statically or it can be setup  dynamically.
   If we have to setup the intermediate LSPs dynamically  then how do we
do
it ??
 
So one possible solution will be  something like this:

 When a Path for a new LSP set up starts from LER1 , reaches LSR3 (we
don't
have any LSP between LSR3 and LSR4) then we delay this path request and
start
a new path message from LSR3 to LSR4 through lsr11...lsr1n which will
establish LSP between LSR3 and LSR4.Once this is established we can allow
the
delayed Path message to be forwarded to LSR4 through the intermediate LSRs
and then finally to the destination. The resv message will also propagate
upstream to the sender.
   But in this procedure when do we reserve the resources for the
LSP(between
LSR3 and LSR4)???

One more solution is to establish the inner LSP (between LSR3 and LSR4)
statically.

Which one is better?? Or is there any other method of setting up of such
hierarchical LSPs.??
  

Thanks in advance,


                                         Regards
                                        Ramanjaneyulu Y.T. 

[mpls-linux-general] Hierarchical LSP set up

[Ramanjaneyulu Y T <yt...@cs...>]

Hi,

   I have questions on how to establish LSPs . pls go through following
mail and answer to those.

       Thanks in advance,




  The following is the scenarios to establish hierarchial LSps.

Method1
-------





    ---------						 ---------
   |	     |						|	  |
   | LER11   |						|  LER12  |
   |	     |						|	  |
    ---------					 	 ---------
	|						     |
	.       	  Y		      Z	   	     .
	.       --------       -------		  ------   T .
        |__X___|        |     |       |          |      |____|
	       | LER1   |-----|       |-----.....|LER2  |
	       |	|     |       |          |      |
		--------       -------	          ------
            
at LER1                                       at LER2
label look up table 				label look up table
  		
 X -- FWD Y					Z - FWD T

NHLFE    					NHLFE 	

 Y -- PUSH Y 					T -- PUSH T





Note:
----
 PUSH y  -- PUSH label Y
 FWD  y  -- check entry 'Y'
            at NHLFE table    

  The output entry it having separate  operations. In this case it just
forwads to soecified interface in table.
                  

   ---
    Initially there is no LSP existing between LER1 and LER2. When request
comes from LER11 , PATH message is sent to LER12 . When LER12 responds
with
RESV message with label for previous hop.When RESV message reaches from
upstream LSR to LER2 , it allocates new label and binds with label from
upstream LSR and propagates RESV message to previous hop. The same process
is
repeated at all LSRS and LER1 also. Now LSP is established between from
LER11
to LER12 through LER1 and LER2. Note that this is not hierarchical LSP. 

  In this case , all data transfers occurs normally. 

Consider the following scenario.

  


    --------						 ---------
   |	     |						|	  |
   | LER11   |						|  LER12  |
   |	     |						|	  |
    ---------					 	 ---------
	|						     |
	. 		  Y		  Z		     .
	.       --------       -------		  ------     .
        |__X___|        |     |       |          |      |__T_|
	       | LER1   |-----|       |-----.....|LER2  |
	 ______|	|     |       |          |      |_____
	|A	--------       -------	          ------      | 	
	|						   B  |
	. 						      .	
	.						      .
							      |	
	|						 ----------
     --------						|	   |
    |	     |						|  LER 22  |
    | LER 21 |						|	   |
    |	     |						 ----------
     -------- 					



In this scenario, we want to set up an LSP between LER21 and LER 22
through
LER1 and LER 2 which is a heirarchical LSP (in the sense that the same LSP
wil
be used by both the traffic flows from LER 11 and LER 21)
					
Note:
----
  LER2 generates label 'C' and informs to LER1 for LER21.  



at LER1                                       at LER2

label look up table 				label look up table
  		
 X -- FWD Y					Z - FWD T
 A -- PUSH C , FWD Y                            C - FWD B

NHLFE    					NHLFE 	

 Y -- PUSH Y 					T -- PUSH T
						B -- PUSH B	







   If LER21 wants to establish LSP to LER22. It sends PATH request to
LER22.
LER22 responds to PATH message with RESV message with label for previous
hop.
when RESV message reaches to LER2 , it generates a new label for LER1 ,
LSP
is already existing between LER1 and LER2. In core LSRS between LER1 and
LER2
, just bypasses this message. At LER1 , it generates a new label and
places
PUSH LER2 label operation in newly generated label and forwards it to
previous hop.


    My question is , how LER2 differentiate MPLS data packets whether to
forward
to LER12 or LER22 by seeing on top label ( here 'Z'). 

Method2
-------
    If we establish one LSP between LER1 and LER2, then we can use this
LSP to
establish LER11 and LER12 as hierarchical LSPs. same way for LER21 and
LER22.
If this is the case at LER2 , data packet contains label stack of depth 2
.
So POP top label at LER2 and based on next label one can forward the
packet. 
But for this one is required to establish LSPs statically and those 2
nodes
should  know each other. But this approach is not suitable, i think , due
to
these constraints.


       During LSP establishment between LER11 and LER12 , the LER2
generates
new label and informs to LER1. This is same for second LSP also.

    suppose LER2 generates M for LER12. The table update is as follows.

at LER1                                       at LER2

label look up table 				label look up table
  		
    						Z - POP
 A -- PUSH C , FWD Y                            C - FWD B
 X -- PUSH M , FWD Y  				M - FWD T

NHLFE    					NHLFE 	

 Y -- PUSH Y 					T -- PUSH T
						B -- PUSH B
								


  So at LER2 , the MPLS pkt conatins M,Z or C,Z. So by looking on tables ,
it
learns POP top label and looks on next label. This is works fine in
hierarchical environmant , but it has constraints.

Questions:
---------

1. Is above methods are correct ?

2.    Other than these 2 methods any other methods avaialble to achieve
hierarchial LSPs ?.













                                         
                                         Regards
                                        Ramanjaneyulu Y.T. 
--  
 " A real friend is one who walks in when the rest of the world walks
 out."
 ------------------------------------------------------------------------------ 
Y.T.RAMANJANEYULU                        |   My other mail Ids:
E-70,INDIAN INSTITUTE OF SCIENCE         |         yt...@12...
BANGALORE - 560012                       |         ki...@ex...
PH: 91 - 80 - 3092622 ( HOSTEL )         |
    91 - 80 - 3092658 ( HFCL LAB )       |
                   visit my home page:www2.csa.iisc.ernet.in/~ytr
--------------------------------------------------------------------------------

Re: [mpls-linux-general] RE: [MPLS-Linux] Bug with 2.4.0-test11, mpls 0.700 and Interphase ATM PCI x575/x52 5/x531

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

On Tue, Dec 05, 2000 at 05:07:52PM -0500, Jonathan Earle wrote:
> > -----Original Message-----
> > From: James R. Leu [mailto:jl...@mi...]
> > 
> > What is the physical ATM index of the card?  (more 
> > /proc/net/atm/devices)
> 
> root@onc2:~> cat /proc/net/atm/devices
> Itf Type    ESI/"MAC"addr AAL(TX,err,RX,err,drop) ...
>   0 ia      00007794576c  0 ( 0 0 0 0 0 )  5 ( 190 0 190 0 0 )
> 
> > Can you try doing a mplsadm -d prior to running this command 
> > and see if
> > if gives any output?
> 
> If I use atm1 for the adapter instead of atm0, it stops crashing.  The LSP
> itself doesn't seem to work though - tcpdumping either side results in plain
> ping results.

Which makes sense.  atm1 is going to try and create a vcc on physical ATM
index 1 (this changed in 0.700).  You don;t have atm index 1 so if fails
(unfortunatly I haven't implemented failures coming back via netlink)

Jim
-- 
James R. Leu