Thread: [mpls-linux-devel] linux-kernel-2.6.14
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel
|
From: Bob B. <bob...@gm...> - 2005-11-10 15:27:57
Attachments:
diff_of_linux-kernel_for2.6.14.diff
|
Hi list, I want to intergrate mpls-linux into my device, and would like to use kernel 2.6.14. To that end I have modified the patches/linux-kernel.d= iff to get a successful patch (a diff for the diff file is attached). Is anyone else working on this? I am getting compile errors, and can probably work through them, but, if it is already done somewhere I could save a lot of time. Are there any reasons not to move forward with my plans? Thanks, -Bob |
|
From: James R. L. <jl...@mi...> - 2005-11-10 15:36:46
|
My development tree is currently patched against 2.6.13 so getting mpls-linux to work on a 2.6.11 (and beyond) kernel is possible. My guess is you are seeing the issue with 'sock_no_release' being removed. Someone has already posted patches for this, in fact they might be available from http://sf.net/projects/mpls-linux under the patch section. May I ask what your working on? Also you might be interested to know that 1.950 is almost ready for release. It adds some significant features, as well as fixes a race conditions with respect to IPv4 route cac= he and NHLFE deletes. On Thu, Nov 10, 2005 at 10:27:52AM -0500, Bob Beers wrote: > Hi list, >=20 > I want to intergrate mpls-linux into my device, and would like to > use kernel 2.6.14. To that end I have modified the patches/linux-kernel= .diff > to get a successful patch (a diff for the diff file is attached). >=20 > Is anyone else working on this? I am getting compile errors, and can > probably work through them, but, if it is already done somewhere I could > save a lot of time. >=20 > Are there any reasons not to move forward with my plans? >=20 > Thanks, >=20 > -Bob --=20 James R. Leu jl...@mi... |
|
From: Bob B. <bob...@gm...> - 2005-11-10 18:05:05
|
> mpls-linux to work on a 2.6.11 (and beyond) kernel is possible. > My guess is you are seeing the issue with 'sock_no_release' > being removed. Someone has already posted patches for this, in fact > they might be available from http://sf.net/projects/mpls-linux under the > patch section. great, I'll look there. > that 1.950 is almost ready for release. It adds some significant > features, as well as fixes a race conditions with respect to IPv4 route c= ache > and NHLFE deletes. also good, I'll keep an eye out for that release. -- -Bob |
|
From: Bob B. <bob...@gm...> - 2005-11-22 21:26:46
|
On 11/10/05, James R. Leu <jl...@mi...> wrote:
> My development tree is currently patched against 2.6.13 so getting
> mpls-linux to work on a 2.6.11 (and beyond) kernel is possible.
>
>
I got your development tree as of 20051121, and applied
patch-2.6.15-rc1-rc2 since I noticed you were at -rc1.
But I get a compile error:
CC [M] net/ipv4/mpls4.o
net/ipv4/mpls4.c: In function `mpls4_local_deliver':
net/ipv4/mpls4.c:298: error: too few arguments to function `ip_rcv'
make[2]: *** [net/ipv4/mpls4.o] Error 1
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2
and, of course it's true: ip_rvc() expects 4 arguments.
net/ipv4/ip_input.c:
int ip_rcv(struct sk_buff *skb,
struct net_device *dev,
struct packet_type *pt,
struct net_device *orig_dev)
but mpls4_local_deliver() provides only 3:
net/ipv4/mpls4.c:
return ip_rcv(skb, skb->dev, NULL);
Should I go just drop back to the 1.946 tarball and apply to say, 2.6.10?
What is likely to get me to a working MPLS enabled 2.6.x kernel most quickl=
y?
Thanks,
-Bob
|
|
From: James R. L. <jl...@mi...> - 2005-11-23 14:08:27
|
At this time your quickest path is to revert back to 2.6.9 and apply the 1.946 patch. Although I'm getting dangerously close to=20 making a new release .. (probably next week after the US thanksgiving holiday). If you want to forge ahead, update you linux-kernel tree and make sure to pull out a new iproute2-mpls tree (View: //depot/iproute2-mpls/... //<new-client-name>/...) As of last night I was able to use the 'mpls' utility to create static LSPs and bind routes to them. If you're really looking for something bleeding edge, grab my ebtables-mpls tree and you can do "ethernet over MPLS" (the support was there many release ago, in a hacked up sort of way, now using ebtables I have a much better implementation) On Tue, Nov 22, 2005 at 04:26:37PM -0500, Bob Beers wrote: > On 11/10/05, James R. Leu <jl...@mi...> wrote: > > My development tree is currently patched against 2.6.13 so getting > > mpls-linux to work on a 2.6.11 (and beyond) kernel is possible. > > > > > I got your development tree as of 20051121, and applied > patch-2.6.15-rc1-rc2 since I noticed you were at -rc1. >=20 > But I get a compile error: >=20 > CC [M] net/ipv4/mpls4.o > net/ipv4/mpls4.c: In function `mpls4_local_deliver': > net/ipv4/mpls4.c:298: error: too few arguments to function `ip_rcv' > make[2]: *** [net/ipv4/mpls4.o] Error 1 > make[1]: *** [net/ipv4] Error 2 > make: *** [net] Error 2 >=20 > and, of course it's true: ip_rvc() expects 4 arguments. > net/ipv4/ip_input.c: > int ip_rcv(struct sk_buff *skb, > struct net_device *dev, > struct packet_type *pt, > struct net_device *orig_dev) >=20 > but mpls4_local_deliver() provides only 3: > net/ipv4/mpls4.c: > return ip_rcv(skb, skb->dev, NULL); >=20 > Should I go just drop back to the 1.946 tarball and apply to say, 2.6.10? > What is likely to get me to a working MPLS enabled 2.6.x kernel most quic= kly? >=20 > Thanks, >=20 > -Bob --=20 James R. Leu jl...@mi... |
|
From: Bob B. <bob...@gm...> - 2005-11-23 17:13:00
|
On 11/23/05, James R. Leu <jl...@mi...> wrote: > At this time your quickest path is to revert back to 2.6.9 and > apply the 1.946 patch. Although I'm getting dangerously close to > making a new release .. (probably next week after the US thanksgiving > holiday). > 2.6.9 is just a bit too old for some of the other kernel things I need, but if I am completely stumped I may try it. :P > If you want to forge ahead, update you linux-kernel tree and make sure > to pull out a new iproute2-mpls tree > (View: //depot/iproute2-mpls/... //<new-client-name>/...) //depot/iproute2-mpls-1.1/ ?? Thanks, -Bob |
|
From: Bob B. <bob...@gm...> - 2005-12-01 17:29:51
|
On 11/23/05, James R. Leu <jl...@mi...> wrote: > At this time your quickest path is to revert back to 2.6.9 and > apply the 1.946 patch. Although I'm getting dangerously close to > making a new release .. (probably next week after the US thanksgiving > holiday). > Ok, trying two paths at the same time. I am trying this, but make fails wi= th a few warnings: net/mpls/mpls_netlink.o(.init.text+0x0): In function `init_module': : multiple definition of `init_module' net/mpls/mpls_init.o(.init.text+0x0): first defined here ... and similar complaint about `cleanup_module'. Clues for me? -- -Bob |
|
From: James R. L. <jl...@mi...> - 2005-12-01 18:11:50
|
For now don't compile MPLS as a module. I'm still working out module loading issues. On Thu, Dec 01, 2005 at 12:29:43PM -0500, Bob Beers wrote: > On 11/23/05, James R. Leu <jl...@mi...> wrote: > > At this time your quickest path is to revert back to 2.6.9 and > > apply the 1.946 patch. Although I'm getting dangerously close to > > making a new release .. (probably next week after the US thanksgiving > > holiday). > > >=20 > Ok, trying two paths at the same time. I am trying this, but make fails = with > a few warnings: >=20 > net/mpls/mpls_netlink.o(.init.text+0x0): In function `init_module': > : multiple definition of `init_module' > net/mpls/mpls_init.o(.init.text+0x0): first defined here > ... >=20 > and similar complaint about `cleanup_module'. >=20 > Clues for me? >=20 > -- > -Bob --=20 James R. Leu jl...@mi... |
|
From: Bob B. <bob...@gm...> - 2005-12-01 20:47:38
|
On 12/1/05, James R. Leu <jl...@mi...> wrote: > For now don't compile MPLS as a module. I'm still working out module > loading issues. > OK, all MPLS built-in, no modules. but ... trying the example in mpls-linux-patches.README.iproute2 iproute2/mpls# ./mpls nhlfe add key 0 Cannot talk to rtnetlink: Connection refused Did I leave out a module? Also, I'm confused about the mplsadm2 command mentioned in patches/README.examples? Where do I find that tool? -- -Bob |
|
From: James R. L. <jl...@mi...> - 2005-12-01 21:58:48
|
Since you're using the mpls-kernel from my dev tree, you will need to use the iproute-mpls from my dev tree as well. (ie the patch in mpls-linux is out-dated) mplsadm2 is the name of the old utility to add MPLS entities. That functionality is not handled by the 'mpls' utility in iproute-mpls. I'll update the README to remove references to mplsadm2 On Thu, Dec 01, 2005 at 03:47:36PM -0500, Bob Beers wrote: > On 12/1/05, James R. Leu <jl...@mi...> wrote: > > For now don't compile MPLS as a module. I'm still working out module > > loading issues. > > >=20 > OK, all MPLS built-in, no modules. >=20 > but ... trying the example in mpls-linux-patches.README.iproute2 >=20 > iproute2/mpls# ./mpls nhlfe add key 0 > Cannot talk to rtnetlink: Connection refused >=20 > Did I leave out a module? >=20 > Also, I'm confused about the mplsadm2 command mentioned in > patches/README.examples? Where do I find that tool? >=20 > -- > -Bob --=20 James R. Leu jl...@mi... |
|
From: Bob B. <bob...@gm...> - 2005-12-02 14:05:58
|
On 12/1/05, James R. Leu <jl...@mi...> wrote:
> Since you're using the mpls-kernel from my dev tree, you will
> need to use the iproute-mpls from my dev tree as well.
> (ie the patch in mpls-linux is out-dated)
ok, let me see if I understand my options:
1) a)use your dev tree for kernel 2.6.15-rc1-mpls
(all MPLS in kernel -- no modules)
b)use dev tree for iproute2 and mpls is the binary tool
2) a)use 2.6.9 vanilla kernel, apply linux-kernel.diff from 1.946 tarball
(all MPLS in kernel -- no modules)
b)use iproute2 package from ???, apply iproute2.diff from 1.946 tarball
I'll willing to try both/either.
BTW, is there a shortcut for 'p4 sync'? When I do that, it gets
_everything_ again,
doesn't seem to get just changed files -- (takes a _lo-o-o-o-ong_ time).
--
Thanks,
-Bob
|
|
From: James R. L. <jl...@mi...> - 2005-12-02 22:04:15
|
On Fri, Dec 02, 2005 at 09:05:50AM -0500, Bob Beers wrote:
<snip>
> BTW, is there a shortcut for 'p4 sync'? When I do that, it gets
> _everything_ again,
> doesn't seem to get just changed files -- (takes a _lo-o-o-o-ong_ time).
Your client view has a great impact on this.
What I do is have multiple clients each with a very specific view.
That way when sync'ing a client p4 only has to consider a small number
of files. Also if you've been syncing recently there have been large
changes in the tree, merging that latest linux rev to all sorts of
branches.
BTW you can see all of the clients by doing a p4 clients (note 's' at the e=
nd).
Do 'p4 clients | grep jleu' and you'll see how many clients I have created.
Doing a 'p4 client -o <client-name>' and you can see what the details for
that client are. For example doing a:
p4 client -o jleu:mpls-kernel-3
shows the details of my HOL mpls-kernel tree, and show the view I'm using:
//depot/mpls-kernel-1.1/... //jleu:mpls-kernel-3/...
Which maps just the mpls-kernel-1.1 directory to my client. If you
didn't modify your view, then your view looks like:
//depot/... //jleu:mpls-kernel-3/...
Which means every directory in the dev tree is mapped into your client ...
which is a bad idea :-)
I see you have a client (actually 3, but they all look like they resuse
the same directory). If I were you I would move all of the views execpt
for the mpls-kernel-1.1 to a new client. Leave the mpls-kernel-1.1 line
so you don't have to re-sync it. My guess is that the size of the
mpls-kernel-1.1 directory is what is making it so slow, that and the fact
my p4 server lives off of a DSL line with an upstream of 400Kbps.
--=20
James R. Leu
jl...@mi...
|
|
From: Bob B. <bob...@gm...> - 2005-12-06 21:32:17
|
Hi James,
Thanks for the p4 hints.
I have made some progress in your dev tree.
I have built and booted into an mpls enabled kernel.
But when I try to run through the MPLS-Linux example, here
are the results:
bash-3.00# cat /sys/mpls/version
1.950
bash-3.00# cat /sys/mpls/debug
1
bash-3.00# /usr/sbin/mpls nhlfe add key 0
NHLFE entry key 0x00000002 mtu 0 propagate_ttl
(0 bytes, 0 pkts)
bash-3.00# /usr/sbin/mpls nhlfe change key 0x2 instructions push gen
10000 nexthop eth0 ipv4 172.16.87.21
bash-3.00# /usr/sbin/ip route add 172.16.87.21/32 via 172.16.87.21
spec_nh 0x8847 0x2
Error: either "to" is duplicate, or "spec_nh" is a garbage.
bash-3.00#
I did recompile the iproute2 files after rebooting into my new kernel.
I did edit the Makefile, ran make and make install (as root).
What did I miss? How do I troubleshoot?
Thanks,
--
-Bob
|
|
From: James R. L. <jl...@mi...> - 2005-12-06 21:50:30
|
You're getting bitten by my lack of new documentation.
With the iproute2 that is in the dev tree there is a new
syntax. Looking at the output of 'ip route help' would have helped you,
but here it the new syntax you want to use:
ip route add 10.0.0.0/16 via 192.168.1.1 mpls 0x2
If you plan on using the iptables from my dev tree, there is a new
syntax for that as well:
iptables -A OUTPUT -d 10.0.0.1/32 -j mpls --nhlfe=3D0x2
In the dev tree there is also support for ebtables, if you plan
on doing ethernet over MPLS. I have an example I can send you if
you're interested.
Version 1.950 also supports PHP. The same feature can
be used to prevent an IP lookup on the egress LER.
The mpls_tunnel interface has also changed in 1.950. Since I told
you to make MPLS static in the kernel, you will only have one
tunnel interface. Once I fix the module loading (or add a new config
item for the MPLS tunnel interface) then you will be able to load the
module multiple times for multiple tunnel interfaces.
I'm probably forgetting something, let me know if you run into more
problems.
BTW look at the output of 'dmesg' for some insight as to what is
happening inside of the MPLS code. If you want to turn that off
just do 'echo 0 > /sys/mpls/debug'
On Tue, Dec 06, 2005 at 04:31:46PM -0500, Bob Beers wrote:
> Hi James,
>=20
> Thanks for the p4 hints.
>=20
> I have made some progress in your dev tree.
> I have built and booted into an mpls enabled kernel.
>=20
> But when I try to run through the MPLS-Linux example, here
> are the results:
>=20
> bash-3.00# cat /sys/mpls/version
> 1.950
> bash-3.00# cat /sys/mpls/debug
> 1
> bash-3.00# /usr/sbin/mpls nhlfe add key 0
> NHLFE entry key 0x00000002 mtu 0 propagate_ttl
> (0 bytes, 0 pkts)
> bash-3.00# /usr/sbin/mpls nhlfe change key 0x2 instructions push gen
> 10000 nexthop eth0 ipv4 172.16.87.21
> bash-3.00# /usr/sbin/ip route add 172.16.87.21/32 via 172.16.87.21
> spec_nh 0x8847 0x2
> Error: either "to" is duplicate, or "spec_nh" is a garbage.
> bash-3.00#
>=20
>=20
> I did recompile the iproute2 files after rebooting into my new kernel.
> I did edit the Makefile, ran make and make install (as root).
> What did I miss? How do I troubleshoot?
>=20
> Thanks,
>=20
> --
> -Bob
--=20
James R. Leu
jl...@mi...
|
|
From: Bob B. <bob...@gm...> - 2005-12-06 22:06:42
|
On 12/6/05, James R. Leu <jl...@mi...> wrote: > You're getting bitten by my lack of new documentation. > > With the iproute2 that is in the dev tree there is a new > syntax. Looking at the output of 'ip route help' would have helped you, > but here it the new syntax you want to use: > > ip route add 10.0.0.0/16 via 192.168.1.1 mpls 0x2 > ok, thanks, I get a step further root@alakazam:~# /usr/sbin/ip route add 172.16.87.21/32 via 172.16.87.21 mpls 0x2 does not complain but, root@alakazam:~# /usr/sbin/mpls nhlfe show just sits there and doesn't return. root@alakazam:~# tail -n 30 /var/log/debug Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:398:genl_mpls_nhlfe_dump: Enter: entry 0 Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:402:genl_mpls_nhlfe_dump: Dump: entry 0 Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:249:mpls_fill_nhlfe: enter Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:49:mpls_copy_instr: enter Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_opcode.c:364:mpls_unbuild_opcode_push: enter Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_opcode.c:369:mpls_unbuild_opcode_push: exit Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_opcode.c:1109:mpls_unbuild_opcode_set: enter Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_opcode.c:1115:mpls_unbuild_opcode_set: exit Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:63:mpls_copy_instr: exit Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:266:mpls_fill_nhlfe: exit Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:419:genl_mpls_nhlfe_dump: Exit: entry 1 Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:398:genl_mpls_nhlfe_dump: Enter: entry 1 Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:402:genl_mpls_nhlfe_dump: Dump: entry 0 Dec 6 16:59:51 alakazam kernel: MPLS DEBUG net/mpls/mpls_netlink.c:419:genl_mpls_nhlfe_dump: Exit: entry 1 > If you plan on using the iptables from my dev tree, there is a new > syntax for that as well: > > iptables -A OUTPUT -d 10.0.0.1/32 -j mpls --nhlfe=3D0x2 > yes, I will need this as well, but first things first. :) > In the dev tree there is also support for ebtables, if you plan > on doing ethernet over MPLS. I have an example I can send you if > you're interested. > > Version 1.950 also supports PHP. The same feature can > be used to prevent an IP lookup on the egress LER. > > The mpls_tunnel interface has also changed in 1.950. Since I told > you to make MPLS static in the kernel, you will only have one > tunnel interface. Once I fix the module loading (or add a new config > item for the MPLS tunnel interface) then you will be able to load the > module multiple times for multiple tunnel interfaces. > I will live with one tunnel while I get to know this stuff. > I'm probably forgetting something, let me know if you run into more > problems. > > BTW look at the output of 'dmesg' for some insight as to what is > happening inside of the MPLS code. If you want to turn that off > just do 'echo 0 > /sys/mpls/debug' > wilco. <snip old message> |
|
From: James R. L. <jl...@mi...> - 2005-12-07 06:21:50
|
The bug you're seeing is one I fixed in change 1310. Could you make sure y=
our
iproute-mpls tree has that change.
cd iproute-mpls
p4 changes ... | more
The '...' tells p4 to only consider files in this part of the depot
(remember your client has just a small view of the depot, without '...'
you would get all changes submitted to the depot)
Also I did some work tonight on modules. I was able to compile
mpls, mpls_tunnel, mpls4, mpls6, ipt_mpls, ebt_mpls as modules
and load them in the correct order and get a functional MPLS stack.
So make sure to sync your mpls-kernel tree and rebuild (optionally
with MPLS compiled as a module)
On Tue, Dec 06, 2005 at 05:06:03PM -0500, Bob Beers wrote:
> On 12/6/05, James R. Leu <jl...@mi...> wrote:
> > You're getting bitten by my lack of new documentation.
> >
> > With the iproute2 that is in the dev tree there is a new
> > syntax. Looking at the output of 'ip route help' would have helped you,
> > but here it the new syntax you want to use:
> >
> > ip route add 10.0.0.0/16 via 192.168.1.1 mpls 0x2
> >
>=20
> ok, thanks, I get a step further
>=20
> root@alakazam:~# /usr/sbin/ip route add 172.16.87.21/32 via
> 172.16.87.21 mpls 0x2
>=20
> does not complain but,
>=20
> root@alakazam:~# /usr/sbin/mpls nhlfe show
>=20
> just sits there and doesn't return.
>=20
> root@alakazam:~# tail -n 30 /var/log/debug
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:398:genl_mpls_nhlfe_dump: Enter: entry 0
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:402:genl_mpls_nhlfe_dump: Dump: entry 0
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:249:mpls_fill_nhlfe: enter
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:49:mpls_copy_instr: enter
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:364:mpls_unbuild_opcode_push: enter
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:369:mpls_unbuild_opcode_push: exit
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:1109:mpls_unbuild_opcode_set: enter
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:1115:mpls_unbuild_opcode_set: exit
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:63:mpls_copy_instr: exit
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:266:mpls_fill_nhlfe: exit
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:419:genl_mpls_nhlfe_dump: Exit: entry 1
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:398:genl_mpls_nhlfe_dump: Enter: entry 1
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:402:genl_mpls_nhlfe_dump: Dump: entry 0
> Dec 6 16:59:51 alakazam kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:419:genl_mpls_nhlfe_dump: Exit: entry 1
>=20
>=20
>=20
> > If you plan on using the iptables from my dev tree, there is a new
> > syntax for that as well:
> >
> > iptables -A OUTPUT -d 10.0.0.1/32 -j mpls --nhlfe=3D0x2
> >
>=20
> yes, I will need this as well, but first things first. :)
>=20
> > In the dev tree there is also support for ebtables, if you plan
> > on doing ethernet over MPLS. I have an example I can send you if
> > you're interested.
> >
> > Version 1.950 also supports PHP. The same feature can
> > be used to prevent an IP lookup on the egress LER.
> >
> > The mpls_tunnel interface has also changed in 1.950. Since I told
> > you to make MPLS static in the kernel, you will only have one
> > tunnel interface. Once I fix the module loading (or add a new config
> > item for the MPLS tunnel interface) then you will be able to load the
> > module multiple times for multiple tunnel interfaces.
> >
>=20
> I will live with one tunnel while I get to know this stuff.
>=20
> > I'm probably forgetting something, let me know if you run into more
> > problems.
> >
> > BTW look at the output of 'dmesg' for some insight as to what is
> > happening inside of the MPLS code. If you want to turn that off
> > just do 'echo 0 > /sys/mpls/debug'
> >
>=20
> wilco.
> <snip old message>
>=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_idv37&alloc_id=16865&op?k
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: Bob B. <bob...@gm...> - 2005-12-07 14:34:29
|
On 12/7/05, James R. Leu <jl...@mi...> wrote: > The bug you're seeing is one I fixed in change 1310. Could you make sure= your > iproute-mpls tree has that change. > > cd iproute-mpls > p4 changes ... | more > > The '...' tells p4 to only consider files in this part of the depot > (remember your client has just a small view of the depot, without '...' > you would get all changes submitted to the depot) bbeers@alakazam:~/download/perforce/p4client/iproute2$ ../../p4 -c bbeers:iproute2-mpls changes ... | more Change 1311 on 2005/11/23 by jleu@jleu:iproute2-mpls 'Fixes to compile against 2.6.15' Change 1310 on 2005/11/23 by jleu@jleu:iproute2-mpls 'Finish converting from SHIM to ' Change 1302 on 2005/11/17 by jleu@jleu:iproute2-mpls 'Allow for using an environment ' Change 1301 on 2005/11/17 by jleu@jleu:iproute2-mpls 'Convert to generic netlink syst' Change 1288 on 2005/11/01 by jleu@jleu:iproute2-mpls 'Update mpls.h to latest from mp' Change 1285 on 2005/10/25 by jleu@jleu:iproute2-mpls 'Correctly parse the args for 'p' Change 1280 on 2005/10/21 by jleu@jleu:iproute2-mpls 'Add support for packet nexthops' Change 1278 on 2005/10/21 by jleu@jleu:iproute2-mpls 'Update the help to reflect the ' Change 1277 on 2005/10/21 by jleu@jleu:iproute2-mpls 're-enable tunnel commands, but ' Change 1268 on 2005/10/15 by jleu@jleu:iproute2-mpls 'make sure mpls/mpls get added t' Change 1264 on 2005/10/14 by jleu@jleu:iproute2-mpls 'integ RPM build infrastructure ' Change 1258 on 2005/10/14 by jleu@jleu:iproute2-mpls 'my currenty shim target work gr' Change 1249 on 2005/10/09 by jleu@jleu:iproute2-mpls 'Change shim parsing. Now the d' Change 1248 on 2005/10/09 by jleu@jleu:iproute2-mpls 'Use the new change flag to conv' Change 1236 on 2005/10/04 by jleu@jleu:iproute2-mpls 'Fix the dump processi= ng ' Change 1229 on 2005/09/19 by jleu@jleu:iproute2-mpls 'Switch from RTA_SPEC_* to RTA_S' Change 1227 on 2005/09/16 by jleu@jleu:iproute2-mpls 'Convert mpls_monitor to SHIM ' Change 1226 on 2005/09/16 by jleu@jleu:iproute2-mpls 'Modify makefile to compile the ' Change 1225 on 2005/09/16 by jleu@jleu:iproute2-mpls 'Convert mpls utility to use SHI' Change 1224 on 2005/09/16 by jleu@jleu:iproute2-mpls 'Add MPLS and SHIM related userl' Change 1223 on 2005/09/16 by jleu@jleu:iproute2-mpls 'Update rtnetlink with RTM_SHIM ' Change 1192 on 2005/08/25 by jleu@jleu:iproute2-mpls 'Integrate changes for FC4's ipr' Change 1157 on 2005/05/25 by jleu@jleu:iproute2-mpls-1.1 'This patch is from Vincent Untz' Change 1076 on 2005/01/22 by jleu@jleu:iproute2-mpls-1.1 'Add mpls-linux version to the o' Change 1066 on 2005/01/13 by jleu@jleu:iproute2-mpls-1.1 'I forgot to convert ALL the tun' Change 1056 on 2005/01/08 by jleu@jleu:iproute2-mpls-1.1 'Clean up the traffic stats outp' Change 1053 on 2005/01/06 by jleu@jleu:iproute2-mpls-1.1 'Convert to use mpls_tunnel_req ' Change 1051 on 2005/01/05 by jleu@jleu:iproute2-mpls-1.1 'remove mpls_util.[ch] we do not' Change 1045 on 2005/01/04 by jleu@jleu:iproute2-mpls-1.1 'Implement the rest of the MPLS ' Change 1040 on 2004/12/30 by jleu@jleu:iproute2-mpls-1.1 'Conditionally define AF_MPLS ' Change 1039 on 2004/12/30 by jleu@jleu:iproute2-mpls-1.1 'Switch to use AF_MPLS instead o' Change 1038 on 2004/12/30 by jleu@jleu:iproute2-mpls-1.1 'use AF_MPLS instead of PF_MPLS ' Change 1037 on 2004/12/30 by jleu@jleu:iproute2-mpls-1.1 'Add special nexthop defines and' Change 1036 on 2004/12/22 by jleu@jleu:iproute2-mpls-1.1 'Integrate changes for iproute 2' Change 988 on 2004/11/02 by jleu@jleu:iproute2-mpls-1.1 'Only get an answer when adding ' Change 987 on 2004/11/02 by jleu@jleu:iproute2-mpls-1.1 'Correct handling of command lin' Change 931 on 2004/10/10 by jleu@jleu:iproute2-mpls-1.1 'mpls monitor will only show net' Change 930 on 2004/10/10 by jleu@jleu:iproute2-mpls-1.1 'Fix the install target for the ' Change 912 on 2004/09/29 by jleu@jleu:iproute2-mpls-1.1 'get rid of do_mpls(), do the do' Change 906 on 2004/09/23 by jleu@jleu:iproute2-mpls-1.1 'First cut at a mpls monitor ' Change 867 on 2004/09/09 by jleu@jleu:iproute2-mpls-1.1 'Submitted by Christophe Fillot ' Change 832 on 2004/08/25 by jleu@jleu:iproute2-mpls-1.1 'Fix nexthop address handling Re' Change 819 on 2004/08/04 by jleu@jleu:iproute2-mpls-1.1 'Add dumping instructions to the' Change 817 on 2004/08/04 by jleu@jleu:iproute2-mpls-1.1 'Add netlink support for add/del' Change 769 on 2004/07/13 by jleu@jleu:iproute2-mpls-1.1 'Update to iproute-2.4.7-14 (fed' Change 459 on 2003/11/18 by jleu@jleu:iproute2-mpls-1.1 'Branch from iproute2-mpls for c' bbeers@alakazam:~/download/perforce/p4client/iproute2$ does this mean I do or don't have the changes???? > > Also I did some work tonight on modules. I was able to compile > mpls, mpls_tunnel, mpls4, mpls6, ipt_mpls, ebt_mpls as modules > and load them in the correct order and get a functional MPLS stack. > So make sure to sync your mpls-kernel tree and rebuild (optionally > with MPLS compiled as a module) Great! I'll give it a try, I would prefer modules, as I have different targets with only one (so far) wanting MPLS. This thread no longer matches the subject, would you prefer I start anew in mpls-linux-users? -- -Bob |
×
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