[mpls-linux-general] problems with static label configuration
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
[mpls-linux-general] problems with static label configuration
|
From: Maic G. <ma...@ha...> - 2007-05-04 14:52:03
|
Hallo,
I have some problems with quagga, ldp and mpls. I also have some problems w=
ith
the static label configuration.
I have a fedora core 5 (thanks to Marco Schmidt) and install all the rpm=EF=
s
from sf for the version 1.955.
So first the static label configuration problem:
I do:
Mpls labelspace show
I got:
LABELSPACE entry dev lo labelspace -1
LABELSPACE entry dev eth0 labelspace 20
LABELSPACE entry dev sit0 labelspace -1
I do:
Mpls nhlfe add key 0 instructions push gen 1100 nexthop eth0 ipv4 10.0.0.15
I got:
NHLFE entry key 0x4 mtu 0 propagate_ttl
(0 bytes, 0 pkts)
I got in dmsg:
unk.c:297:genl_mpls_nhlfe_new: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:394:mpls_add_out_label: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:130:nhlfe_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:115:nhlfe_dst_gc: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:116:nhlfe_dst_gc: exit
MPLS DEBUG net/mpls/mpls_nhlfe.c:151:nhlfe_dst_alloc: exit
MPLS DEBUG net/mpls/mpls_netlink.c:274:mpls_nhlfe_event: enter
MPLS DEBUG net/mpls/mpls_netlink.c:234:mpls_fill_nhlfe: enter
MPLS DEBUG net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter
MPLS DEBUG net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit
MPLS DEBUG net/mpls/mpls_netlink.c:258:mpls_fill_nhlfe: exit
MPLS DEBUG net/mpls/mpls_netlink.c:288:mpls_nhlfe_event: exit
MPLS DEBUG net/mpls/mpls_nhlfe.c:451:mpls_add_out_label: exit
MPLS DEBUG net/mpls/mpls_opcode.c:345:mpls_build_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:356:mpls_build_opcode_push: exit
MPLS DEBUG net/mpls/mpls_opcode.c:1035:mpls_build_opcode_set: enter
MPLS DEBUG net/mpls/mpls_dst.c:169:mpls_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_dst.c:216:mpls_dst_alloc: exit(00000000)
MPLS DEBUG net/mpls/mpls_opcode.c:1080:mpls_build_opcode_set: SET error
building DST info
MPLS DEBUG net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit
MPLS DEBUG net/mpls/mpls_instr.c:89:mpls_instrs_free: enter
MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
MPLS DEBUG net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit
MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
MPLS DEBUG net/mpls/mpls_instr.c:95:mpls_instrs_free: exit
MPLS DEBUG net/mpls/mpls_netlink.c:334:genl_mpls_nhlfe_new: Exit: -1
I do:
Ip route add 192.168.30.0/24 via 10.0.0.15 mpls 4
I got no message -> every think is ok
I got in dmsg:
No message -> every think is ok
I do a:
ip route show
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1
192.168.30.0/24 via 10.0.0.15 dev eth0 mpls 0x4
169.254.0.0/16 dev eth0 scope link
-> every think is ok
I do:
ping -c 2 192.168.30.1
PING 192.168.30.1 (192.168.30.1) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
--- 192.168.30.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 20014ms
I got a mistake
I got in dmsg:
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev1: claim the port first
ppdev2: claim the port first
ppdev3: claim the port first
MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu: =
0
dst: c805ed80
MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu: =
0
dst: c805ed80
MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
Where is the problem? Weeks ago I use an open suse and patch the mpls code
into the kernel and every think works fine. Now I take the kernel form the
linux-mpls project and it does not work.
Please help me.
--------------------------------------------
Maic Groffmann
email: ma...@ha...
|
