WEBVTT

1
00:00:00.080 --> 00:00:01.960
<v Speaker 1>Welcome to the deep dive. We're here to cut through

2
00:00:01.960 --> 00:00:05.599
<v Speaker 1>the noise on complex topics and give you the real insights. Today,

3
00:00:05.960 --> 00:00:09.560
<v Speaker 1>we're really diving deep into computer networking, peeling back the layers,

4
00:00:09.560 --> 00:00:12.400
<v Speaker 1>you know, yeah, understanding what actually makes your digital world tick.

5
00:00:12.839 --> 00:00:15.919
<v Speaker 1>We're using hazene gabers past the COMPTI in Network Plus

6
00:00:15.919 --> 00:00:18.440
<v Speaker 1>Exam guide as our map. But don't worry, this is

7
00:00:18.440 --> 00:00:20.879
<v Speaker 1>an exam prep No. Our mission is to pull out

8
00:00:20.879 --> 00:00:23.920
<v Speaker 1>the core ideas, the stuff that helps you really get

9
00:00:23.960 --> 00:00:26.280
<v Speaker 1>what's happening with all the tech you use every day,

10
00:00:26.640 --> 00:00:29.280
<v Speaker 1>turning the magic into something well understandable.

11
00:00:29.399 --> 00:00:31.920
<v Speaker 2>Absolutely, and it's really important to stress the stuff we're

12
00:00:31.920 --> 00:00:35.359
<v Speaker 2>talking about based on Network Plus EID, it's all vendor neutral. Yeah,

13
00:00:35.399 --> 00:00:38.320
<v Speaker 2>so these ideas they apply it everywhere, Cisco, Juniper, your

14
00:00:38.320 --> 00:00:42.280
<v Speaker 2>little home router, doesn't matter. It's the fundamental logic and

15
00:00:42.320 --> 00:00:46.119
<v Speaker 2>that's essential knowledge, whether you're just curious or maybe thinking

16
00:00:46.159 --> 00:00:49.880
<v Speaker 2>about it. Rolls like a network admin or system engineer exactly.

17
00:00:50.240 --> 00:00:52.439
<v Speaker 1>Okay, so let's get into it. We'll start with the basics,

18
00:00:52.719 --> 00:00:55.520
<v Speaker 1>like how do all these different gadgets even start talking

19
00:00:55.520 --> 00:00:57.320
<v Speaker 1>to each other? Then we'll look at the gear that

20
00:00:57.320 --> 00:00:59.840
<v Speaker 1>makes it happen. And finally, how we keep it all

21
00:01:00.159 --> 00:01:04.319
<v Speaker 1>secure and you know working? Right? So first question, You've

22
00:01:04.359 --> 00:01:07.560
<v Speaker 1>got your phone, your laptop, maybe a smart TV, all

23
00:01:07.599 --> 00:01:11.239
<v Speaker 1>on the same Wi Fi. How how do they communicate?

24
00:01:11.319 --> 00:01:12.159
<v Speaker 1>They're so different?

25
00:01:12.359 --> 00:01:15.680
<v Speaker 2>Yeah, it seems complex, but it boils down to protocols.

26
00:01:16.040 --> 00:01:21.000
<v Speaker 2>Think of protocols as the agreed upon languages for networks,

27
00:01:21.079 --> 00:01:24.799
<v Speaker 2>just like you'd use different tones or words for different situations. Devices,

28
00:01:24.840 --> 00:01:28.359
<v Speaker 2>you specific protocols for specific jobs. You know, web browsing

29
00:01:28.439 --> 00:01:31.519
<v Speaker 2>uses one set of rules, sending email uses another. It's

30
00:01:31.519 --> 00:01:33.120
<v Speaker 2>all about having that common ground.

31
00:01:33.200 --> 00:01:35.519
<v Speaker 1>Okay, so they need a shared language. Yeah, that makes sense.

32
00:01:35.560 --> 00:01:37.959
<v Speaker 1>And the guide talks about ports. Now you don't mean

33
00:01:37.959 --> 00:01:39.920
<v Speaker 1>the physical holes like the ethernet jack.

34
00:01:39.799 --> 00:01:42.599
<v Speaker 2>Right question, No, not the physical ports. We're talking about

35
00:01:42.680 --> 00:01:47.920
<v Speaker 2>virtual ports. Here. Imagine your computer has one main Internet connection, right,

36
00:01:48.079 --> 00:01:51.000
<v Speaker 2>like one big front door to a building. But inside

37
00:01:51.000 --> 00:01:53.879
<v Speaker 2>that building there are thousands of numbered offices. Those are

38
00:01:53.879 --> 00:01:56.480
<v Speaker 2>the virtual ports. All the data comes through the one

39
00:01:56.519 --> 00:02:00.000
<v Speaker 2>main door, the physical connection, but these virtual ports sorted out.

40
00:02:00.159 --> 00:02:02.959
<v Speaker 2>So web traffic goes to say office four four three,

41
00:02:03.560 --> 00:02:05.799
<v Speaker 2>email goes somewhere else. It keeps everything organized.

42
00:02:06.040 --> 00:02:08.879
<v Speaker 1>I see, So one physical pipe but lots of virtual

43
00:02:08.960 --> 00:02:13.479
<v Speaker 1>channels inside it clever, and the guide mentions some are

44
00:02:14.000 --> 00:02:16.919
<v Speaker 1>well known. Why is that significant? Which one should we

45
00:02:17.199 --> 00:02:18.159
<v Speaker 1>you know, maybe know about?

46
00:02:18.199 --> 00:02:20.520
<v Speaker 2>All right, the well known ports zero to en twenty three,

47
00:02:20.560 --> 00:02:23.599
<v Speaker 2>they're like universal standard, super important. Think about it. If

48
00:02:23.639 --> 00:02:27.199
<v Speaker 2>every website used a different port for basic browsing, nothing

49
00:02:27.199 --> 00:02:29.919
<v Speaker 2>would work. So for secure websites, look for the little

50
00:02:29.919 --> 00:02:33.439
<v Speaker 2>padlock that's HTTPS using port four to forty three really

51
00:02:33.479 --> 00:02:35.360
<v Speaker 2>crucial for privacy like online banking.

52
00:02:35.439 --> 00:02:37.360
<v Speaker 1>Okay, four forty three for secure stuff.

53
00:02:37.439 --> 00:02:40.919
<v Speaker 2>Yeah, and older unencrypted sites use HTTP on port eighty.

54
00:02:41.120 --> 00:02:44.319
<v Speaker 2>When you type a website name like the dive Dot show,

55
00:02:44.439 --> 00:02:47.120
<v Speaker 2>that's DNS working behind the scenes on port fifty three,

56
00:02:47.439 --> 00:02:49.639
<v Speaker 2>it translates the name into the number.

57
00:02:49.360 --> 00:02:51.039
<v Speaker 1>Of the IP address the phone book thing.

58
00:02:51.240 --> 00:02:53.719
<v Speaker 2>Exactly the Internet's phone book. And if you're managing a

59
00:02:53.759 --> 00:02:57.520
<v Speaker 2>server remotely, you'll often use SSH on port twenty two

60
00:02:57.759 --> 00:03:02.000
<v Speaker 2>for a secure connection. It's this simple agreement on numbers

61
00:03:02.039 --> 00:03:06.120
<v Speaker 2>that well, that's the whole Internet function smoothly. It's foundational stuff.

62
00:03:05.879 --> 00:03:08.960
<v Speaker 1>That really clarifies it. Yeah, okay, so devices have a language,

63
00:03:09.159 --> 00:03:12.840
<v Speaker 1>protocols and these virtual doors the ports, but how do

64
00:03:12.879 --> 00:03:16.120
<v Speaker 1>they actually handle the information. How's it packaged? Incent That's

65
00:03:16.120 --> 00:03:18.000
<v Speaker 1>where this OSI model.

66
00:03:17.680 --> 00:03:21.080
<v Speaker 2>Comes in, right, Right, the OSI model Open Systems interconnect.

67
00:03:21.080 --> 00:03:24.719
<v Speaker 2>It sounds technical, but it's really a conceptual map. It's

68
00:03:24.719 --> 00:03:28.120
<v Speaker 2>not physical layers you can touch, but seven logical layers

69
00:03:28.120 --> 00:03:31.319
<v Speaker 2>that describe how communication should happen. And it's real value

70
00:03:31.360 --> 00:03:34.919
<v Speaker 2>for you troubleshooting when things go wrong. This model helps

71
00:03:34.919 --> 00:03:36.840
<v Speaker 2>you think logically about where the problem might be.

72
00:03:37.159 --> 00:03:39.400
<v Speaker 1>I like the analogy in the source sending a letter

73
00:03:39.400 --> 00:03:42.719
<v Speaker 1>from the US to Spain. It helps visualize packaging sending

74
00:03:42.879 --> 00:03:44.319
<v Speaker 1>unpacking exactly.

75
00:03:44.319 --> 00:03:45.960
<v Speaker 2>That's a great way to think about it. Let's map

76
00:03:46.000 --> 00:03:49.159
<v Speaker 2>a few layers to that idea. Layer one the physical layer,

77
00:03:49.240 --> 00:03:51.599
<v Speaker 2>that's the actual cables, the Wi Fi signals, the physical

78
00:03:51.639 --> 00:03:54.360
<v Speaker 2>connection in the letter analogy, did you even put the

79
00:03:54.439 --> 00:03:56.000
<v Speaker 2>letter in the mailbox? If you just toss it out

80
00:03:56.000 --> 00:03:57.319
<v Speaker 2>the window, it's not going anywhere.

81
00:03:57.400 --> 00:03:57.560
<v Speaker 1>Right.

82
00:03:58.199 --> 00:04:01.199
<v Speaker 2>Layer one asks is it physically connected?

83
00:04:01.479 --> 00:04:03.719
<v Speaker 1>Makes sense? Can't send data without a connection.

84
00:04:03.919 --> 00:04:06.599
<v Speaker 2>Then jump up to layer three, the network layer. This

85
00:04:06.639 --> 00:04:09.879
<v Speaker 2>is where I addresses live. This layer figures out the

86
00:04:09.919 --> 00:04:13.039
<v Speaker 2>best path across different networks, like the main post office

87
00:04:13.120 --> 00:04:16.439
<v Speaker 2>routing your letter across countries using the address. It asks

88
00:04:16.600 --> 00:04:18.079
<v Speaker 2>where's this going? What's the route?

89
00:04:18.199 --> 00:04:21.240
<v Speaker 1>Okay? IP addresses for routing and way up at the top.

90
00:04:21.319 --> 00:04:24.360
<v Speaker 2>Layer seven the application layer. This is what you actually

91
00:04:24.399 --> 00:04:27.399
<v Speaker 2>see and interact with your browser or your email app.

92
00:04:27.680 --> 00:04:29.839
<v Speaker 2>This is the recipient opening and reading your letter. It

93
00:04:29.879 --> 00:04:31.879
<v Speaker 2>asks what does the user want to do? Can I

94
00:04:31.920 --> 00:04:35.240
<v Speaker 2>display this web page or send this email? So connecting

95
00:04:35.279 --> 00:04:38.040
<v Speaker 2>it all if your internet's out, The OSI model gives

96
00:04:38.040 --> 00:04:41.600
<v Speaker 2>you steps. Is it layer one, check the cables? Is

97
00:04:41.639 --> 00:04:44.160
<v Speaker 2>it Layer three? Am I getting an IP address? Or

98
00:04:44.240 --> 00:04:46.319
<v Speaker 2>layer seven is my browser just frozen?

99
00:04:46.560 --> 00:04:48.439
<v Speaker 1>I see. It helps narrow it down instead of just

100
00:04:48.480 --> 00:04:50.920
<v Speaker 1>you know, rebooting everything blindly precisely.

101
00:04:51.160 --> 00:04:52.800
<v Speaker 2>It's about structure diagnosis.

102
00:04:53.079 --> 00:04:57.319
<v Speaker 1>Okay, so we have the languages, protocols, and the blueprint

103
00:04:57.600 --> 00:05:01.399
<v Speaker 1>OSI model, but what about the actual hardware, the physical

104
00:05:01.439 --> 00:05:03.519
<v Speaker 1>stuff that makes the network go right.

105
00:05:03.480 --> 00:05:07.800
<v Speaker 2>The devices. Let's start local on your home or office network,

106
00:05:07.839 --> 00:05:11.079
<v Speaker 2>your local area network or land. The key player is

107
00:05:11.160 --> 00:05:13.680
<v Speaker 2>usually a switch. Think of a switch as a really

108
00:05:13.720 --> 00:05:17.839
<v Speaker 2>efficient local traffic director. Unlike old hubs that just yelled data.

109
00:05:17.680 --> 00:05:19.759
<v Speaker 1>Everywhere, ah the dumb cousin right.

110
00:05:19.639 --> 00:05:22.879
<v Speaker 2>Oh yeah, exactly. A switch is smart. It learns the

111
00:05:23.000 --> 00:05:26.120
<v Speaker 2>unique MSc address of each device. Plugged into it. It

112
00:05:26.160 --> 00:05:28.639
<v Speaker 2>builds a little table so it knows exactly which port

113
00:05:28.680 --> 00:05:31.319
<v Speaker 2>leads to your laptop, which to your printer. It sends

114
00:05:31.399 --> 00:05:33.519
<v Speaker 2>data only where it needs to go, very efficient.

115
00:05:33.600 --> 00:05:36.879
<v Speaker 1>Okay, so the switch handles traffic within my local network,

116
00:05:37.240 --> 00:05:39.600
<v Speaker 1>But what gets the data out to the wider Internet.

117
00:05:39.839 --> 00:05:43.040
<v Speaker 2>That's the router's job. If a switch connects devices on

118
00:05:43.079 --> 00:05:46.439
<v Speaker 2>the same network, a router connects different networks together, it's

119
00:05:46.439 --> 00:05:49.800
<v Speaker 2>your gateway. Routers mainly look at IP addresses and use

120
00:05:49.839 --> 00:05:52.519
<v Speaker 2>their routing table like a map of known networks, to

121
00:05:52.560 --> 00:05:55.560
<v Speaker 2>decide the best path to send data packets towards their

122
00:05:55.600 --> 00:05:56.480
<v Speaker 2>final destination.

123
00:05:56.920 --> 00:06:00.000
<v Speaker 1>So switch is local, router is the connector between networks

124
00:06:00.560 --> 00:06:02.000
<v Speaker 1>like my home in the Internet.

125
00:06:02.079 --> 00:06:04.920
<v Speaker 2>You got it, and standing guard often near the router

126
00:06:05.000 --> 00:06:08.600
<v Speaker 2>is the firewall. A firewall is your network security guard.

127
00:06:08.920 --> 00:06:11.879
<v Speaker 2>It inspects incoming and outgoing traffic and decides what to

128
00:06:11.920 --> 00:06:14.959
<v Speaker 2>allow or block based on rules. These rules are called

129
00:06:15.040 --> 00:06:18.319
<v Speaker 2>access control lists or acls. They can be based on

130
00:06:18.399 --> 00:06:20.959
<v Speaker 2>IP addresses, port numbers, all sorts.

131
00:06:20.759 --> 00:06:22.800
<v Speaker 1>Of criteria, Like a bouncer with a strict list.

132
00:06:22.959 --> 00:06:26.240
<v Speaker 2>Pretty much standard rules are often let internal traffic out,

133
00:06:26.279 --> 00:06:29.839
<v Speaker 2>but be very suspicious of incoming traffic. It's about controlling access.

134
00:06:30.000 --> 00:06:35.199
<v Speaker 1>Okay, switch, router, firewall. They work together. But how do

135
00:06:35.279 --> 00:06:38.160
<v Speaker 1>all my devices get those IP addresses and MT dresses

136
00:06:38.160 --> 00:06:38.800
<v Speaker 1>in the first place.

137
00:06:38.879 --> 00:06:41.639
<v Speaker 2>Well, MS addresses are burned in by the manufacturer their

138
00:06:41.680 --> 00:06:45.399
<v Speaker 2>unique hardware IDs, but IP addresses are usually assigned. We've

139
00:06:45.519 --> 00:06:48.519
<v Speaker 2>mostly used IPv four, those thirty two bit addresses like

140
00:06:48.720 --> 00:06:50.639
<v Speaker 2>one on E two point one sixty eight point one

141
00:06:50.759 --> 00:06:54.480
<v Speaker 2>point one, one hundred zero, but we've basically run out.

142
00:06:54.480 --> 00:06:56.639
<v Speaker 2>There are just too many devices now I've heard about that,

143
00:06:56.680 --> 00:06:58.879
<v Speaker 2>which is why IPv six is rolling out. It uses

144
00:06:58.879 --> 00:07:02.240
<v Speaker 2>one hundred and twenty eight addresses. The number is astronomical,

145
00:07:02.560 --> 00:07:04.879
<v Speaker 2>like trillions of addresses for every person on Earth. We

146
00:07:04.920 --> 00:07:07.639
<v Speaker 2>won't run out of those anytime soon. And internally, on

147
00:07:07.680 --> 00:07:10.480
<v Speaker 2>your own network, you typically use private IP addresses from

148
00:07:10.519 --> 00:07:13.920
<v Speaker 2>specific ranges like one ninety two point one sixty eight

149
00:07:14.000 --> 00:07:17.199
<v Speaker 2>dot something dot something. These aren't routable on the public Internet.

150
00:07:17.279 --> 00:07:19.600
<v Speaker 1>So how does my new phone get one of those

151
00:07:19.639 --> 00:07:22.720
<v Speaker 1>private ips automatically? When I connect to Wi Fi, I

152
00:07:22.759 --> 00:07:23.959
<v Speaker 1>don't type anything in AH.

153
00:07:24.040 --> 00:07:27.399
<v Speaker 2>That's the magic of DHCP, the Dynamic Host Configuration protocol.

154
00:07:27.399 --> 00:07:30.160
<v Speaker 2>When your phone joins the network, it basically broadcasts, Hey,

155
00:07:30.560 --> 00:07:33.959
<v Speaker 2>anyone got an IP address for me? That's the discover step.

156
00:07:34.120 --> 00:07:37.240
<v Speaker 2>A DHCP server on your network, often built into your router,

157
00:07:37.439 --> 00:07:39.680
<v Speaker 2>here's this and says sure, how about this one? That's

158
00:07:39.680 --> 00:07:42.079
<v Speaker 2>the offer. Your phone says okay, I'll take it. That's

159
00:07:42.120 --> 00:07:45.680
<v Speaker 2>the request, and the server confirms it's yours for a while.

160
00:07:46.040 --> 00:07:53.040
<v Speaker 2>The ACK or acknowledgment discover offer request ack DRA happens

161
00:07:53.040 --> 00:07:56.959
<v Speaker 2>in seconds, totally automatic, like getting a hotel room key dera.

162
00:07:57.360 --> 00:08:01.160
<v Speaker 1>Got it, simple but effective. But I still use names

163
00:08:01.360 --> 00:08:04.720
<v Speaker 1>like Google dot Com not numbers. How does that translation happen?

164
00:08:05.079 --> 00:08:08.040
<v Speaker 2>That's DNS again, the Domain Name system. It's the Internet's

165
00:08:08.079 --> 00:08:11.399
<v Speaker 2>phone book. Remember your computer asks a DNS server, Hey,

166
00:08:11.480 --> 00:08:14.240
<v Speaker 2>what's the IP address for Google dot Com? The DNS

167
00:08:14.279 --> 00:08:16.639
<v Speaker 2>server looks it up and sends back the correct numerical

168
00:08:16.639 --> 00:08:17.360
<v Speaker 2>IP address.

169
00:08:17.519 --> 00:08:20.000
<v Speaker 1>So DNS finds the number for the name exactly.

170
00:08:20.040 --> 00:08:22.800
<v Speaker 2>Without DNS, we'd all have from memorized IP addresses, which

171
00:08:22.839 --> 00:08:24.519
<v Speaker 2>would be well impossible.

172
00:08:24.600 --> 00:08:26.839
<v Speaker 1>Yeah, no kidding, Yes, Okay, one more piece of magic.

173
00:08:27.199 --> 00:08:30.160
<v Speaker 1>How can my whole office, dozens of computers, phones, everything,

174
00:08:30.199 --> 00:08:33.120
<v Speaker 1>all share just one public IP address to get online?

175
00:08:33.240 --> 00:08:36.600
<v Speaker 2>Ah, that's NAT network address translation, and it's buddy pat

176
00:08:36.759 --> 00:08:41.240
<v Speaker 2>port address translation. When your computer with its private IP

177
00:08:41.720 --> 00:08:45.320
<v Speaker 2>sends data out, your router performed a little switcheroo. It

178
00:08:45.360 --> 00:08:48.559
<v Speaker 2>replaces your private source IP with its own public IP

179
00:08:48.639 --> 00:08:50.360
<v Speaker 2>address that's NAT.

180
00:08:50.080 --> 00:08:53.279
<v Speaker 1>Okay, so it disguises the internal address, right.

181
00:08:53.039 --> 00:08:55.240
<v Speaker 2>But how does it know where to send the replies

182
00:08:55.320 --> 00:08:59.480
<v Speaker 2>back to? That's paaa T. The router also assigns a

183
00:08:59.559 --> 00:09:02.919
<v Speaker 2>unique out going port number to your computer's connection. When

184
00:09:02.919 --> 00:09:05.440
<v Speaker 2>the reply comes back to that specific port number on

185
00:09:05.480 --> 00:09:08.279
<v Speaker 2>the router's public IP, the writer knows, ah, this goes

186
00:09:08.320 --> 00:09:10.559
<v Speaker 2>back to laptop or this one goes to the phone.

187
00:09:10.679 --> 00:09:12.559
<v Speaker 1>So it uses port numbers to keep track of all

188
00:09:12.600 --> 00:09:14.799
<v Speaker 1>the internal devices sharing the one public IP.

189
00:09:15.039 --> 00:09:18.519
<v Speaker 2>Precisely, it allows many devices to share one address. It

190
00:09:18.559 --> 00:09:21.000
<v Speaker 2>was a brilliant fix for the IPv four shortage. Really,

191
00:09:21.360 --> 00:09:25.919
<v Speaker 2>it's this amazing coordinated dance of DHCP, DNS, NAT PAT

192
00:09:26.759 --> 00:09:28.320
<v Speaker 2>all working together seamlessly.

193
00:09:28.639 --> 00:09:31.399
<v Speaker 1>We understand the structure, the addressing of the really critical part.

194
00:09:31.639 --> 00:09:33.440
<v Speaker 1>How do we protect all this? How do we keep

195
00:09:33.480 --> 00:09:34.600
<v Speaker 1>networks safe and running?

196
00:09:34.840 --> 00:09:38.720
<v Speaker 2>Security is huge, absolutely non negotiable. Let's start with something

197
00:09:38.720 --> 00:09:43.320
<v Speaker 2>we mentioned ACLS, access control lists on firewalls and routers.

198
00:09:43.799 --> 00:09:46.639
<v Speaker 2>These rules are your first line of defense. You define

199
00:09:46.679 --> 00:09:49.759
<v Speaker 2>exactly what's allowed in and out, maybe block traffic from

200
00:09:49.840 --> 00:09:52.879
<v Speaker 2>known bad IP addresses or only allow access to your

201
00:09:52.919 --> 00:09:55.720
<v Speaker 2>web server on port four four three and the order

202
00:09:55.799 --> 00:09:59.080
<v Speaker 2>matters rules are checked top down, and usually there's an

203
00:09:59.120 --> 00:10:02.480
<v Speaker 2>invisible deny everything else rule at the very bottom. If

204
00:10:02.519 --> 00:10:04.440
<v Speaker 2>it's not explicitly allowed, it's blocked.

205
00:10:04.840 --> 00:10:08.399
<v Speaker 1>Makes sense be specific about what's okay. What about remote access?

206
00:10:08.440 --> 00:10:10.840
<v Speaker 1>Lots of us work from home now VPNs Yes.

207
00:10:11.039 --> 00:10:14.840
<v Speaker 2>VPNs virtual private networks are essential for that. They create

208
00:10:14.879 --> 00:10:18.279
<v Speaker 2>a secure, encrypted tunnel across the public Internet. It's like

209
00:10:18.360 --> 00:10:20.799
<v Speaker 2>sending your data inside a locked po box instead of

210
00:10:20.799 --> 00:10:23.360
<v Speaker 2>just on a postcard. You have client to site VPNs,

211
00:10:23.360 --> 00:10:25.399
<v Speaker 2>where you the remote worker connects securely back to the

212
00:10:25.440 --> 00:10:28.799
<v Speaker 2>office network, and site to site VPNs, which securely link

213
00:10:28.879 --> 00:10:32.039
<v Speaker 2>two entire office networks together over the Internet, making them

214
00:10:32.039 --> 00:10:33.639
<v Speaker 2>act like one private network.

215
00:10:33.759 --> 00:10:35.240
<v Speaker 1>So it encrypts the traffic between the.

216
00:10:35.159 --> 00:10:40.240
<v Speaker 2>Points exactly, using strong protocols like IPsec or ssltls to

217
00:10:40.320 --> 00:10:42.639
<v Speaker 2>keep it confidential and ensure it hasn't been tampered with.

218
00:10:43.159 --> 00:10:45.919
<v Speaker 2>But security isn't just the network, it's the devices to

219
00:10:46.440 --> 00:10:51.519
<v Speaker 2>device hardening. This means reducing the attack surface of your routers, switches, servers,

220
00:10:51.559 --> 00:10:55.320
<v Speaker 2>even your laptop. Simple things really change default passwords, use

221
00:10:55.360 --> 00:10:58.200
<v Speaker 2>strong ones, keep from more updated, turn off services you

222
00:10:58.279 --> 00:11:00.679
<v Speaker 2>don't need, disable unused to port.

223
00:11:00.559 --> 00:11:01.879
<v Speaker 1>Basic digital hygiene.

224
00:11:01.960 --> 00:11:04.080
<v Speaker 2>Essentially, that's a great way to put it. Every little

225
00:11:04.080 --> 00:11:05.480
<v Speaker 2>bit helps lock things down.

226
00:11:05.840 --> 00:11:08.159
<v Speaker 1>And when it comes to who can access things? I

227
00:11:08.240 --> 00:11:11.159
<v Speaker 1>hear triple A and MFA thrown around. What's the quick version?

228
00:11:11.200 --> 00:11:15.360
<v Speaker 2>Okay? Triple A is a framework authentication, authorization, and accounting.

229
00:11:15.679 --> 00:11:19.759
<v Speaker 2>Authentication is who are you? Prove it? Usually use your name, password,

230
00:11:19.759 --> 00:11:22.279
<v Speaker 2>maybe a certificate. Authorization is okay, now that I know

231
00:11:22.279 --> 00:11:24.159
<v Speaker 2>who you are, what are you allowed to do? Can

232
00:11:24.200 --> 00:11:26.559
<v Speaker 2>you access this file? Share? Can you change this setting?

233
00:11:26.639 --> 00:11:29.840
<v Speaker 2>Accounting is what did you do? Logging, access, changes, etc.

234
00:11:30.200 --> 00:11:33.480
<v Speaker 1>For security, audit, authenticate, authorize account got.

235
00:11:33.320 --> 00:11:38.240
<v Speaker 2>It an MFA Multi factor authentication? This is huge for security.

236
00:11:38.320 --> 00:11:40.639
<v Speaker 2>It means proving who you are with more than one thing,

237
00:11:41.200 --> 00:11:43.960
<v Speaker 2>not just something you know like a password, but also

238
00:11:44.279 --> 00:11:47.240
<v Speaker 2>maybe something you have like a code generated on your

239
00:11:47.279 --> 00:11:50.720
<v Speaker 2>phone app or a physical token, or something you are

240
00:11:51.279 --> 00:11:54.440
<v Speaker 2>like a fingerprint or face scan, or even somewhere you

241
00:11:54.480 --> 00:11:58.759
<v Speaker 2>are like geofencing or something you do like your typing pattern.

242
00:11:59.039 --> 00:12:02.080
<v Speaker 1>So password plus phone code is MFA. Yep.

243
00:12:02.360 --> 00:12:04.919
<v Speaker 2>Even if someone steals your password, they still need your phone.

244
00:12:05.120 --> 00:12:08.720
<v Speaker 2>It makes unauthorized access much much harder. Taking all this

245
00:12:08.799 --> 00:12:13.240
<v Speaker 2>together ACLS, VPNs hardening triple A MFA. It's about layers.

246
00:12:13.840 --> 00:12:16.679
<v Speaker 2>No single thing is perfect, but multiple layers build strong

247
00:12:16.720 --> 00:12:18.279
<v Speaker 2>defense protecting your data.

248
00:12:18.360 --> 00:12:21.240
<v Speaker 1>That's a great overview of defense. But things still break

249
00:12:21.320 --> 00:12:23.159
<v Speaker 1>right networks go down? What happens?

250
00:12:23.159 --> 00:12:26.360
<v Speaker 2>Then? How do you fix ith troubleshooting? Yes, it's inevitable,

251
00:12:26.399 --> 00:12:28.840
<v Speaker 2>but having a method is key and knowing some basic

252
00:12:28.879 --> 00:12:31.720
<v Speaker 2>tools like the command ping super simple, super useful.

253
00:12:31.840 --> 00:12:34.399
<v Speaker 1>You mentioned that it checks if something's reachable.

254
00:12:34.320 --> 00:12:37.679
<v Speaker 2>Exactly you type ping followed by an IP address or

255
00:12:37.759 --> 00:12:40.679
<v Speaker 2>host name like ping Google dot com. It sends a

256
00:12:40.679 --> 00:12:42.559
<v Speaker 2>little test packet and sees if it gets a reply.

257
00:12:43.039 --> 00:12:45.559
<v Speaker 2>Tells you if the target is online and responding, and

258
00:12:45.639 --> 00:12:48.840
<v Speaker 2>how fast the connection is. First step in diagnosing is

259
00:12:48.879 --> 00:12:49.279
<v Speaker 2>it down?

260
00:12:49.679 --> 00:12:51.360
<v Speaker 1>Okay? Ping is step one? What else?

261
00:12:51.639 --> 00:12:55.360
<v Speaker 2>Tracer on Windows or trace route on the clinics. This

262
00:12:55.440 --> 00:12:57.919
<v Speaker 2>shows you the path the hops your data takes to

263
00:12:57.919 --> 00:13:00.639
<v Speaker 2>get somewhere. If your connection to a website, a slow

264
00:13:01.039 --> 00:13:03.360
<v Speaker 2>tracer can show you where the delay is happening, Is

265
00:13:03.399 --> 00:13:05.679
<v Speaker 2>it close to you, near the destination or somewhere in

266
00:13:05.720 --> 00:13:08.159
<v Speaker 2>the middle. Helps pinpoint bottlenecks.

267
00:13:07.679 --> 00:13:09.399
<v Speaker 1>Like following the mail route to see where the truck

268
00:13:09.399 --> 00:13:09.919
<v Speaker 1>got's stuck.

269
00:13:09.960 --> 00:13:13.519
<v Speaker 2>Good analogy. You also have ipcon fig Windows or if

270
00:13:13.519 --> 00:13:16.399
<v Speaker 2>config m clinics to see your own computer's network settings,

271
00:13:16.440 --> 00:13:22.240
<v Speaker 2>your IP address, subnet mask, gateway, DNS, servers, essential info.

272
00:13:22.200 --> 00:13:23.600
<v Speaker 1>Right check your own setup first.

273
00:13:23.799 --> 00:13:27.519
<v Speaker 2>But beyond tools, it's about the troubleshooting methodology. A systematic

274
00:13:27.519 --> 00:13:30.399
<v Speaker 2>approach is crucial. The guide has a good seven step one.

275
00:13:30.720 --> 00:13:36.120
<v Speaker 2>One identify the problem, gatter symptoms, what's actually wrong? What changed? Two?

276
00:13:36.639 --> 00:13:40.480
<v Speaker 2>Theorize the cause, make an educated guess, use the OSI model,

277
00:13:40.679 --> 00:13:45.279
<v Speaker 2>is it physical network application? Three? Test your theory. Try

278
00:13:45.320 --> 00:13:48.120
<v Speaker 2>one thing based on your theory. Unplug that cable, restart

279
00:13:48.120 --> 00:13:51.080
<v Speaker 2>that service. Four plan the fix. If your test work,

280
00:13:51.159 --> 00:13:54.039
<v Speaker 2>figure out the steps to implement the solution properly. Five,

281
00:13:54.360 --> 00:13:58.080
<v Speaker 2>implement the fix. Six verify did it fix the original problem?

282
00:13:58.120 --> 00:14:01.000
<v Speaker 2>Did it break anything else? Maybe implement preventive measures now.

283
00:14:01.159 --> 00:14:03.919
<v Speaker 2>Seven document write down what happened, what you did, and

284
00:14:03.960 --> 00:14:06.960
<v Speaker 2>the outcome, so important for next time. Following a process

285
00:14:07.000 --> 00:14:09.279
<v Speaker 2>like this will turns panic into problem solving. It makes

286
00:14:09.320 --> 00:14:12.360
<v Speaker 2>you methodical and it raises a key point. Troubleshooting isn't

287
00:14:12.399 --> 00:14:15.240
<v Speaker 2>just fixing, it's learning, preventing future issues and building a

288
00:14:15.240 --> 00:14:18.320
<v Speaker 2>more reliable network for yourself. Hashtag had outroge.

289
00:14:18.480 --> 00:14:21.840
<v Speaker 1>Wow, Okay, that was a lot, but incredibly useful. We've

290
00:14:21.879 --> 00:14:25.639
<v Speaker 1>gone from basic protocols the language's devices speak through the

291
00:14:25.639 --> 00:14:30.080
<v Speaker 1>OSI models layers to the actual hardware like switches and routers,

292
00:14:30.360 --> 00:14:34.759
<v Speaker 1>how addressing like IPDHCP and DNS works, and finally into

293
00:14:34.799 --> 00:14:37.919
<v Speaker 1>securing it all and fixing it when it breaks. I

294
00:14:37.919 --> 00:14:40.039
<v Speaker 1>feel like you really do have a solid foundation now

295
00:14:40.039 --> 00:14:42.639
<v Speaker 1>for understanding this digital world we live in.

296
00:14:42.759 --> 00:14:45.080
<v Speaker 2>Absolutely the goal wasn't just facts, but a way to

297
00:14:45.080 --> 00:14:47.080
<v Speaker 2>think about it right. To see the connections every time

298
00:14:47.120 --> 00:14:49.200
<v Speaker 2>you load a web page, send an email, make a

299
00:14:49.200 --> 00:14:52.759
<v Speaker 2>secure payment. All these principles we discussed are working together

300
00:14:52.799 --> 00:14:54.559
<v Speaker 2>behind the scenes. It's quite an ecosystem.

301
00:14:54.840 --> 00:14:58.279
<v Speaker 1>Definitely had some aha moments there. We hope this deep

302
00:14:58.320 --> 00:15:01.200
<v Speaker 1>dive helps you feel more informed, may be less intimidated

303
00:15:01.240 --> 00:15:03.320
<v Speaker 1>by the tech around you. So here's the thought to

304
00:15:03.360 --> 00:15:06.039
<v Speaker 1>leave you with next time your internet seems slow or

305
00:15:06.039 --> 00:15:09.039
<v Speaker 1>an app won't connect. Instead of just reaching for the reboot,

306
00:15:09.080 --> 00:15:12.440
<v Speaker 1>buttons straight away, Will you maybe pause and think in layers?

307
00:15:12.759 --> 00:15:16.679
<v Speaker 1>Ask yourself what language might be failing, Which device could

308
00:15:16.679 --> 00:15:20.919
<v Speaker 1>be the bottleneck, what security rule might be interfering. Thanks

309
00:15:20.919 --> 00:15:23.720
<v Speaker 1>for joining us on the deep dive. Keep exploring, keep questioning,