作者wst2080 ()
看板Network
标题Re: [问答] traceroute问题
时间Mon Nov 22 20:31:20 2010
跑的架构
Switch → R0 → R1 → R2 → R3 → R5 → R4
架构的IP:
Switch: 1.1.1.10
R0's LAN: 1.1.1.1
R0's S0/0: 100.100.100.100
R1's S0/1: 100.100.100.1
R1's S0/0: 12.1.1.1
R2's S0/1: 12.1.1.2
R2's S0/0: 23.1.1.2
R3's S0/1: 23.1.1.3
R3's S0/0: 35.1.1.3
R5's S0/1: 35.1.1.5
R5's S1/0: 54.1.1.5
R4's S1/0: 54.1.1.4
来源:
Switch# traceroute 54.1.1.4
Type escape sequence to abort.
Tracing the route to
01:03:54: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:03:57: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:00: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
54.1.1.4
1
01:04:03: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:03: IP: s=1.1.1.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:03: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 66, sending broad/multicast
01:04:06: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 66, sending broad/multicast
01:04:09: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 66, sending broad/multicast
1.1.1.1 2 msec 3 msec 5 msec
2
01:04:12: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:12: IP: s=1.1.1.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:12: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:12: IP: s=1.1.1.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:12: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:12: IP: s=100.100.100.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:12: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 72, sending broad/multicast
01:04:15: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 72, sending broad/multicast
01:04:18: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 72, sending broad/multicast
100.100.100.1 19 msec 18 msec 16 msec
3
01:04:21: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:21: IP: s=100.100.100.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:21: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:21: IP: s=100.100.100.1 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:21: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:21: IP: s=12.1.1.2 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:21: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:24: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:27: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
12.1.1.2 31 msec 29 msec 31 msec
4
01:04:30: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:30: IP: s=12.1.1.2 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:30: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:30: IP: s=12.1.1.2 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:30: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:30: IP: s=23.1.1.3 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:30: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:33: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:36: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
23.1.1.3 42 msec 42 msec 45 msec
5
01:04:39: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:39: IP: s=23.1.1.3 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:39: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:39: IP: s=23.1.1.3 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:39: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:39: IP: s=35.1.1.5 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:39: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:42: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:45: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
35.1.1.5 55 msec 55 msec 55 msec
6
01:04:48: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:48: IP: s=35.1.1.5 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:48: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:48: IP: s=35.1.1.5 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:48: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:48: IP: s=54.1.1.4 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:48: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:51: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
01:04:54: IP: s=1.1.1.10 (local), d=255.255.255.255 (VLAN1), len 67, sending broad/multicast
54.1.1.4 71 msec 76 msec *
01:04:57: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
01:04:57: IP: s=54.1.1.4 (VLAN1), d=1.1.1.10, len 56, rcvd 1
01:04:57: IP: s=1.1.1.10 (local), d=54.1.1.4 (VLAN1), len 28, sending
R0的讯息:
*Mar 1 01:13:15.641: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:18.645: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:21.646: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:24.651: IP: s=1.1.1.1 (local), d=1.1.1.10 (FastEthernet0/1), len 56, sending
*Mar 1 01:13:24.659: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 66, rcvd 2
*Mar 1 01:13:27.660: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 66, rcvd 2
*Mar 1 01:13:30.669: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 66, rcvd 2
*Mar 1 01:13:33.670: IP: s=1.1.1.1 (local), d=1.1.1.10 (FastEthernet0/1), len 56, sending
*Mar 1 01:13:33.674: IP: s=1.1.1.1 (local), d=1.1.1.10 (FastEthernet0/1), len 56, sending
*Mar 1 01:13:33.698: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 72, rcvd 2
*Mar 1 01:13:36.703: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 72, rcvd 2
*Mar 1 01:13:39.708: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 72, rcvd 2
*Mar 1 01:13:42.777: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:45.782: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:48.787: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:51.896: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:54.901: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:13:57.906: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:01.051: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:04.068: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:07.105: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:10.258: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:13.263: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
*Mar 1 01:14:16.268: IP: s=1.1.1.10 (FastEthernet0/1), d=255.255.255.255, len 67, rcvd 2
途中每一台的Router(R1,R2,R3,R5):
(都会有这样的回应~~~ 回应给来源端!!!)
*Mar 1 01:13:56.448: ICMP: time exceeded (time to live) sent to 1.1.1.10 (dest was 54.1.1.4)
*Mar 1 01:14:05.483: ICMP: time exceeded (time to live) sent to 1.1.1.10 (dest was 54.1.1.4)
*Mar 1 01:14:05.499: ICMP: time exceeded (time to live) sent to 1.1.1.10 (dest was 54.1.1.4)
目的端的Router(R4):
*Mar 1 01:14:08.949: UDP: rcvd src=1.1.1.10(36886), dst=54.1.1.4(33449), length=8
*Mar 1 01:14:08.949: ICMP: dst (54.1.1.4) port unreachable sent to 1.1.1.10
*Mar 1 01:14:18.031: UDP: rcvd src=1.1.1.10(35474), dst=54.1.1.4(33450), length=8
*Mar 1 01:14:18.035: ICMP: dst (54.1.1.4) port unreachable sent to 1.1.1.10
*Mar 1 01:14:18.108: UDP: rcvd src=1.1.1.10(33969), dst=54.1.1.4(33451), length=8
PS: 由於每次traceroute都会有三次测试~ 所以会有三次一样的纪录出现!!!
(我把Run出来的结果po出来~你自己去分析看看!!!)
※ 引述《jeffccc (奇蹟の苏生)》之铭言：
: 请问一下traceroute为什麽可以找到完整路径呢?
: 因为他送出去的封包应该只能放九个IP ADDR
: 要是目的地的距离超过九个ROUTER的话
: 後面的ROUTER要记录在哪里?
与这个无关~~~ 路由器的多寡 不影响traceroute的跑法~~~ 前一张的推文已经提到了!!!
: 例如现在找到了R1~R10共10个router,但还没到达目的地
: traceroute下一个要送的封包里面的路径该怎麽写?
: 写R2~R10吗?
: 还是只写一个R10?
只要写目的地就好~~~ 你又不知道每一台的路由怎麽跑~ 只要知道目的就好~
该怎麽去~ 就是路由器之间的路由来决定封包怎麽跑~~~
1F：→ wst2080:记得去画一张图 然後把Switch po出来的结果 一一的去推敲 11/22 20:45
2F：→ wst2080:相信你会对这些Traceroute的流程会更加的了解 11/22 20:45
※ 编辑: wst2080 来自: 122.116.248.253 (11/22 20:48)
※ 编辑: wst2080 来自: 122.116.248.253 (11/22 20:48)
3F：推 jeffccc:如果是这例子当然浅显易懂,不过问题是有多个路径的话,你 11/22 21:22
4F：→ jeffccc:怎麽知道你送第一个封包(ttl=1)还有第10个封包(ttl=10)会 11/22 21:23
5F：→ jeffccc:从相同的router走?我想是不是要把经过的router标在header 11/22 21:24
6F：→ jeffccc:中,让router可以根据header中的位址送封包 11/22 21:25
7F：→ jeffccc:因为每次封包走的路径都不同,但是traceroute送出的封包又 11/22 21:26
8F：→ jeffccc:不只是一个,他要是每个封包都走不同路径怎办 11/22 21:26
9F：→ wst2080:路由器收到封包 决定的并不是封包 而是路由器 懂吗??? 11/22 22:22
10F：→ wst2080:多条路径不会影响封包的传递 而是路由的选择而已 11/22 22:23
11F：→ wst2080:而路由器收到封包 看的是 目标 这样~~~ 懂吗??? 11/22 22:23
12F：→ wst2080:明天我再抽空Run看看你说的附载平衡 把结果po出来 11/22 23:55
13F：→ wst2080:或许我说的部份 你就会懂了 11/22 23:55
14F：→ wst2080:负载平衡 11/22 23:55