跟读练习: Traceroute: You're Probably Reading the Results Wrong - 通过视频学习英语口语

选择练习模式

每种模式都会打开全屏练习室。

54 句

如果句子过短或过长，请点击 Edit 进行调整。

If you work in IT, you've probably used Traceroute at least a few times, but I bet some of you have no idea how it actually works.

It's one of the first tools we reach for when we're trying to figure out where a network connection is dying.

You run it, you see a list of hops, you find out where it times out, and you're basically done.

But there's some really cool stuff happening underneath the hood that changes how you should actually interpret those results.

Okay, so at its core, traceroute is exploiting something called the TTL field in the IP header.

TTL stands for time to live, and it's basically a hop counter.

Every time a packet passes through a router, that router reduces the TTL by one.

When the TTL hits zero, the router drops the packet and sends back an ICMP time exceeded message to the source.

Now, I know that just sounded like a lot, but stick with me.

This is all gonna make sense in a minute.

Trust me.

Okay?

All right.

Now, traceroute starts by sending out a packet with a TTL of 1.

That packet hits the first router.

The router reduces the TTL to zero, drops it, and then sends back the time-exceeded message.

And then boom, now Traceroute knows the IP address of the first hop and how long it took to get there.

Then it sends out another packet with a TTL of two.

That packet makes it to the first router, hits the second router, gets dropped, and then the second router sends back a time exceeded message.

Now, Traceroute knows the second hop.

I think you can see where I'm going with this.

It keeps doing this, incrementing the TTL each time until it finally reaches the destination.

Now, but you might be asking, how does it know what hop is the destination?

Well, that's a very good question.

It knows this because at the last hop, instead of getting an ICMP time exceeded, it gets an ICMP echo reply or port unreachable message.

It kind of depends on the protocol you're using, but that's how it knows it's done.

Now, here is where it gets interesting.

Traceroute on Windows and Traceroute on Linux work differently by default.

Windows uses ICMP echo requests,

basically a ping packet, and Linux and Unix use UDP packets to high numbered ports.

Now you might be asking, why does that matter?

Well, it's because firewalls and routers treat these differently.

A lot of networks block ICMP, or at least they rate limit it, so that they deprioritize that traffic.

So if you're running traceroute on Windows and you're seeing a bunch of timeouts, it might not actually be because the path is broken.

It might be because the ICMP is being filtered somewhere along the way.

If you run the same traceroute using UDP or TCP, you might get a completely different result.

And also, this is really important.

The path you see in traceroute is not necessarily the path your actual traffic is taking.

Routers can use different paths for different types of traffic.

They can use something called ECMP or equal cost multipath, meaning there might be multiple paths to the same destination

and your trace route packets might take a different path than your actual application traffic.

Oh, one more thing.

Those round trip times you see in trace route, they're not cumulative.

Each hop shows the round trip time from your source to that specific router and back.

So if you see hop three with a 20 milliseconds time and a hot four with a 15 milliseconds, that doesn't mean hot four is faster.

That just means hot four responded faster to the ICMP request.

The actual latency is still accumulating as you go.

So what do you actually need to remember?

Traceroute is an amazing tool, but you need to understand what it's actually showing you.

It's not a perfect map of your traffic path.

And those timeouts don't always mean there's a problem.

Sometimes you need to run it with different protocols or run it multiple times to see if the path changes.

Now you know how traceroute actually works under the hood.

I hope that helped and don't forget to follow me nerds.

下载应用

流利口语所需的一切

AI 发音评分逐句打分

音标练习掌握每个音

词汇学习建立你的词库

词汇游戏边玩边学

扫码

Download on theApp Store Get it onGoogle Play

✨ 推荐视频

275 句

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

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

跟读练习: Traceroute: You're Probably Reading the Results Wrong - 通过视频学习英语口语

选择练习模式

下载应用

Every Networking Concept Explained In 20 Minutes

Video

The Absurd Engineering Behind the Internet

BGP Overview

Every Hardware Protocol Explained Simply in 10 Minutes!

Free CCNA | VLANs (Part 2) | Day 17 | CCNA 200-301 Complete Course

How Do I Reverse Brain Rot?

Real British English conversation practice , directions to coach (B1–C1)

Why Do You Need BOTH a MAC and IP Address?

Translating Claude’s thoughts into language

How to Become Your Own ISP

Network Ports Explained

本课的词汇与口语要点

视频中的重点词汇

视频中出现的短语动词

需要注意的发音

如何用这段视频练习

什么是跟读法？