シャドーイング練習: 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発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える

同じチャンネル

FOR YOU

おすすめ動画

このレッスンの語彙とスピーキングのポイント

このスピーキングレッスンは、動画「Traceroute (tracert) Explained - Network Troubleshooting」を教材にしています。 繰り返し出てくる語は次のとおりです:packet, router, traceroute, destination, trip。 この動画には、シャドーイング用の文が11文、単語が1477語あります。 音声の長さは9:22です。 話す速さは1分あたり約158語で、日常会話に近い自然なペースです。 英語の頻出3,000語に含まれる単語は81%だけなので、語彙は難しめです。 全11文のうち2文が疑問文なので、疑問文のイントネーションや短い受け答えの練習に向いています。

この動画の重要語彙

動画に出てくる覚えておきたい単語15語を、発音と意味つきで紹介します。

単語発音意味
packet 名詞/ˈpæk.ɪt/パケット, 小包
destination 名詞/dɛstɪˈneɪʃən/目的地
server 名詞/ˈsɝvɚ/サーバー
hop 名詞/hɒp/ホップ
indicate 動詞/ˈɪndɪˌkeɪt/示す, 指す
utility 名詞/juːˈtɪlɪti/有用, 有用性
column 名詞/ˈkɒləm/柱
timing 名詞/ˈtaɪmɪŋ/タイミング
communicate 動詞/kəˈmjuːnɪkeɪt/伝える
trace 名詞/tɹeɪs/跡, 痕跡
topic 名詞/ˈtɑpɪk/話題, テーマ
naturally 副詞/ˈnæt͡ʃ.(ə.)ɹə.li/勿論
compare 動詞/kəmˈpɛɚ/比べる, 比較する
curious 形容詞/ˈkjʊɹ.i.əs/好奇心の強い, 知りたがる
custom 名詞/ˈkʌstəm/習慣, 風俗

動画に出てくる句動詞

単語発音意味
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

注意したい発音

話し手はit'll, I'm, doesn'tなど、短縮形や弱形を16回使っています。聞こえたとおりの短い形で発音しましょう。

  • 「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/

日本語話者が苦手な音:

  • /r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/, roughly /ˈɹʌf.li/, gradually /ˈɡɹæd͡ʒuəli/, gradual /ˈɡɹæd͡ʒuəl/
  • /f/ — 「フ」ではなく、上の歯と下唇で出す: roughly /ˈɹʌf.li/, default /dɪˈfɔlt/, configure /kənˈfɪɡə(ɹ)/
  • 子音の連続 — 間に母音を入れない: consistent /kənˈsɪs.tənt/, trace /tɹeɪs/, curious /ˈkjʊɹ.i.əs/, conclusion /kənˈkluːʒən/, default /dɪˈfɔlt/

この動画での練習方法

  1. まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
  2. まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
  3. 自分の声を録音して元の音声と比べます。packet, destination, serverなどの単語に特に注意しましょう。

シャドーイングとは?英語上達に効果的な理由

シャドーイング(Shadowing)は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的:ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影(shadow)」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →