쉐도잉 연습: I might have found the BEST budget router... - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

243 문장

문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.

I picked up these two proprietary systems off of eBay for pennies on the dollar, and after just a little bit of tinkering, I was able to convert them into extremely useful and efficient little DIY routers.

At least, that's what I was hoping to say when I first started this project.

Now don't get me wrong, I was able to modify both of these so that they can be repurposed, and in some ways they work really well, especially considering just how much I paid for them.

But it didn't take just a little bit of tinkering, it took so much tinkering that I was about ready to pull an office space on one of these two specifically.

But I didn't do that, and after many hours of reading through forum posts and failing and trying again, I finally managed to mostly get these little guys working.

So let me show you how I did that, and what these interesting little systems might be capable of.

So what are these two systems?

Well, let's start with this one first, which is a Dell EMC Edge 510 LTE.

These devices are used for SD-WAN applications, specifically with VMware's VeloCloud service, and I don't really care all that much about any of that.

Essentially, these boxes would be deployed on the edge of a company's network, places like office branches or retail locations, and rather than being configured locally,

they would all be managed from a central service.

These boxes would then handle routing, firewall policies, VPN tunnels, WAN failover, all that stuff to create a wide area network between all of the different branches.

So a software defined WAN or SD-WAN.

Now I need to give a quick shout out to Micola, hopefully I'm saying that right, for sending me an email about these.

And after looking into it, I was able to very easily buy one of these for just $17 or so on eBay.

And it even came new in the box.

Well, it seems to be new.

There is a dent right here on the back panel, but there's no other scratches.

So I'm assuming this was actually like new old stock.

In that email, he also shared a link to this thread on the serve the home forum, which covers a few other similar devices like this Edge 610.

Unfortunately though, this is not what I meant to buy.

I was really meaning to buy an Edge 620 for some reasons that I'll get to here in a bit.

I did go ahead and purchase a 620 after I noticed my mistake, but that still hasn't shipped and it's been well over a week now so who knows if I'll ever get that.

But today we're going to still at least talk about these two units.

Now obviously both of these devices come with a handful of Ethernet ports.

The 510 has four RJ45 gigabit ports and the 610 has six RJ45 gigabit ports as well as two SFP1 giga ports.

Now the 620

that I was hoping to buy as well as some of

the other higher-end models actually come with 10 gig SFP plus ports.

Now these systems also come with some Intel Atom processors,

which would lead one to believe that these should be able to be repurposed with non-proprietary software like OpenSense or OpenWRT.

And it seems like much smarter people than I have figured out ways of doing just that.

But before trying to hack into these things, let's talk a bit more about the specs.

The Edge 510 obviously features those 4 gigabit NICs on the back, but it also has a barrel jack for power, a reset button, and then under a little cover,

this mini USB port for a serial connection as well as a SIM card slot.

You also get two USB 2 ports, one on either side, and that's really about it for the outside.

If you remove four screws on the bottom, you can easily pop off the lid, and here you don't really find much, just a mini PCIe slot for the Wi-Fi card,

as well as an M.2B key slot for a cell modem.

One of the features of these models, as the LTE in the name might suggest, is that these could be used with a cellular connection, so if your ISP went down for some reason,

it could fail over to a backup cellular connection, which I also forgot to mention that there are these antenna connectors on the back for some cellular antennas.

Back on the inside, hidden away somewhere, there's a 16GB EMMC flash chip for storage,

as well as 4GB of DDR3L memory and the Intel Atom C20358 processor.

This dual core from back in 2013 probably isn't all that much to write home about, But with a TDP of just 7 watts,

it might be pretty efficient while having just enough horsepower to scrape by.

The 610 has a bit more going for it in terms of specs, we already talked about those network ports on the back, and like the 510 it has a barrel jack for power,

a reset button, and another cover that exposes a mini USB port for serial.

Oh, and this also has two USB ports, one on either side, but these are USB 3 ports.

Once again, four screws are all you need to take out to pop open the cover, and here while While there is a bit more going on, it's pretty similar to the 510.

There's a mini PCIe slot for WiFi, an empty B-key slot for a non-existent modem, and that's about it.

Oh, and I should note that on both of these systems, the M.2 B-key slot doesn't support SATA or PCIe,

they only support USB, which seems to be the case for most of these cell modem slots I've come across.

The 610 also includes 16GB of EMMC flash storage and 4GB of RAM, but this uses a newer Intel Atom, the C3308.

This is still a dual core, but it was released in 2017, supports DDR4, and is, uh, well, it's just pretty much all around slightly better and newer.

Now, like I said, I don't have a 620, but the higher-end models of these, like the 620 and 640 and 680, come with dual 10 gig NICs, but they also have better CPUs,

more expansion options, more RAM, so maybe I'll have to do a video diving into those.

For now, though, I just had my two models, which both just had some nonsense VeloCloud stuff installed on them, and I wanted to run something better.

Now theoretically these systems are just simple x86 systems and normally

that would mean you can just install a new operating system on them and boom you're done.

But if you hadn't noticed I mentioned the word Dell which means this is going to be a huge hassle.

Now you know what isn't going to be a huge hassle?

Keeping all of your devices charged thanks to an awesome power bank like this one from today's sponsor Ugreen.

Ugreen makes some of my favorite tech accessories that I quite literally use every day, and somehow they just keep getting better.

Luckily for you, Ugreen's Prime Day Sale is coming up here soon, where you can get up to 40% off some incredible products, like for example this Nexode Pro 200W Powerbank.

This thing includes one of my favorite features of Ugreen's products, which is this 65cm retractable cable.

This makes it so easy to just toss this into my bag

and not even worry about whether or not I packed a USB-C cable.

And with a rating of over 1000 plug and 25,000 retract cycles, this thing will be charging your gear for quite a long time.

And there's actually another built-in cable that's, well, it's sort of hidden because it actually doubles as this little carry handle.

And then see, you can just pop it out and it's another little cable.

How cool.

Along with that, you also get a Type-C and Type-A port.

So in total, you can charge four devices all at once.

As the name suggests, it can support up to 200 watts of total power across all ports, and 100 watts on just a single port,

which is powerful enough to charge a 15-inch M5 MacBook Air to almost 50% in just half an hour.

And with this 25,000 milliamp hour battery, it can charge something like an iPhone 17 Pro Max over three times.

You also get a great looking display that can show metrics like total output power, individual port stats, and more.

There's also other great devices like this Nexo Pro 160-watt charger.

This also comes with a handy display, as well as four USB-C ports and a Type-A port, making it perfect for sort of your main charging station, either at home or at the office or wherever.

With its powerful gallium nitride technology, it can provide up to 140 watts on either of the first two USB-C ports.

And with built-in power management, it also automatically distributes current to help prevent any overheating or overcharging.

If you're interested, you can get up to 40% off of these

or other Ugreen gadgets by checking out their Prime Day deals from June 23rd to the 26th.

Just click my links down in the description.

All right, back to hacking these little guys.

One of the first problems you'll come across is that, well, neither one of these have any sort of video output.

That's not a huge issue normally, I've actually tackled quite a few different headless systems in the past, either by adding on a GPU via some sort of adapter,

or by using a serial connection.

And both of these options are available with these two systems.

While I did get a GPU working via a very sketchy series of adapters, I primarily decided to use the serial port, which just requires a simple mini-USB cable.

I started with the 510 because I felt a little more confident I could get that working, thanks to this incredible guide on GitHub from Jacob Witt.

Here, he consolidated info from a bunch of other awesome people on the NetGate forums and created a guide for installing OpenSense.

I skipped over the GPU bit, just using a serial connection, and then I followed the rest of the instructions.

I signed into the pre-installed VeloCloud OS by using the password Velohello plus the last three digits of the Dell service tag.

From there, you just download a modified firmware image, flash it to the BIOS chip, and then use an I2C command to disable the watchdog timer.

Oh, which I haven't mentioned the watchdog timer yet, but that's one of the biggest issues with these systems.

By default, if the system isn't booted into the correct OS where the watchdog gets disabled, the system will just hard reset after a few minutes.

So if you do manage to get into a different installer or a different OS, the system will work for a bit, but then it will just continue power cycling on you unless you figure out a way to disable it.

But after following these instructions, that problem was solved.

Now with this guide, he installs OpenSense, but I also wanted to try out OpenWrt and also just plain Debian 13 for some testing.

100

But whenever I tried booting into those, I just got a blank console.

101

I'll come back to that later though.

102

The important thing was that this 510 was now cracked and I wanted to move on to the 610.

103

Now this is where things start to get pretty messy.

104

There isn't a clear conclusive guide on this or the other 600 series models.

105

I might be getting some of this stuff wrong because it's pretty messy but just bear with me.

106

Like I mentioned before there's a thread on the serve the

107

home forum where a bunch of incredible people have poured hours into trying to reverse engineer these things

108

and I believe through a combination of different BIOS versions and using I2C commands, people have figured out how to crack the 620

109

and the higher-end models and be able to use them as standard x86 systems pretty well.

110

But once again, I accidentally ordered the 610, which, well, most people just say to absolutely avoid.

111

And that's not just because getting a hold of a BIOS version is pretty much impossible

112

or because it has the 1GB SFP ports instead of 10GB, but it's actually for some even more horrible reasons that we'll get into here very shortly.

113

Now I still wanted to see if I could get this working though so I connected up my serial cable, booted it up, and I was actually able to get into the BIOS menu fairly easily.

114

While looking around though the watchdog timer kicked in and the system rebooted.

115

There's no setting in the BIOS menu to disable this either so I decided to start digging a bit further.

116

The built-in VeloCloud software on this model was pretty much useless

117

and booting into anything else didn't keep the watchdog timer from resetting.

118

but a lot of people mentioned booting into Dell's Diag OS.

119

I think some people had devices that already had this pre-installed on a different partition or something.

120

Mine didn't, and I was eventually able to hunt down a download link for it.

121

So I flashed that to a USB, booted into it, and miraculously, the system didn't reset.

122

Now I'm not sure if I just got lucky

123

and had the right BIOS version or the right version of Diag OS to have this working so easily, but whenever I booted into that Diag OS,

124

It not only kept the watchdog timer from resetting then, but it actually seemed to permanently fix it because after that,

125

I could hang around in the BIOS or boot into a different operating system and not have the system reset.

126

What actually fixed the problem was some initialization that was happening in DiagOS at slash at C slash rc.local, which right off the bat,

127

you can see this run some I2C commands that disable the watchdog timer.

128

This info is really helpful because if for some reason the PIC chip, which is what controls the watchdog timer, If that ever gets reset, you could just save these commands

129

and run them from whichever operating system you're wanting to use to make sure it always stays disabled.

130

So with that solved, it seemed like I pretty much had both the 510

131

and the 610 in a state where I could install whatever operating system I wanted and just hit the ground running.

132

At least that's what I was hoping was the case.

133

We'll come back to this 510 here in a bit.

134

We're going to focus on the 610 for just a second.

135

I did install OpenSense to the internal flash with no issues.

136

but when I went to actually try to configure the interfaces,

137

only four showed up, which obviously doesn't really line up with our six plus two pattern of network ports we have here.

138

To just get into the web UI, I used a USB to Ethernet adapter, and there, in the OpenSense UI, I saw the exact same thing,

139

and I couldn't find a way to get any of these working.

140

So I plugged in a Debian 13 live USB that I modified to work via serial, that way I could just hop in and tinker around a bit.

141

Side note, if having a little Debian live image that works out of the box via serial sounds interesting, I'll have a repo to my configs for how I got that set up,

142

so you can make one for yourself if you're interested.

143

In Debian, I once again saw those four interfaces, and also once again couldn't get any of them working.

144

Now, based on my research into this, I sort of already expected something like this, because, uh, well, those six RJ45 ports aren't typical network interfaces.

145

They're really just ports that are connected to an embedded Marvell switch chip.

146

So essentially, this is just a network switch that's connected to the rest of the system.

147

I actually came across something pretty similar to this when I looked at this Raspberry NVR just a little while back.

148

But here, these ports are supposed to act differently.

149

They're not supposed to act like a simple network switch.

150

I'm not exactly sure why Dell went with this setup.

151

I'm assuming it was cheaper

152

and possibly more efficient to have some of the networking offloaded to a dedicated chip rather than everything going through the CPU, I don't really know.

153

Once again, I'm probably going to get some of this wrong or oversimplify a bit.

154

But essentially how I believe this is all connected is

155

that there are these six ports that are connected to the switch chip, and then there are two internal interfaces between the CPU and that same switch chip,

156

which would be two of the interfaces we saw earlier.

157

To be able to sort of see all of these interfaces independently, the switch configures all six of these ports to be on separate VLANs, and then those get passed to the OS via two trunk ports,

158

which are those two interfaces I just mentioned.

159

Whenever you boot into Diag OS, you can actually see these interfaces labeled as, for example, ETH 0.1 at ETH 0, up through ETH 1.6 at ETH 1.

160

For all of that to work properly, the internal switch needs to set up and configure all of those VLANs,

161

and then the operating system needs to create all of the correct interfaces and link it all up properly.

162

Now, the two SFP ports are a bit simpler.

163

it seems like those were just essentially tied directly to an individual interface.

164

In DiagOS, for example, it was ETH3 and ETH4, but by default, they're actually disabled.

165

Back in that slash at C slash rc.local I mentioned earlier, you can find pretty much all of this.

166

After the watchdog stuff at the top, there's some init commands that go to the Marvell 88E6190 switch chip using this VP1400MDIO tool.

167

And then later on it runs a separate script

168

that configures all of those weird VLANs to make all of the routing work.

169

For the SFP ports, there's just a simple pair of I2C commands that turn off TX disable.

170

I don't know why that needs to be disabled by default, but it is.

171

And fortunately, since that's just a simple I2C command, that's an easy fix that can not only be repeated with other operating systems, but that setting also persists between worm reboots.

172

So if you boot into DiagOS, it'll fix those ports, and then if you boot into something else without doing a hard reset, those ports will still continue to work.

173

Configuring the other ports, though, was obviously not as simple.

174

I'll be honest, most of this stuff is pretty far over my head.

175

I tried to use all of the information that was available on that forum thread, as well as using an LLM for a little bit of help as well.

176

And while I actually managed to at least copy over some of the programs

177

and info from the DiagOS install into a different Debian install, and I even had a script that seemed to get the switch up and running.

178

However, I could just not get any of the actual interfaces linked up in the operating system.

179

I don't think I saw anywhere else where someone got this working in Linux, but I did see this post here where someone was able to get this working in PFSense+.

180

However, that seemed to require modules that only exist in PFSense+, which is the paid version of PFSense, and those weren't included in OpenSense, at least as far as I'm aware.

181

And I wasn't about to start trying to recompile the FreeBSD kernel or anything.

182

I'm sure solving this is possible by someone smarter than me or if I just put in a lot more time, but for now that's where I gave up.

183

I at least had two working interfaces on this, so I was able to boot back into OpenSense and use interfaces 3 and 4.

184

Using a couple of SFP to RJ45 transceivers, I was able to set this up as a basic little firewall

185

and when testing with with an upstream open speed test server, I was getting pretty much full gigabit speeds.

186

All right, now moving back to the 5.10 for a bit.

187

In OpenSense, I didn't have any issues configuring the interfaces, they all just showed up and worked,

188

but it did seem like this older system struggled a little bit to maintain gigabit read speeds.

189

I also wanted to try setting up OpenWrt to see

190

if I could get this set up as not only a firewall slash router, but also as a wireless access point.

191

To do so, I started booting into my Debian Live image, but I remembered that I had ran into that weird quirk earlier where I was just met with a blank screen.

192

On a whim, I decided to try changing the arguments in Grub to use TTYS1 instead of S0, and that actually did the trick.

193

It's a bit annoying because everything up through the bootloader works on TTYS0, but it seems like whenever this actually boots into an operating system,

194

it switches over to TTYS1.

195

Anyway, I had it figured out

196

and was able to use the Debian Live image to then download

197

and flash OpenWrt to the built-in flash storage without any major issues.

198

Well, other than that, once again, I couldn't get OpenWrt booted into a console because the whole TTY is one thing.

199

I was able to solve this by going back into my Debian Live ISO and modifying the grub parameters again,

200

which worked, but then I realized I didn't need to get into a serial console.

201

I could just plug a network cable in and use the web UI.

202

I'm an idiot.

203

At that point, I was able to straighten out which port was assigned to what, and I re-ran my speed tests, and here I found that, well, it managed gigabit just fine.

204

I'm not sure if that's an OpenWRT versus OpenSense thing or Linux versus FreeBSD or what, but I wasn't complaining.

205

Now, OpenWRT is a bit more complicated to get set up.

206

For example, it pretty much doesn't come with any packages pre-included, so I had to find and install the right packages for my WiFi adapter to work.

207

but once I did, I was able to set up an SSID and connect to it with my phone, and the speeds here weren't incredible or anything, but I was testing from all the way across the house,

208

and I'm sure things could improve with a bit of tweaking.

209

Clearly, between these two systems, the 510 is a better value for a repurposed DIY router.

210

It's substantially cheaper.

211

It's good enough for simple gigabit.

212

It has four working ports rather than two, and it doesn't require any extra transceivers or SFP equipment,

213

and it has a built-in cell modem and antennas if that's something you're interested in.

214

But I was still curious about this 610 because it does have that more modern CPU or relatively more modern CPU

215

and so I thought maybe this still could be useful in some non-router use cases.

216

To test that out, I installed Debian, but for realsies this time, onto an actual SSD using the mini PCA slot and some adapters.

217

I also tried installing Debian onto an SSD with the 510 as well, but that system doesn't support booting from NVMe using that mini PCIe slot,

218

so you would either have to configure a separate USB drive to function as a bootloader, or just do what I did and use a USB adapter.

219

Once I had an actual install of Debian, I ran Geekbench 6 to get a rough idea of how these two systems performed in comparison to some others.

220

Starting with the 610, the result was not great.

221

It managed single and multi-core scores of 223 and 411 respectively, which is worse than a Raspberry Pi 4B.

222

Now, PowerDraw here was okay.

223

At idle, it sat right around 10 watts, and it only really jumped up to like 11, almost 12 watts when actually running workloads.

224

I did notice that in the UEFI menu, Turbo was disabled, so I re-ran the test after enabling that.

225

The PowerDraw didn't really look any different, so I wasn't expecting a change, but that change actually gave a 27 to 28% bump in performance,

226

which was still worse than a Pi 4.

227

But hey, it wasn't nearly as bad as the C2358 in the Edge 510.

228

That system only managed scores of 147 and 265.

229

While you could absolutely run some lightweight server workloads like Home Assistant or something on this 610,

230

by the time you bought one of these and then got some SFP transceivers to be able to network it probably, and then did all the hacky stuff to actually get it working,

231

you would already be way better off by just buying an older Raspberry Pi.

232

But for now, I can at least say that this Edge 510, especially for the $17 or $18 I paid for it, is a heck of a value

233

if you're looking for a flexible little gigabit router for a backup

234

or for traveling or for just a simple little router for your home lab.

235

As long as you don't mind putting in a bit of elbow grease to get it working.

236

As much as I wanted to pull what little hair I have out while working on these, I still had a lot of fun just tinkering around and I hope you guys had as much fun watching this video.

237

If so, maybe consider leaving a like or subscribing.

238

That actually goes a long way.

239

Also, you might consider becoming a raid member.

240

For as little as a dollar a month, you can get early access to ad-free versions of all of

241

my videos as well as some other perks depending on the tier.

242

That's about it for this one though.

243

So as always, thank you guys so much for watching, stay curious, and I can't wait to see you in the next one.

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인

IPA 발음 연습모든 소리 마스터

단어 학습나만의 단어장 만들기

단어 게임놀면서 외우기

QR 스캔

Download on theApp Store Get it onGoogle Play

같은 채널

Is The Framework Laptop ACTUALLY Worth It?

Business EnglishUniversity StudentsWorking Adults

FOR YOU

이 레슨의 어휘와 말하기 포인트

이 B2 수준 말하기 레슨은 영상 “I might have found the BEST budget router..”을(를) 바탕으로 합니다. 이 영상에는 섀도잉할 문장 243개와 단어 4416개가 있습니다. 말하는 구간의 길이는 22:17입니다. 화자는 분당 약 198단어로 빠르게 말하므로 연음과 약하게 발음되는 소리가 많습니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 77%뿐이라 어휘가 어려운 편입니다.

이 영상의 핵심 어휘

영상에서 가장 어려운 단어 15개를 발음, 뜻과 함께 정리했습니다.

단어	발음	뜻
boot 명사	/but/	장화, 목화
interface 명사	/ˈɪn(t)ɚˌfeɪs/	인터페이스
install 동사	/ɪnˈstɔl/	설치하다, 깔다
configure 동사	/kənˈfɪɡə(ɹ)/	설정하다
gigabit 명사	/ˈɡɪɡəbɪt/	기가비트
timer 명사	/ˈtaɪmɚ/	타이머
watt 명사	/wɑt/	와트
router 명사	/ˈɹaʊ.tɚ/	라우터
modem 명사	/ˈmoʊdəm/	모뎀
firewall 명사	/ˈfaɪ(ə)ɹˌwɔl/	방화벽
antenna 명사	/ænˈtɛn.ə/	촉각, 더듬이
modify 동사	/ˈmɑ.dɪˌfaɪ/	수정하다
cellular 형용사	/ˈsɛl.ju.lə/	세포의
grub 명사	/ɡɹʌb/	유충
spectacles 명사	/ˈspɛktəkl̩z/	안경

영상에 나오는 구동사

단어	뜻
come up 동사	올라오다
give up 동사	항복하다
look around 동사	둘러보다
pick up 동사	줍다
turn off 동사	끄다, 턴오프하다

이 영상의 문법

화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.

문형	영상 속 표현
수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점	can be repurposed · would be deployed · be managed
현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때	hasn't shipped · have figured · I've come
관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보	first, which is · Dell which means · products, which is

주의할 발음

화자는 I'm, didn't, don't 같은 축약형과 약화된 형태를 73번 사용합니다. 들리는 대로 짧게 발음하세요.

“sh”와 “zh” 소리: instruction /ɪnˈstɹʌkʃən/, partition /pɑɹˈtɪ.ʃən/, shout /ʃaʊt/
긴 단어 — 강세 위치에 주의: proprietary /pɹəˈpɹaɪ.ə.tə.ɹi/, consolidate /kənˈsɒl.ɪ.deɪt/, parameter /pəˈɹæm.ə.tɚ/, accessory /əkˈsɛs.(ə.)ɹi/, fortunately /ˈfɔɹ.t͡ʃə.nɪt.li/

한국어 화자가 어려워하는 소리:

/f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: interface /ˈɪn(t)ɚˌfeɪs/, configure /kənˈfɪɡə(ɹ)/, firewall /ˈfaɪ(ə)ɹˌwɔl/, modify /ˈmɑ.dɪˌfaɪ/, config /ˌkənˈfɪɡ/
/v/ — ㅂ(/b/)과 구별하기: transceiver /tɹænˈsi.vɚ/, conclusive /kənˈkluːsɪv/, whichever /wɪt͡ʃˈɛvɚ/, convert /kənˈvɝt/, dive /daɪv/
/z/ — ㅈ이 아니라 성대를 울리는 /s/: spectacles /ˈspɛktəkl̩z/, existent /ɪɡˈzɪst(ə)nt/, expose /ɪkˈspoʊz/

이 영상으로 연습하는 방법

먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
자신의 목소리를 녹음해 원본과 비교하고, boot, interface, install 같은 단어에 특히 주의합니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: I might have found the BEST budget router... - 영상으로 영어 말하기 배우기

연습 모드 선택

앱 다운로드

같은 채널

Is The Framework Laptop ACTUALLY Worth It?

추천 영상

your home router STILL SUCKS!! (use OPNsense instead)

Color Palettes Worth Another Look

BEST Budget Mouse of 2026? ATK A9 Mini+ Review (shocking)

This 25-Year-Old Built a 2-Year Moat Nobody Can Bet Against | Corgi, Nico Laqua & Emily Yuan

I bought the most SATISFYING TECH on the internet.

Embedded Insiders: Qualcomm's Acquisition of Arduino

Mac vs Windows - It's not close in 2026!

Phát âm chuẩn cùng VOA - Anh ngữ đặc biệt: Computers Could Be Used to Heat Homes (VOA)

Provision LEMP with Ansible on a Raspberry Pi Cluster (Pi Dramble #4)

I Go To The Cloud.

I Built a Fully Autonomous Flying Umbrella

FREE CCNA 200-301 course // Complete Practical CCNA (v1.1 2025 Course) with real equipment