Shadowing Practice: Traceroute (tracert) Explained - Network Troubleshooting - Learn English Speaking with Video

בחר מצב תרגול

כל מצב פותח חדר תרגול במסך מלא.

101 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
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 מילים לתרגול Shadowing. הדיבור נמשך 9:22. הדובר מדבר בקצב טבעי של כ-158 מילים בדקה, קרוב לשיחה יומיומית. רק 81% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר. 2 מתוך 11 המשפטים שלו הם שאלות, כך שזה תרגול טוב לאינטונציה של שאלות ולתשובות קצרות.

אוצר מילים מרכזי בסרטון הזה

15 מילים מהסרטון שכדאי ללמוד, עם ההגייה והמשמעות שלהן:

מילההגייהמשמעות
packet שם עצם/ˈpæk.ɪt/חֲבִילָה
destination שם עצם/dɛstɪˈneɪʃən/יַעַד
server שם עצם/ˈsɝvɚ/שָׁרָת
domain שם עצם/ˌdəʊˈmeɪ̯n/תְּחוּם
consistent שם תואר/kənˈsɪs.tənt/עקבי ikví
column שם עצם/ˈkɒləm/עַמּוּד
topic שם עצם/ˈtɑpɪk/נוֹשֵׂא
necessarily תואר הפועל/ˌnɛs.əˈsɛɹ.ə.li/בהכרח
compare פועל/kəmˈpɛɚ/השווה \ הִשְׁוָה
curious שם תואר/ˈkjʊɹ.i.əs/סַקְרָן, סקרנית
custom שם עצם/ˈkʌstəm/מִנְהָג
conclusion שם עצם/kənˈkluːʒən/מסקנה
default שם עצם/dɪˈfɔlt/ברירת מחדל
keyboard שם עצם/ˈki.bɔɹd/מִקְלֶדֶת
continent שם עצם/ˈkɑntɪnənt/יַבֶּשֶׁת

דקדוק בסרטון הזה

המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:

מבנהבסרטון
סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולהis taken · is measured · wasn't configured
משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר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/

צלילים שדוברי עברית מתקשים בהם:

  • /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: packet /ˈpæk.ɪt/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, gradually /ˈɡɹæd͡ʒuəli/, examine /ɪɡˈzæmɪn/, gradual /ˈɡɹæd͡ʒuəl/
  • /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: trace /tɹeɪs/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/, curious /ˈkjʊɹ.i.əs/, roughly /ˈɹʌf.li/
  • /ŋ/ בסוף מילה — צליל אפי בלי “ג” בסוף: ping /pɪŋ/, timing /ˈtaɪmɪŋ/

איך לתרגל עם הסרטון הזה

  1. הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
  2. התחילו במהירות 0.75×, תרגלו Shadowing משפט אחר משפט, וחזרו למהירות רגילה כשזה מרגיש קל.
  3. הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו packet, destination, server.

מהי טכניקת השאדואינג?

שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.

טכניקת Shadowing: קרא את המדריך המלא שלב אחר שלב →