Re: [mpls-linux-devel] mpls-linux on 64 bit kernel
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-devel] mpls-linux on 64 bit kernel
|
From: Chris R. <Chr...@nr...> - 2010-05-18 15:29:16
|
Jorge
Oops.... cut&pasted wrong show statement it should have been:
# ip route show
10.50.110.0/24 via 10.50.1.2 dev eth1 mpls 0x2
Also here is a debug dump, doesnt seem to show anything related......
kernel: MPLS mpls_skb_dump: from eth1 with len 88 (1832)headroom=48
tailroom=1464
Further, the ping from Host B is "ping -I 10.50.110.1 10.50.210.1"
Note also, with "ping 10.50.210.1" from Host B the results are the same
- no reply. Iptables is turned off so it isn't filters. Its like the
packet labels are getting popped and then the packet is dropped? More
hunting to do yet......
HERE is a wireshark dump from Host A of the receiving packet from Host
B's ping
No. Time Source Destination Protocol
Info
46 486.578136 10.50.110.1 10.50.210.1
ICMP Echo (ping) request
Frame 46 (102 bytes on wire, 102 bytes captured)
Ethernet II, Src: MagicCon_00:47:5e (00:05:1b:00:47:5e), Dst:
MagicCon_70:e9:37 (00:05:1b:70:e9:37)
MultiProtocol Label Switching Header, Label: 2000, Exp: 0, S: 1, TTL: 64
MPLS Label: 2000
MPLS Experimental Bits: 0
MPLS Bottom Of Label Stack: 1
MPLS TTL: 64
Internet Protocol, Src: 10.50.110.1 (10.50.110.1), Dst: 10.50.210.1
(10.50.210.1)
Internet Control Message Protocol
Type: 8 (Echo (ping) request)
Code: 0 ()
Checksum: 0x05d9 [correct]
Identifier: 0xa516
Sequence number: 12 (0x000c)
Data (56 bytes)
0000 a7 b0 f2 4b 00 00 00 00 ee 34 06 00 00 00 00 00 ...K.....4......
0010 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f ................
0020 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f !"#$%&'()*+,-./
0030 30 31 32 33 34 35 36 37
...Chris
On 05/18/2010 11:03 AM, Jorge Boncompte [DTI2] wrote:
> El 18/05/2010 16:48, Chris Robson escribió:
>
>> Hi Jorge
>>
>> Good and bad news.
>>
>> Good news is the lock up is fixed. I can see, via wireshark and debug,
>> ping packets being received without the system locking.
>>
>> Bad news is, the reply is not going out. Although, I'm not sure the
>> back-to-back host configuration is correct so that maybe the reason.
>> ergo here is what is configured:
>>
>>
>> Host A: eth1 - 10.50.1.1/24
>> eth0:1 - 10.50.210.1/24
>> /sbin/mpls labelspace set dev eth1 labelspace 0
>> LSPKey=`/sbin/mpls nhlfe add key 0 instructions push gen
>> 1000 nexthop eth1 ipv4 10.50.1.2 | grep key | cut -c 17-26`
>> /sbin/ip route add 10.50.110.0/24 via 10.50.1.2 mpls $LSPKey
>> /sbin/mpls ilm add label gen 2000 labelspace 0
>>
>> Host B: eth1 - 10.50.1.2/24
>> eth0:1 - 10.50.110.1/24
>> /sbin/mpls labelspace set dev eth1 labelspace 0
>> LSPKey=`/sbin/mpls nhlfe add key 0 instructions push gen
>> 2000 nexthop eth1 ipv4 10.50.1.1 | grep key | cut -c 17-26`
>> /sbin/ip route add 10.50.210.0/24 via 10.50.1.1 mpls $LSPKey
>> /sbin/mpls ilm add label gen 1000 labelspace 0
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>> +++++++++++++++++++++++++++++++++++++++++++
>> Host A configuration info:
>>
>> eth0 Link encap:Ethernet HWaddr 00:21:86:52:8D:E4
>> inet addr:10.128.112.6 Bcast:10.128.112.255 Mask:255.255.255.0
>> inet6 addr: fe80::221:86ff:fe52:8de4/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:512 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:666 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:70643 (68.9 KiB) TX bytes:84260 (82.2 KiB)
>> Memory:fa200000-fa220000
>>
>> eth0:1 Link encap:Ethernet HWaddr 00:21:86:52:8D:E4
>> inet addr:10.50.110.1 Bcast:10.50.110.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> Memory:fa200000-fa220000
>>
>> eth1 Link encap:Ethernet HWaddr 00:05:1B:00:47:5E
>> inet addr:10.50.1.2 Bcast:10.50.1.255 Mask:255.255.255.0
>> inet6 addr: fe80::205:1bff:fe00:475e/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:19 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:3469 (3.3 KiB) TX bytes:5209 (5.0 KiB)
>>
>> # mpls nhlfe show
>> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>> push gen 2000 set eth1 ipv4 10.50.1.1 (0 bytes, 0 pkts)
>> # mpls ilm show
>> ILM entry label gen 1000 labelspace 0 proto ipv4
>> pop peek (0 bytes, 0 pkts)
>> # ip route show
>> 10.50.210.0/24 via 10.50.1.1 dev eth1 mpls 0x2
>>
> This is wrong... shouldn't it be 10.50.1.2?
>
>
>> ++++++++++++++++++++++++++++++++++++++++++++
>> ++++++++++++++++++++++++++++++++++++++++++++
>>
>> Host B configuration dump:
>>
>> eth0 Link encap:Ethernet HWaddr 00:21:86:52:8D:E4
>> inet addr:10.128.112.6 Bcast:10.128.112.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:947 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:1293 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:141125 (137.8 KiB) TX bytes:156121 (152.4 KiB)
>> Memory:fa200000-fa220000
>>
>> eth0:1 Link encap:Ethernet HWaddr 00:21:86:52:8D:E4
>> inet addr:10.50.110.1 Bcast:10.50.110.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> Memory:fa200000-fa220000
>>
>> eth1 Link encap:Ethernet HWaddr 00:05:1B:00:47:5E
>> inet addr:10.50.1.2 Bcast:10.50.1.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:20 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:3551 (3.4 KiB) TX bytes:5209 (5.0 KiB)
>>
>> # mpls nhlfe show
>> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>> push gen 2000 set eth1 ipv4 10.50.1.1 (1260 bytes, 15 pkts)
>> [root@FARP ~]# mpls ilm show
>> ILM entry label gen 1000 labelspace 0 proto ipv4
>> pop peek (0 bytes, 0 pkts)
>>
> Have you copy&pasted the configuration because it looks the same.
>
>
|
