Re: [mpls-linux-general] Mpls installation problems with the new version.
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-general] Mpls installation problems with the new version.
|
From: Oliver H. <ho...@tm...> - 2002-08-01 12:00:47
|
Am Mit, 2002-07-31 um 19.51 schrieb James R. Leu: > > I defined a wrong outgoing lable on a edge router, and I saw two things: > > a) Ping is still working, but why? If mpls didn't know the incoming > > label, it pops the label off and tries to find a working label in the > > outgoing labels? Or is the label poped off and forwarded by normal ip? >=20 > I haven't done any negative testing recently, I will try your test tonight. > It shouldn't have worked. >=20 > > b) Tracerout stops at the middle of the lsp (3 PCs). Why it is not > > forwarded like the pings? >=20 > *shrug* Let me figure out what the ping _worked_ first :-) This is my configuration: The way of the ping:=20 obiwan (192.168.2.1) :eth1<-->eth0: amidala (192.168.2.2, 192.168.5.2) :eth1<-->eth1: vader (192.168.5.3) --- [root@obiwan bin]# cat /proc/net/mpls_* 0x40005400 1663/245091/0 gen 21 0 1 POP PEEK=20 eth1 0 12 0x00000008 0/0/0 1 PUSH(gen 99) SET(eth1,192.168.2.2)=20 [root@obiwan bin]# netstat -rn Kernel IP Routentabelle Ziel Router Genmask Flags MSS Fenster irtt Iface 192.168.5.3 192.168.2.2 255.255.255.255 UGH 40 0 0 eth1 --- [root@amidala root]# cat /proc/net/mpls_* 0x40005800 0/0/0 gen 22 0 1 POP FWD(0x00000015)=20 0x4000d000 34/2992/0 gen 52 0 1 POP FWD(0x00000018)=20 eth0 0 12 eth1 0 10 0x00000015 43/3290/0 2 PUSH(gen 53) SET(eth1,192.168.5.3)=20 0x00000018 34/2856/0 2 PUSH(gen 21) SET(eth0,192.168.2.1) [root@amidala root]# netstat -rn Kernel IP Routentabelle Ziel Router Genmask Flags MSS Fenster irtt Iface 192.168.5.3 0.0.0.0 255.255.255.255 UH 40 0 0 eth1 --- [root@vader root]# cat /proc/net/mpls_* 0x4000d400 47/3800/0 gen 53 0 1 POP PEEK=20 0x40012400 4984/438592/0 gen 73 0 1 POP PEEK=20 eth1 0 9 eth2 0 10 0x00000008 4984/418656/0 1 PUSH(gen 74) SET(eth2,192.168.7.4)=20 0x0000000a 37/3108/0 1 PUSH(gen 52) SET(eth1,192.168.5.2) --- [root@obiwan bin]# ping 192.168.5.3 PING 192.168.5.3 (192.168.5.3) from 192.168.2.1 : 56(84) bytes of data. 64 bytes from 192.168.5.3: icmp_seq=3D0 ttl=3D254 time=3D428 usec 64 bytes from 192.168.5.3: icmp_seq=3D1 ttl=3D254 time=3D210 usec 64 bytes from 192.168.5.3: icmp_seq=3D2 ttl=3D254 time=3D250 usec --- [root@obiwan bin]# traceroute 192.168.5.3 traceroute to 192.168.5.3 (192.168.5.3), 30 hops max, 38 byte packets 1 amidala (192.168.2.2) 0.234 ms 0.150 ms 0.126 ms 2 * * * 3 vader-5-3 (192.168.5.3) 0.268 ms 0.214 ms 0.197 ms I get always the * * * ....but its a 100Mbit network.... It will be forwarded too, but 1) with delay and 2) why? --- If you are interessted in the ethereal logm you can find them on http://www.tm.informatik.uni-frankfurt.de/~oliver/mpls/ There are the logs of the ethereal output of amidala-eth0, amidala-eth1 and vader-eth1 during the ping and traceroute. You can see, that I have pushed a label 99 on obiwan, but there is no oncoming label defined on amidala, but the packets are forwarded. Oliver --=20 Dipl.-Inf. Oliver Horvath Johann Wolfgang Goethe-Universit=E4t Tel: 069/798-28358 (Fax: 23340) Institut f=FCr Informatik - Telematik |
