跟讀練習: Traceroute (tracert) Explained - Network Troubleshooting - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

101 句
如果句子過短或過長,請點選 Edit 進行調整。
1
What is traceroute?
2
So that is the topic of this video.
3
Now traceroute is a command line utility that is used to show the route
4
that is taken by data packets as they travel across the internet to their destination.
5
Now the internet is a global network of routers that allows computers
6
and servers the ability to communicate with each other from all over the world.
7
And these routers communicate with each other so they can direct or route the data packets to their intended destination.
8
And the TraceRoute utility is just a tool
9
that is used to find out the exact path a data packet is taken from the sender to the destination.
10
And by using TraceRoute you can use this tool to help you find problems like bottlenecks,
11
such as why and where a connection to a server might be lagging.
12
Or you can also use it if you're just curious about the path the data packets take to their destination.
13
Now traceroute is a little bit different from doing a ping, because when you ping a server such as google .com,
14
your computer will send out four data packets to the destination and once it reaches the destination, it'll return the data packets back to your computer.
15
So if you received all or some of the data packets back to your computer,
16
then that tells us that there is general connectivity between your computer and the destination.
17
And in addition, it'll also tell us how long the trip took for the data packets to go to
18
and from the destination, which is measured in milliseconds.
19
However, a trace route will tell us more information.
20
So generally speaking, a trace route not only pings the final destination, but it also pings each router on its way to the destination.
21
And it measures the round trip time that the data packets took from each router in the destination.
22
So for example, let's go ahead and trace the route from our computer to a server over the internet.
23
And in this example, I'm using a Microsoft Windows computer.
24
So at a command prompt you would type trace rt space
25
and then the IP address or the host name of the destination.
26
So in this case I'm going to use google .com again and then I'm going to press enter on a keyboard.
27
Then our computer will send three data packets to each router on its way to the destination.
28
And each time the data packets reaches a router on its path,
29
the router will send back the three data packets back to our computer and tell us information about that router, such as the router's IP address,
30
and it'll also tell us the round trip time measured in milliseconds
31
that the three data packets took to and from each router.
32
And now the trace is complete.
33
So now let's examine the final results.
34
Now the first column tells us the number of hops or steps that the route took to the destination, which was a total of eight hops.
35
The next three columns shows us the round trip time each data packet took to each point and back to your computer.
36
So the first row, the data packets only took one millisecond.
37
So the route was very short because it's within my local area network.
38
The first hop was my modem router in my home.
39
But But as you can see, once the data goes out on the internet,
40
the round trip times significantly increase and the further that the data packets have to travel to each router,
41
then naturally the round trip times will gradually increase, with the final destination being the longest round trip time.
42
So the final destination time in a traceroute would be roughly the same time if you were just do a ping,
43
which was 21 milliseconds, because remember a ping only displays the time of the final destination.
44
And the last column tells us the IP addresses of each router and the final destination,
45
and it'll also tell us the domain name if it's available.
46
Now going back to the round trip times,
47
one of the main things that you want to look at when you're doing a trace route are consistent round -trip times.
48
So as you can see, these round -trip times are normal.
49
They are consistent and have a slight gradual increase with no major time increases between the hops.
50
So in another scenario, let's suppose that the Google website is very slow.
51
Now let's go ahead and ping google .com again.
52
And as we get the replies, you'll notice that this time the round -trip times are very high, averaging around 200 milliseconds.
53
So this could indicate a problem because it's rare for timings to be this high.
54
So by doing a ping it can tell us that there is a problem.
55
However, it cannot tell us where the problem lies.
56
So this is where a traceroute can help.
57
A traceroute can pinpoint where the problem lies.
58
So if we traceroute google .com again, and if we look at the final result,
59
it tells us that the problem is out on the internet on the fifth hop, starting with this router right here,
60
which would also affect the remaining path to the server.
61
So we pinpointed that the slow connection or lag is not within our local area network or with the server.
62
The problem is with a router or routers on the internet.
63
So the traceroute utility is a great tool to pinpoint bottlenecks and connection interruptions on a network.
64
Now sometimes if you see high round trip times while doing a traceroute then this doesn't always indicate a problem.
65
So for example if you do another traceroute and
66
if you happen to see a big round trip time in between a hop then this doesn't necessarily mean
67
that there's a problem with the router.
68
It could just mean that the distance between certain routers are thousands of miles apart.
69
For example, where the data has to jump over to another continent.
70
Or sometimes you may see asterisks coming from a router.
71
Now this could indicate that there is a problem with the router
72
or it could also mean that the router is working fine but it wasn't configured to return traceroute replies.
73
But the router still passed on the data packets to the next router.
74
Now as I mentioned earlier, traceroute sends out three data packets to each point on its path.
75
And sometimes you might see a high round trip time compared to the other two on the same hop.
76
Now this is not really a big deal.
77
It just means that something strange has happened to
78
that one data packet because if all three timings were high then that indicates an issue that we discussed earlier.
79
So this is why three data packets are sent so it can isolate false issues.
80
Now there is another value in traceroute called TTL or time to live.
81
TTL is a given value to the data packets on how long they can live before they are discarded.
82
So for example when we do another traceroute and you'll notice that it says over a maximum of 30 hops.
83
So this means that the TTL is set to 30, which is the default value.
84
So if the data packets don't reach their destination after 30 hops, the data packets are dropped.
85
So in another example, let's set the TTL to a custom value of 4.
86
So again in a Windows computer we type tracerrt -h4 and then google .com.
87
So this means that when the data reaches the fourth hop the data packet is dropped and won't continue on.
88
So what is the purpose of having a TTL in the first place?
89
Well having a TTL would prevent a data packet from traveling endlessly around the internet trying to find its destination.
90
Now this can happen if certain routers on the internet were misconfigured.
91
So for example if there was no TTL limit and
92
when we try to do another trace route and
93
if certain routers on the internet were misconfigured the data packets could be caught in an endless loop between these routers.
94
So they would just keep on passing these data packets back to each other forever.
95
And when this happens, it could slow down the internet because these routers are constantly busy dealing with these data packets.
96
So this is why a time limit was placed to keep this from happening and wasting bandwidth.
97
And in conclusion, Traceroute can be run on different operating systems.
98
In Windows, you type Traceroute and then the domain name
99
or IP address and in Mac or Linux systems you type traceroute and then the domain name or IP address.
100
So thank you everyone for watching this video on traceroute.
101
Please subscribe, follow me on Twitter and thank you for watching.

下載應用

流利口語所需的一切

AI 發音評分逐句打分
音標練習掌握每個音
詞彙學習建立你的詞庫
詞彙遊戲邊玩邊學

同頻道

FOR YOU

推薦影片

本課的詞彙與口語要點

這節口語課以影片“Traceroute (tracert) Explained - Network Troubleshooting”為素材。 影片中反覆出現的詞有:packet, router, traceroute, destination, trip。 這段影片共有 11 個句子、1477 個單詞可供跟讀。 講話部分時長為 9:22。 說話人語速自然,每分鐘約 158 個詞,接近日常對話。 只有 81% 的單詞屬於英語最常用的 3,000 詞,詞彙難度較高。 全部 11 個句子中有 2 個是問句,適合練習疑問語調和簡短回答。

影片中的重點詞彙

影片中 15 個值得學習的單詞,附發音和釋義:

單詞發音釋義
packet 名詞/ˈpæk.ɪt/包, 小包
destination 名詞/dɛstɪˈneɪʃən/目的地
ping 動詞/pɪŋ/ping
server 名詞/ˈsɝvɚ/伺服器 /伺服器, 伺服器
hop 名詞/hɒp/蛇麻草, 啤酒花
indicate 動詞/ˈɪndɪˌkeɪt/表明, 表示
domain 名詞/ˌdəʊˈmeɪ̯n/領域 /領域
utility 名詞/juːˈtɪlɪti/效用, 用處 /用處
consistent 形容詞/kənˈsɪs.tənt/一貫的 /一貫的
column 名詞/ˈkɒləm/柱子, 柱
trace 名詞/tɹeɪs/痕跡 /痕跡
topic 名詞/ˈtɑpɪk/主題 /主題, 話題 /話題
necessarily 副詞/ˌnɛs.əˈsɛɹ.ə.li/必然地, 必定地
compare 動詞/kəmˈpɛɚ/比, 比較 /比較
curious 形容詞/ˈkjʊɹ.i.əs/好奇, 有好奇心

影片中出現的短語動詞

單詞發音釋義
go ahead 動詞/ˌɡoʊ əˈhɛd/請便 /請便
find out 動詞找出, 查明
slow down 動詞減速 /減速, 放慢

影片中的語法

說話人最常用的結構,並附上影片中的原話:

結構影片中的用法
被動語態 be + 過去分詞 — 強調發生了什麼,而不是誰做的is taken · is measured · wasn't configured
定語從句 who / which + 從句 — 補充說明人或事物destination, which is · destination, which was

需要注意的發音

說話人用了 16 次縮略和弱讀形式,例如 it'll, I'm, doesn't。請按聽到的簡短形式來說。

  • “sh” 和 “zh” 音: destination /dɛstɪˈneɪʃən/, conclusion /kənˈkluːʒən/, interruption /ˌɪntəˈɹʌpʃən/
  • 長單詞——注意重音位置: destination /dɛstɪˈneɪʃən/, utility /juːˈtɪlɪti/, communicate /kəˈmjuːnɪkeɪt/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/

中文母語者容易讀錯的音:

  • 詞尾子音 — 要讀清楚,後面不要加母音: packet /ˈpæk.ɪt/, hop /hɒp/, indicate /ˈɪndɪˌkeɪt/, consistent /kənˈsɪs.tənt/, communicate /kəˈmjuːnɪkeɪt/
  • /r/ 和 /l/ 的區別: naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/, roughly /ˈɹʌf.li/, gradually /ˈɡɹæd͡ʒuəli/, gradual /ˈɡɹæd͡ʒuəl/
  • /æ/ — 嘴張大,不要讀成 /e/: packet /ˈpæk.ɪt/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, gradually /ˈɡɹæd͡ʒuəli/, examine /ɪɡˈzæmɪn/, gradual /ˈɡɹæd͡ʒuəl/

如何用這段影片練習

  1. 先完整聽一遍影片,不要開口,記下不認識的單詞。
  2. 先用 0.75 倍速逐句跟讀,熟練之後再回到正常速度。
  3. 錄下自己的聲音並與原聲對比,特別注意 packet, destination, ping 這類單詞。

什麼是跟讀法?

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧,最初開發用於專業口譯員的培訓,並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大:您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同,跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性,語調,節奏,連讀,聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →