Re: [問答] traceroute問題

看板Network作者時間15年前 (2010/11/22 20:31), 編輯推噓1(1推 0噓 13→)
留言14則, 2人參與, 最新討論串2/9 (看更多)
跑的架構 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? 只要寫目的地就好~~~ 你又不知道每一台的路由怎麼跑~ 只要知道目的就好~ 該怎麼去~ 就是路由器之間的路由來決定封包怎麼跑~~~
→
11/22 20:45, , 1F
記得去畫一張圖 然後把Switch po出來的結果 一一的去推敲
11/22 20:45, 1F
→
11/22 20:45, , 2F
相信你會對這些Traceroute的流程會更加的了解
11/22 20:45, 2F
※ 編輯: wst2080 來自: 122.116.248.253 (11/22 20:48) ※ 編輯: wst2080 來自: 122.116.248.253 (11/22 20:48)
推
11/22 21:22, , 3F
如果是這例子當然淺顯易懂,不過問題是有多個路徑的話,你
11/22 21:22, 3F
→
11/22 21:23, , 4F
怎麼知道你送第一個封包(ttl=1)還有第10個封包(ttl=10)會
11/22 21:23, 4F
→
11/22 21:24, , 5F
從相同的router走?我想是不是要把經過的router標在header
11/22 21:24, 5F
→
11/22 21:25, , 6F
中,讓router可以根據header中的位址送封包
11/22 21:25, 6F
→
11/22 21:26, , 7F
因為每次封包走的路徑都不同,但是traceroute送出的封包又
11/22 21:26, 7F
→
11/22 21:26, , 8F
不只是一個,他要是每個封包都走不同路徑怎辦
11/22 21:26, 8F
→
11/22 22:22, , 9F
路由器收到封包 決定的並不是封包 而是路由器 懂嗎???
11/22 22:22, 9F
→
11/22 22:23, , 10F
多條路徑不會影響封包的傳遞 而是路由的選擇而已
11/22 22:23, 10F
→
11/22 22:23, , 11F
而路由器收到封包 看的是 目標 這樣~~~ 懂嗎???
11/22 22:23, 11F
→
11/22 23:55, , 12F
明天我再抽空Run看看你說的附載平衡 把結果po出來
11/22 23:55, 12F
→
11/22 23:55, , 13F
或許我說的部份 你就會懂了
11/22 23:55, 13F
→
11/22 23:55, , 14F
負載平衡
11/22 23:55, 14F
‣ 更多 wst2080 的文章
文章代碼(AID): #1CwcAQ6F (Network)
討論串 (同標題文章)
以下文章回應了本文：
完整討論串 (本文為第 2 之 9 篇)：
排序： 最新先 | 最舊先 | 留言數
在新視窗開啟完整討論串 (共9篇)
‣ 更多 wst2080 的文章
文章代碼(AID): #1CwcAQ6F (Network)