跟读练习: 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秒紧跟说话者的影子。与被动听力或语法练习不同,跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性,语调,节奏,连读,听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →