WEBVTT

1
00:00:00.000 --> 00:00:02.520
<v Speaker 1>All right, so you're about to dive into p sense

2
00:00:02.919 --> 00:00:07.360
<v Speaker 1>sense a firewall so powerful that even giants like Google

3
00:00:07.480 --> 00:00:11.000
<v Speaker 1>and NASA rely on it. Crazy, right, and the kicker

4
00:00:11.759 --> 00:00:12.880
<v Speaker 1>it's completely free.

5
00:00:13.039 --> 00:00:14.320
<v Speaker 2>I know it's wild.

6
00:00:14.560 --> 00:00:16.679
<v Speaker 1>So let's peel back the layers and get you up

7
00:00:16.679 --> 00:00:19.039
<v Speaker 1>to speed on why p sense is such a big deal,

8
00:00:19.519 --> 00:00:21.600
<v Speaker 1>how to get it running, and how you can use

9
00:00:21.600 --> 00:00:24.960
<v Speaker 1>it to set up things like a DHCP server, craft

10
00:00:24.960 --> 00:00:27.760
<v Speaker 1>your own firewall rules. Yeah, and even turn it into

11
00:00:27.800 --> 00:00:28.800
<v Speaker 1>a squid proxy server.

12
00:00:29.039 --> 00:00:31.640
<v Speaker 2>Lots to cover. Oh yeah, it's pretty amazing how something

13
00:00:31.679 --> 00:00:36.280
<v Speaker 2>free can be trusted by organizations that demand top notch security.

14
00:00:36.560 --> 00:00:40.520
<v Speaker 2>And it really speaks volumes about how robust and versatile

15
00:00:40.520 --> 00:00:41.200
<v Speaker 2>pfense is.

16
00:00:41.359 --> 00:00:44.679
<v Speaker 1>Yeah, so what's the secret, sauce. What is it about

17
00:00:44.719 --> 00:00:46.320
<v Speaker 1>p sense that makes it so popular?

18
00:00:46.399 --> 00:00:49.240
<v Speaker 2>Well, at its core, pfence is an open source firewall

19
00:00:49.280 --> 00:00:53.560
<v Speaker 2>built on FreeBSD, which is known for its stability and security. Okay,

20
00:00:53.600 --> 00:00:55.600
<v Speaker 2>but it's more than just a firewall. It's like a

21
00:00:55.719 --> 00:00:58.159
<v Speaker 2>multi tool for your network. You can use it as

22
00:00:58.159 --> 00:01:03.399
<v Speaker 2>your main router, wire hot spot, a VPN server, pull.

23
00:01:03.240 --> 00:01:05.519
<v Speaker 1>A VPN server too. Yeah, I could use this to

24
00:01:05.799 --> 00:01:09.760
<v Speaker 1>securely access my home network from anywhere in the world.

25
00:01:09.519 --> 00:01:12.000
<v Speaker 2>Exactly really, and that's just scratching the surface.

26
00:01:12.120 --> 00:01:12.519
<v Speaker 1>Oh wow.

27
00:01:12.680 --> 00:01:16.079
<v Speaker 2>It can also act as a DHCP and DNS server,

28
00:01:16.719 --> 00:01:21.200
<v Speaker 2>handle multiple Internet connections for backup or faster speeds, and

29
00:01:21.239 --> 00:01:23.959
<v Speaker 2>even manage how traffic flows in and out of your network.

30
00:01:24.120 --> 00:01:25.000
<v Speaker 1>So it can do all that.

31
00:01:25.120 --> 00:01:27.840
<v Speaker 2>It's like having a Swiss army knife for network management,

32
00:01:28.280 --> 00:01:31.560
<v Speaker 2>but instead of a tiny blade, you get industrial grade tools.

33
00:01:31.680 --> 00:01:33.680
<v Speaker 1>All right, I'm sold. Let's get this thing run in

34
00:01:33.760 --> 00:01:34.920
<v Speaker 1>Oh where do we even start?

35
00:01:35.079 --> 00:01:37.280
<v Speaker 2>Well, the latest version is two point four point three

36
00:01:37.640 --> 00:01:39.439
<v Speaker 2>and the best part is you can test it out

37
00:01:39.680 --> 00:01:43.000
<v Speaker 2>without messing with your current setup, installing it on a

38
00:01:43.079 --> 00:01:43.879
<v Speaker 2>virtual machine.

39
00:01:43.959 --> 00:01:44.879
<v Speaker 1>Virtual machine.

40
00:01:45.000 --> 00:01:47.560
<v Speaker 2>Think of it like taking a car for a test

41
00:01:47.640 --> 00:01:49.920
<v Speaker 2>drive before you buy it. Okay, you get to experience

42
00:01:50.000 --> 00:01:51.719
<v Speaker 2>all the features without any risk.

43
00:01:51.959 --> 00:01:55.799
<v Speaker 1>Makes sense. So we download the installer, choose the right version,

44
00:01:56.040 --> 00:01:58.040
<v Speaker 1>and get that virtual machine rolling.

45
00:01:58.200 --> 00:02:00.359
<v Speaker 2>You got it, and the installation is pretty straight forward.

46
00:02:00.719 --> 00:02:03.439
<v Speaker 2>The installer walks you through choosing the right options for

47
00:02:03.519 --> 00:02:06.200
<v Speaker 2>your setup. Don't worry, it's simpler than it sounds.

48
00:02:06.239 --> 00:02:06.560
<v Speaker 1>Okay.

49
00:02:06.640 --> 00:02:09.159
<v Speaker 2>Once you're up and running, PF Sense has the super

50
00:02:09.360 --> 00:02:12.000
<v Speaker 2>user friendly web interface for configuration.

51
00:02:12.280 --> 00:02:16.199
<v Speaker 1>Web interface, no messing around with complicated command lines.

52
00:02:16.319 --> 00:02:17.919
<v Speaker 2>Nope, it's all point and click.

53
00:02:18.039 --> 00:02:18.360
<v Speaker 1>Wow.

54
00:02:18.439 --> 00:02:21.759
<v Speaker 2>You just log in with the default username, admin and

55
00:02:21.840 --> 00:02:24.280
<v Speaker 2>password sense okay, and you're in control.

56
00:02:24.439 --> 00:02:27.400
<v Speaker 1>Wait, hold on default password. Isn't that a security risk?

57
00:02:27.800 --> 00:02:29.560
<v Speaker 2>You're absolutely right. The first thing you should do is

58
00:02:29.639 --> 00:02:30.919
<v Speaker 2>change that default password.

59
00:02:31.039 --> 00:02:31.360
<v Speaker 1>Okay.

60
00:02:31.400 --> 00:02:34.800
<v Speaker 2>P Sense takes security seriously, but it's always best to

61
00:02:34.919 --> 00:02:36.960
<v Speaker 2>personalize those credentials right away.

62
00:02:37.199 --> 00:02:40.960
<v Speaker 1>Good point. So once we're in Prick, what kind of

63
00:02:40.960 --> 00:02:43.280
<v Speaker 1>things can we configure? Right off the bat?

64
00:02:43.439 --> 00:02:46.719
<v Speaker 2>The setup wizard will guide you through the essentials okay,

65
00:02:46.759 --> 00:02:50.280
<v Speaker 2>like naming your PF sense system okay, setting up DNS

66
00:02:50.319 --> 00:02:54.800
<v Speaker 2>servers you can even use Google's public DNS, and synchronizing

67
00:02:54.840 --> 00:02:58.080
<v Speaker 2>the time okay. You'll also configure your main internet connection

68
00:02:58.240 --> 00:03:01.039
<v Speaker 2>and your local network connection. All very straightforward.

69
00:03:01.080 --> 00:03:05.039
<v Speaker 1>Got it? Now? You mentioned DHCP server earlier. Yeah, I

70
00:03:05.039 --> 00:03:07.840
<v Speaker 1>know it has something to do with like automatically assigning

71
00:03:08.000 --> 00:03:11.319
<v Speaker 1>IP addresses, But how does that actually benefit me?

72
00:03:11.479 --> 00:03:14.479
<v Speaker 2>Think of DHDP as a concierge for your devices.

73
00:03:14.680 --> 00:03:15.039
<v Speaker 1>Okay.

74
00:03:15.360 --> 00:03:18.120
<v Speaker 2>Instead of you having to manually assign a unique IP

75
00:03:18.199 --> 00:03:22.120
<v Speaker 2>address to every phone, laptop, or smart fridge that connects

76
00:03:22.120 --> 00:03:26.360
<v Speaker 2>to your network, DHCP does it automatically it's like having

77
00:03:26.400 --> 00:03:29.639
<v Speaker 2>a virtual receptionist that hands out room keys as guests arrived.

78
00:03:29.840 --> 00:03:32.439
<v Speaker 1>So basically, it saves me a ton of time and hassle,

79
00:03:33.120 --> 00:03:35.479
<v Speaker 1>especially if I have a lot of devices on my network.

80
00:03:35.560 --> 00:03:38.479
<v Speaker 2>Exactly, and pfsense makes it super easy to set up

81
00:03:38.479 --> 00:03:40.560
<v Speaker 2>a DHCP server on your local network.

82
00:03:40.639 --> 00:03:41.039
<v Speaker 1>Oh wow.

83
00:03:41.080 --> 00:03:43.599
<v Speaker 2>You get to customize things like the IP address range

84
00:03:43.599 --> 00:03:46.439
<v Speaker 2>and DNS server settings. It's like being the architect of

85
00:03:46.479 --> 00:03:50.080
<v Speaker 2>your own little digital city, and DHCP keeps everything running smoothly.

86
00:03:50.680 --> 00:03:52.840
<v Speaker 1>All right, I'm starting to feel like a networking pro.

87
00:03:53.520 --> 00:03:57.319
<v Speaker 1>No good. Let's talk about the heart of pepsense, the firewall.

88
00:03:57.599 --> 00:04:01.400
<v Speaker 2>This is where things get really interesting. Imagine a firewall

89
00:04:01.479 --> 00:04:04.479
<v Speaker 2>as a security guard standing at the entrance of your network.

90
00:04:04.639 --> 00:04:09.520
<v Speaker 2>It's constantly checking incoming and outgoing traffic, deciding who gets

91
00:04:09.520 --> 00:04:11.879
<v Speaker 2>in and who gets bounced based on the rules you set.

92
00:04:12.039 --> 00:04:15.719
<v Speaker 1>So PSNS is already secure by default, but I can

93
00:04:15.759 --> 00:04:18.600
<v Speaker 1>customize the rules for even more control. You got it.

94
00:04:18.959 --> 00:04:23.439
<v Speaker 2>Pfsense gives you granular control over your network traffic. Okay,

95
00:04:23.680 --> 00:04:26.959
<v Speaker 2>you can create rules for specific types of connections, like

96
00:04:27.000 --> 00:04:30.480
<v Speaker 2>those used for websites, email, or even online games.

97
00:04:30.600 --> 00:04:31.040
<v Speaker 1>Oh wow.

98
00:04:31.160 --> 00:04:33.439
<v Speaker 2>Think of it like having a set of bouncers at

99
00:04:33.439 --> 00:04:36.920
<v Speaker 2>a nightclub, each specializing and different genre of music.

100
00:04:37.079 --> 00:04:39.959
<v Speaker 1>I like that analogy. So I can block certain types

101
00:04:39.959 --> 00:04:42.519
<v Speaker 1>of traffic altogether. Absolutely, Like maybe I want to block

102
00:04:42.560 --> 00:04:44.279
<v Speaker 1>social media sites during work hours.

103
00:04:44.319 --> 00:04:47.439
<v Speaker 2>Absolutely. You can get very specific with the rules, wow,

104
00:04:47.600 --> 00:04:51.040
<v Speaker 2>allowing or blocking traffic based on the source, destination, port

105
00:04:51.199 --> 00:04:54.920
<v Speaker 2>protocol and even the time of day. You're essentially crafting

106
00:04:54.959 --> 00:04:58.480
<v Speaker 2>your own network security policy tailored exactly to your needs.

107
00:04:58.680 --> 00:05:00.600
<v Speaker 1>So it really lets you like find tune things to

108
00:05:00.680 --> 00:05:01.560
<v Speaker 1>exactly how you want.

109
00:05:01.720 --> 00:05:02.480
<v Speaker 2>Yeah, exactly.

110
00:05:02.720 --> 00:05:06.319
<v Speaker 1>Now you mentioned the tfsense processes these firewall rules in

111
00:05:06.399 --> 00:05:08.720
<v Speaker 1>a specific order. Why is that important?

112
00:05:08.959 --> 00:05:11.920
<v Speaker 2>Think of it like a checklistf sense goes through the

113
00:05:12.000 --> 00:05:15.639
<v Speaker 2>rules one by one, from top to bottom. The first

114
00:05:15.759 --> 00:05:19.839
<v Speaker 2>rule that matches the incoming or outgoing traffic determines.

115
00:05:19.360 --> 00:05:21.519
<v Speaker 1>What happens, So the order matters.

116
00:05:21.600 --> 00:05:23.800
<v Speaker 2>That's why the order of your rules is crucial. It's

117
00:05:23.800 --> 00:05:26.040
<v Speaker 2>like setting priorities for your security guard.

118
00:05:26.800 --> 00:05:28.959
<v Speaker 1>So if I have a rule at the top that

119
00:05:29.040 --> 00:05:32.720
<v Speaker 1>blocks all traffic from a specific country and a rule

120
00:05:32.759 --> 00:05:36.560
<v Speaker 1>below it that allows traffic from everyone, the first rule

121
00:05:36.600 --> 00:05:39.519
<v Speaker 1>will win and no one from that country will get through.

122
00:05:39.600 --> 00:05:43.199
<v Speaker 2>You got it. It's all about understanding how pf sense

123
00:05:43.240 --> 00:05:46.480
<v Speaker 2>evaluates those rules and making sure they're in the right

124
00:05:46.600 --> 00:05:49.120
<v Speaker 2>order to enforce your security policy.

125
00:05:49.199 --> 00:05:51.160
<v Speaker 1>So it's kind of like a strategy game. Almost.

126
00:05:51.279 --> 00:05:54.319
<v Speaker 2>Yeah, it's a bit like playing a strategic game of traffic.

127
00:05:54.000 --> 00:05:56.480
<v Speaker 1>Cop This is amazing. It's like I'm learning a secret

128
00:05:56.519 --> 00:05:57.720
<v Speaker 1>language of network control.

129
00:05:57.839 --> 00:05:58.199
<v Speaker 2>Uh huh.

130
00:05:58.480 --> 00:05:59.920
<v Speaker 1>But I'm sure there's more to income.

131
00:06:00.279 --> 00:06:01.800
<v Speaker 2>Oh, there's plenty more to explore.

132
00:06:01.839 --> 00:06:03.759
<v Speaker 1>All right, I'm ready for the next level. Lead the way.

133
00:06:04.160 --> 00:06:06.519
<v Speaker 2>Let's do it. Okay, so you're ready to level up.

134
00:06:06.600 --> 00:06:07.040
<v Speaker 1>Let's do it.

135
00:06:07.160 --> 00:06:09.240
<v Speaker 2>Let's talk about something called network segmentation.

136
00:06:09.720 --> 00:06:10.879
<v Speaker 1>Network segmentation.

137
00:06:11.199 --> 00:06:14.959
<v Speaker 2>Remember how we said PFSENS could create isolated networks.

138
00:06:15.120 --> 00:06:15.680
<v Speaker 1>Uh huh.

139
00:06:15.720 --> 00:06:17.399
<v Speaker 2>This is where it gets really powerful.

140
00:06:17.480 --> 00:06:20.720
<v Speaker 1>Okay, network segmentation. It sounds kind of techy. Break it

141
00:06:20.759 --> 00:06:21.240
<v Speaker 1>down for me.

142
00:06:21.480 --> 00:06:23.199
<v Speaker 2>Imagine your network as a house.

143
00:06:23.439 --> 00:06:23.759
<v Speaker 1>Okay.

144
00:06:23.800 --> 00:06:27.319
<v Speaker 2>With PFSENS, you can build walls and create separate rooms.

145
00:06:27.879 --> 00:06:30.240
<v Speaker 2>You could have a living room for your trusted devices,

146
00:06:30.959 --> 00:06:34.759
<v Speaker 2>a guest room for visitors who need internet access, okay,

147
00:06:34.879 --> 00:06:38.040
<v Speaker 2>and even a garage for those Internet connected gadgets that

148
00:06:38.079 --> 00:06:39.319
<v Speaker 2>make you a little nervous.

149
00:06:39.639 --> 00:06:42.519
<v Speaker 1>Oh, so I could have my main computers and phones

150
00:06:42.680 --> 00:06:45.720
<v Speaker 1>on one network. Yeah, my smart TV and gaming console

151
00:06:45.759 --> 00:06:48.720
<v Speaker 1>on another, and maybe even all those smart light bulbs

152
00:06:48.720 --> 00:06:52.279
<v Speaker 1>and thermostats on a completely separate network exactly.

153
00:06:52.800 --> 00:06:54.600
<v Speaker 2>And the beauty of it is you control the traffic

154
00:06:54.639 --> 00:06:57.759
<v Speaker 2>flow between these segments. Oh, you decide who gets to

155
00:06:57.800 --> 00:07:00.480
<v Speaker 2>talk to whom. It's like having a secure guard at

156
00:07:00.519 --> 00:07:03.319
<v Speaker 2>each door, making sure only authorized personnel can enter.

157
00:07:03.639 --> 00:07:06.480
<v Speaker 1>So if one of those smart light bulbs gets hacked. Yeah,

158
00:07:06.519 --> 00:07:08.360
<v Speaker 1>and let's face it, some of those things are about

159
00:07:08.360 --> 00:07:11.319
<v Speaker 1>as secure as a cardboard box. It can't snoop around

160
00:07:11.319 --> 00:07:13.600
<v Speaker 1>on my main computer or steal my passwords.

161
00:07:13.680 --> 00:07:16.480
<v Speaker 2>You got it. It's all about minimizing risk.

162
00:07:16.680 --> 00:07:17.040
<v Speaker 1>Okay.

163
00:07:17.199 --> 00:07:20.360
<v Speaker 2>By isolating devices, you contain potential threats and keep your

164
00:07:20.399 --> 00:07:21.920
<v Speaker 2>most valuable data safe.

165
00:07:22.240 --> 00:07:22.720
<v Speaker 1>Makes sense.

166
00:07:22.920 --> 00:07:25.839
<v Speaker 2>Plus it can even help with performance, really, keeping those

167
00:07:25.959 --> 00:07:28.680
<v Speaker 2>chatty smart devices from hogging all the bandwidth.

168
00:07:28.680 --> 00:07:32.639
<v Speaker 1>So it's good for security and speed exactly. That's brilliant.

169
00:07:32.720 --> 00:07:35.519
<v Speaker 1>So pf sense really lets you become the architect of

170
00:07:35.560 --> 00:07:39.399
<v Speaker 1>your own network, designing it for security and efficiency. Yeah,

171
00:07:39.480 --> 00:07:43.560
<v Speaker 1>it's like playing digital SimCity, but with real world benefits exactly.

172
00:07:44.040 --> 00:07:46.639
<v Speaker 2>And speaking of security, remember how pfsens is built on

173
00:07:46.720 --> 00:07:49.800
<v Speaker 2>FreeBSD Oh. Yeah, that's a big part of what makes

174
00:07:49.800 --> 00:07:51.240
<v Speaker 2>it so stable and secure.

175
00:07:51.360 --> 00:07:55.040
<v Speaker 1>Okay, let's unpack this FreeBSD thing. What exactly is it?

176
00:07:55.079 --> 00:07:56.000
<v Speaker 1>And why should I care?

177
00:07:56.360 --> 00:07:58.839
<v Speaker 2>Think of FreeBSD as the foundation of your house.

178
00:07:59.000 --> 00:07:59.279
<v Speaker 1>Okay.

179
00:07:59.319 --> 00:08:02.600
<v Speaker 2>It's an operator system known for its rock solid stability

180
00:08:02.639 --> 00:08:06.959
<v Speaker 2>and bulletproof security. It's been around for decades, powering everything

181
00:08:07.000 --> 00:08:11.759
<v Speaker 2>from servers to supercomputers. So pfsense takes this super reliable

182
00:08:11.800 --> 00:08:15.759
<v Speaker 2>foundation and builds all these amazing firewall and networking features

183
00:08:15.759 --> 00:08:18.079
<v Speaker 2>on top of it precisely. Okay, it's like constructing a

184
00:08:18.079 --> 00:08:22.639
<v Speaker 2>skyscraper on bedrock. You're starting with a strong and stable base, gotcha,

185
00:08:22.680 --> 00:08:26.040
<v Speaker 2>And it means pfsns can handle even demanding network traffic

186
00:08:26.160 --> 00:08:30.680
<v Speaker 2>with ease. Plus. FreeBSD is known for its efficiency, meaning

187
00:08:30.839 --> 00:08:34.080
<v Speaker 2>pf sense can run smoothly even on older hardware, so

188
00:08:34.159 --> 00:08:34.759
<v Speaker 2>I don't need.

189
00:08:34.600 --> 00:08:37.519
<v Speaker 1>A top of the line server to run pfsense.

190
00:08:37.159 --> 00:08:40.120
<v Speaker 2>Not at all. The latest version can actually run on

191
00:08:40.159 --> 00:08:41.399
<v Speaker 2>a fairly modest PC.

192
00:08:41.799 --> 00:08:42.159
<v Speaker 1>Really.

193
00:08:42.360 --> 00:08:44.960
<v Speaker 2>Of course, having a bit more horsepower never hurts, but

194
00:08:45.080 --> 00:08:48.039
<v Speaker 2>keepsense won't break the bank when it comes to hardware requirements.

195
00:08:48.080 --> 00:08:50.600
<v Speaker 1>That's good to know. Yeah, okay, I'm ready to jump

196
00:08:50.679 --> 00:08:53.639
<v Speaker 1>back into that user friendly web interface we talked about earlier.

197
00:08:53.720 --> 00:08:55.600
<v Speaker 1>All Right, what are some of the key areas I

198
00:08:55.600 --> 00:08:56.320
<v Speaker 1>should know about?

199
00:08:56.440 --> 00:08:59.879
<v Speaker 2>Well, the pfsn's web interface is like the control sen

200
00:09:00.279 --> 00:09:04.000
<v Speaker 2>for your network. It's incredibly well organized and intuitive, even

201
00:09:04.000 --> 00:09:05.120
<v Speaker 2>if you're not a tech whiz.

202
00:09:05.320 --> 00:09:09.000
<v Speaker 1>Good. I remember you mentioned a system menu earlier, Right,

203
00:09:09.159 --> 00:09:10.759
<v Speaker 1>what kind of things can I tweak in there?

204
00:09:11.000 --> 00:09:13.240
<v Speaker 2>The system menu is where you'll find all the behind

205
00:09:13.279 --> 00:09:15.919
<v Speaker 2>the scenes settings. Okay, think of it like the settings

206
00:09:15.960 --> 00:09:20.080
<v Speaker 2>app on your phone. You can manage certificates, adjust general settings,

207
00:09:20.360 --> 00:09:24.399
<v Speaker 2>and even fine tune how pf sense logs events. And

208
00:09:24.480 --> 00:09:27.559
<v Speaker 2>speaking of security, there's a user manager in there where

209
00:09:27.600 --> 00:09:30.360
<v Speaker 2>you can create accounts for other people and set their permissions.

210
00:09:30.440 --> 00:09:33.399
<v Speaker 1>So if I want to give someone access to manage

211
00:09:33.399 --> 00:09:37.039
<v Speaker 1>the network but not mess with sensitive settings, right.

212
00:09:37.200 --> 00:09:40.200
<v Speaker 2>I can do that exactly. It's all about controlling who

213
00:09:40.240 --> 00:09:42.759
<v Speaker 2>has access to what, Just like those security guards at

214
00:09:42.799 --> 00:09:44.000
<v Speaker 2>the doors of our networkhouse.

215
00:09:44.120 --> 00:09:45.120
<v Speaker 1>I like that analogy.

216
00:09:45.200 --> 00:09:49.000
<v Speaker 2>You can even disable the default admin account for extra security.

217
00:09:49.240 --> 00:09:50.919
<v Speaker 2>Always a good practice.

218
00:09:50.600 --> 00:09:54.440
<v Speaker 1>Smart move. So what about managing those different network segments

219
00:09:54.440 --> 00:09:56.440
<v Speaker 1>we talked about earlier? Yeah, where do I do that?

220
00:09:56.440 --> 00:09:58.600
<v Speaker 2>That's all handled in the interfaces menu.

221
00:09:58.720 --> 00:09:59.840
<v Speaker 1>Interfaces you'll see your.

222
00:09:59.759 --> 00:10:04.159
<v Speaker 2>Main Internet connection and your local network there plus any

223
00:10:04.159 --> 00:10:07.000
<v Speaker 2>additional interfaces you've created for those segment of networks.

224
00:10:07.120 --> 00:10:10.399
<v Speaker 1>So I could have a separate interface for my smart

225
00:10:10.399 --> 00:10:13.159
<v Speaker 1>home network, another for my guest network, and so on.

226
00:10:13.360 --> 00:10:15.919
<v Speaker 2>You got it, And pf sense lets you rename those

227
00:10:15.960 --> 00:10:19.480
<v Speaker 2>interfaces for clarity, so instead of just land, you could

228
00:10:19.519 --> 00:10:22.360
<v Speaker 2>have smart home or guest WIY. Much easier to keep things.

229
00:10:22.240 --> 00:10:26.639
<v Speaker 1>Straight, right, Definitely, I'm all about making things easy to understand. Yeah,

230
00:10:26.679 --> 00:10:29.399
<v Speaker 1>So what about the actual firewall rules? Where do I

231
00:10:29.480 --> 00:10:30.000
<v Speaker 1>find those?

232
00:10:30.200 --> 00:10:33.080
<v Speaker 2>That's all in the firewall menu, of course. Firewall menu,

233
00:10:33.200 --> 00:10:35.639
<v Speaker 2>it's where you'll spend most of your time fine tuning

234
00:10:35.720 --> 00:10:39.039
<v Speaker 2>how PSNS handles traffic. Okay, you'll find everything you need

235
00:10:39.080 --> 00:10:41.399
<v Speaker 2>to create rules managed NAT, which we'll talk about more

236
00:10:41.399 --> 00:10:43.799
<v Speaker 2>in a bit shape traffic, and even set up virtual

237
00:10:43.799 --> 00:10:44.639
<v Speaker 2>IP addresses.

238
00:10:45.000 --> 00:10:48.559
<v Speaker 1>Okay, that sounds pretty powerful. And what about other services

239
00:10:48.559 --> 00:10:51.799
<v Speaker 1>like DHDP and DNS. Yeah, where do those live in

240
00:10:51.799 --> 00:10:52.519
<v Speaker 1>this interface?

241
00:10:52.600 --> 00:10:55.960
<v Speaker 2>That's all in the handy dandy services menu. You can

242
00:10:56.000 --> 00:11:01.440
<v Speaker 2>manage DHCP, DNS, dynamic DNS. We'll explain that one later, okay,

243
00:11:01.480 --> 00:11:03.799
<v Speaker 2>and a whole bunch of other network services that pfsens

244
00:11:03.840 --> 00:11:06.000
<v Speaker 2>can handle. It's like a one stop shop for all

245
00:11:06.039 --> 00:11:07.039
<v Speaker 2>your networking needs.

246
00:11:07.279 --> 00:11:11.440
<v Speaker 1>Wow. This web interface is seriously impressive. It is so

247
00:11:11.600 --> 00:11:14.240
<v Speaker 1>much control all in one place. Yeah, and what about

248
00:11:14.240 --> 00:11:16.879
<v Speaker 1>those VPNs We talked about setting up secure connections to

249
00:11:16.919 --> 00:11:17.600
<v Speaker 1>my home network.

250
00:11:17.720 --> 00:11:20.600
<v Speaker 2>Ah, yes, the VPNs. You'll find all the options for

251
00:11:20.639 --> 00:11:24.639
<v Speaker 2>that in the VPM menu. VBM kefcent supports IPsec, OpenVPN,

252
00:11:24.720 --> 00:11:28.159
<v Speaker 2>and l two tpvpns, giving you lots of choices depending

253
00:11:28.159 --> 00:11:29.919
<v Speaker 2>on your needs and the devices you're using.

254
00:11:30.000 --> 00:11:31.919
<v Speaker 1>So I could set up a secure connection to my

255
00:11:32.000 --> 00:11:35.080
<v Speaker 1>home network for my laptop while I'm traveling, even if

256
00:11:35.080 --> 00:11:37.519
<v Speaker 1>I'm using a public Wi Fi network at a coffee shop.

257
00:11:37.559 --> 00:11:41.159
<v Speaker 2>You got it. VPNs encrypt your traffic, creating a secured

258
00:11:41.240 --> 00:11:45.039
<v Speaker 2>tunnel through the Internet. It's like having a private bodyguard

259
00:11:45.279 --> 00:11:47.120
<v Speaker 2>escorting your data wherever it goes.

260
00:11:47.360 --> 00:11:50.399
<v Speaker 1>Nice. Okay, so lots of choices there for different situations. Yep,

261
00:11:50.759 --> 00:11:52.960
<v Speaker 1>this is amazing. But hold on, there's one more menu

262
00:11:53.080 --> 00:11:55.799
<v Speaker 1>you mentioned status, right. What's that all about.

263
00:11:56.039 --> 00:11:58.759
<v Speaker 2>The Status menu is like your network's dashboard. It gives

264
00:11:58.759 --> 00:12:00.360
<v Speaker 2>you a real time view of what's happening.

265
00:12:00.639 --> 00:12:01.000
<v Speaker 1>Okay.

266
00:12:01.039 --> 00:12:03.759
<v Speaker 2>You can check system logs, see traffic flowing in and out,

267
00:12:04.039 --> 00:12:06.919
<v Speaker 2>and even monitor the health of different services. It's like

268
00:12:07.159 --> 00:12:09.639
<v Speaker 2>having X ray vision into your network so you can

269
00:12:09.960 --> 00:12:12.720
<v Speaker 2>spot any potential issues before they become problem.

270
00:12:12.799 --> 00:12:15.759
<v Speaker 1>It sounds incredibly useful. Yeah, it is, so I can

271
00:12:15.840 --> 00:12:18.639
<v Speaker 1>quickly see if there's a sudden spike in traffic or

272
00:12:18.679 --> 00:12:21.600
<v Speaker 1>if a particular service isn't working properly exactly.

273
00:12:22.399 --> 00:12:25.120
<v Speaker 2>The status menu is your go to place for keeping

274
00:12:25.159 --> 00:12:28.000
<v Speaker 2>tabs on your network's well being. It's like having a

275
00:12:28.000 --> 00:12:31.200
<v Speaker 2>team of network doctors constantly monitoring vital signs.

276
00:12:31.519 --> 00:12:34.639
<v Speaker 1>Okay, all this talk about security and controls making me

277
00:12:34.720 --> 00:12:38.279
<v Speaker 1>feel like a digital superhero. Uh huh, But let's go

278
00:12:38.360 --> 00:12:40.440
<v Speaker 1>back to one of those core features we haven't delved

279
00:12:40.440 --> 00:12:45.399
<v Speaker 1>into yet. Okay, Network Address translation or net What exactly

280
00:12:45.519 --> 00:12:46.840
<v Speaker 1>is it and why should I care?

281
00:12:47.000 --> 00:12:50.200
<v Speaker 2>Great question. NAT is one of those behind the scenes

282
00:12:50.240 --> 00:12:52.080
<v Speaker 2>technologies that makes the Internet work.

283
00:12:52.360 --> 00:12:52.679
<v Speaker 1>Okay.

284
00:12:52.879 --> 00:12:55.240
<v Speaker 2>Imagine you have a whole bunch of devices in your home,

285
00:12:55.360 --> 00:12:56.879
<v Speaker 2>all wanting to access the Internet.

286
00:12:56.960 --> 00:13:00.720
<v Speaker 1>That's my house for sure, Phones, laptops, tablets, gaming consoles

287
00:13:00.759 --> 00:13:02.559
<v Speaker 1>that are all fighting for bandwidth.

288
00:13:02.080 --> 00:13:05.639
<v Speaker 2>Exactly, But your internet provider only gives you one public

289
00:13:05.679 --> 00:13:09.759
<v Speaker 2>IP address, like a single street address for your entire house. Okay,

290
00:13:10.159 --> 00:13:14.360
<v Speaker 2>NAT acts like a super efficient mailroom, taking all those

291
00:13:14.399 --> 00:13:16.879
<v Speaker 2>requests from your devices and bundling them up to go

292
00:13:16.960 --> 00:13:18.639
<v Speaker 2>out through that single IP address.

293
00:13:18.919 --> 00:13:22.200
<v Speaker 1>So it's like NAT is giving each device a temporary

294
00:13:22.240 --> 00:13:26.159
<v Speaker 1>disguise so they can all share that one public IP address.

295
00:13:26.240 --> 00:13:29.480
<v Speaker 2>You've got it. It's like a costume party for your devices,

296
00:13:29.519 --> 00:13:32.320
<v Speaker 2>allowing them to slip out into the Internet world unnoticed.

297
00:13:32.559 --> 00:13:33.840
<v Speaker 1>Uh huh. I like it.

298
00:13:34.440 --> 00:13:37.559
<v Speaker 2>But NAT does more than just save IP addresses. It

299
00:13:37.639 --> 00:13:39.200
<v Speaker 2>also enhances security.

300
00:13:39.879 --> 00:13:40.960
<v Speaker 1>Oh really? How so?

301
00:13:41.200 --> 00:13:44.159
<v Speaker 2>Well, because all your devices are sharing that single public

302
00:13:44.240 --> 00:13:47.799
<v Speaker 2>IP address, anyone trying to connect from the outside can't

303
00:13:47.840 --> 00:13:51.600
<v Speaker 2>directly see the individual devices inside your network. It's like

304
00:13:51.679 --> 00:13:53.679
<v Speaker 2>having a privacy fence around your house. People can see

305
00:13:53.720 --> 00:13:55.759
<v Speaker 2>the address, but they can't peek inside to see who's home.

306
00:13:55.879 --> 00:13:58.679
<v Speaker 1>So NAT acts as a shield protecting my devices from

307
00:13:58.720 --> 00:14:02.000
<v Speaker 1>prying eyes exactly. I like that. Yeah, And you mentioned

308
00:14:02.000 --> 00:14:05.679
<v Speaker 1>that pfense excels at net. What makes it so special

309
00:14:05.720 --> 00:14:06.360
<v Speaker 1>in that regard?

310
00:14:06.919 --> 00:14:10.200
<v Speaker 2>Pfense gives you a ton of flexibility With NAT. You

311
00:14:10.240 --> 00:14:12.399
<v Speaker 2>can set up port forwarding, which is like having a

312
00:14:12.440 --> 00:14:16.320
<v Speaker 2>special delivery service for specific applications. You can create one

313
00:14:16.320 --> 00:14:20.519
<v Speaker 2>to one net mappings, giving certain devices their own dedicated disguises,

314
00:14:21.039 --> 00:14:25.080
<v Speaker 2>and you can even manage outbound net controlling how traffic

315
00:14:25.159 --> 00:14:27.279
<v Speaker 2>from your internal network gets translated.

316
00:14:27.480 --> 00:14:31.000
<v Speaker 1>So PFSENS gives me fine grain control over how networks,

317
00:14:31.559 --> 00:14:33.559
<v Speaker 1>tailoring it to my specific needs.

318
00:14:33.720 --> 00:14:36.399
<v Speaker 2>Exactly. It's like having a master key to the mail room,

319
00:14:36.679 --> 00:14:39.759
<v Speaker 2>allowing you to customize how those packages get delivered.

320
00:14:39.919 --> 00:14:40.320
<v Speaker 1>Nice.

321
00:14:40.399 --> 00:14:43.960
<v Speaker 2>And here's the really cool part. Pfsens can handle multiple

322
00:14:44.000 --> 00:14:44.960
<v Speaker 2>Internet connections.

323
00:14:45.360 --> 00:14:48.039
<v Speaker 1>With multiple Internet connections, so I could have two separate

324
00:14:48.039 --> 00:14:49.679
<v Speaker 1>Internet providers coming into my house.

325
00:14:49.799 --> 00:14:53.919
<v Speaker 2>You could, and pfsense can distribute traffic across those connections

326
00:14:54.039 --> 00:14:57.080
<v Speaker 2>really either for faster speeds. Think of it like adding

327
00:14:57.080 --> 00:15:00.639
<v Speaker 2>more lanes to a highway, or for redundancy. So if

328
00:15:00.639 --> 00:15:03.000
<v Speaker 2>one connection goes down, the other takes over seamlessly.

329
00:15:03.159 --> 00:15:03.840
<v Speaker 1>That's incredible.

330
00:15:03.960 --> 00:15:04.440
<v Speaker 2>Yeah, it is.

331
00:15:04.519 --> 00:15:07.320
<v Speaker 1>So psens could keep my Internet running even if one

332
00:15:07.360 --> 00:15:08.519
<v Speaker 1>connection has a hiccup.

333
00:15:09.000 --> 00:15:09.919
<v Speaker 2>Exactly.

334
00:15:10.080 --> 00:15:11.799
<v Speaker 1>That's peace of mind right there. It's like having a

335
00:15:11.799 --> 00:15:13.200
<v Speaker 1>backup generator for my Internet.

336
00:15:13.320 --> 00:15:16.120
<v Speaker 2>Exactly. It's a game changer for anyone who relies on

337
00:15:16.159 --> 00:15:17.519
<v Speaker 2>a constant Internet connection.

338
00:15:17.639 --> 00:15:21.559
<v Speaker 1>Okay, I am officially blown away. I never realized how

339
00:15:21.639 --> 00:15:25.200
<v Speaker 1>much power and control I could have over my network.

340
00:15:25.320 --> 00:15:26.480
<v Speaker 2>It's pretty amazing.

341
00:15:26.759 --> 00:15:28.759
<v Speaker 1>But I have a feeling we're just getting started.

342
00:15:28.919 --> 00:15:29.279
<v Speaker 2>We are.

343
00:15:31.080 --> 00:15:36.000
<v Speaker 1>What else does psens have up its sleeve? Okay, my

344
00:15:36.039 --> 00:15:40.919
<v Speaker 1>mind is officially blown wide open, multiple Internet connections, network segmentation,

345
00:15:41.039 --> 00:15:44.480
<v Speaker 1>traffic shaping. It's a Lotsense is like a secret weapon

346
00:15:44.480 --> 00:15:46.639
<v Speaker 1>for anyone who wants to take control of their network.

347
00:15:46.879 --> 00:15:48.759
<v Speaker 2>Yeah, and we haven't even touched on some of the

348
00:15:48.799 --> 00:15:50.399
<v Speaker 2>more advanced features yet.

349
00:15:50.440 --> 00:15:50.960
<v Speaker 1>Oh its more.

350
00:15:51.159 --> 00:15:53.200
<v Speaker 2>Remember those VPNs we talked about earlier.

351
00:15:53.279 --> 00:15:53.639
<v Speaker 1>Uh huh.

352
00:15:53.639 --> 00:15:57.200
<v Speaker 2>P sins can actually handle some pretty sophisticated VPN setups.

353
00:15:57.279 --> 00:15:59.960
<v Speaker 1>Okay, let's dive into that. Yeah, I'm all about taking

354
00:16:00.159 --> 00:16:01.799
<v Speaker 1>my network security to the next level.

355
00:16:01.840 --> 00:16:05.360
<v Speaker 2>All right, Well, imagine you have multiple offices or branches

356
00:16:05.440 --> 00:16:06.879
<v Speaker 2>that need to connect securely.

357
00:16:07.159 --> 00:16:07.480
<v Speaker 1>Okay.

358
00:16:07.519 --> 00:16:11.039
<v Speaker 2>P sense can create a permanent encrypted tunnel between those

359
00:16:11.080 --> 00:16:13.080
<v Speaker 2>networks using a protocol.

360
00:16:12.639 --> 00:16:15.000
<v Speaker 1>Called ip sc ip sec.

361
00:16:15.279 --> 00:16:19.200
<v Speaker 2>It's like having a dedicated secure pipeline for data to

362
00:16:19.240 --> 00:16:20.480
<v Speaker 2>flow between locations.

363
00:16:20.639 --> 00:16:22.720
<v Speaker 1>So it's like having all those offices on the same

364
00:16:22.759 --> 00:16:24.480
<v Speaker 1>local network, even though they're miles.

365
00:16:24.200 --> 00:16:27.840
<v Speaker 2>Apart, exactly. And because the traffic is encrypted, it's protected

366
00:16:27.840 --> 00:16:31.799
<v Speaker 2>from eavesdropping or tampering. It's like having an armored truck

367
00:16:31.919 --> 00:16:33.919
<v Speaker 2>transporting your data between locations.

368
00:16:33.960 --> 00:16:37.360
<v Speaker 1>That's impressive, and I'm guessing PFSENS makes this complex setup

369
00:16:37.440 --> 00:16:38.320
<v Speaker 1>easy to manage.

370
00:16:38.399 --> 00:16:41.360
<v Speaker 2>You bet. The web interface guides you through defining the

371
00:16:41.399 --> 00:16:45.240
<v Speaker 2>remote networks, setting up authentication to make sure only authorized

372
00:16:45.240 --> 00:16:49.519
<v Speaker 2>systems can connect. Okay, and choosing the right encryption algorithms

373
00:16:49.519 --> 00:16:50.720
<v Speaker 2>for maximum security.

374
00:16:50.799 --> 00:16:53.360
<v Speaker 1>Sounds like PSNSS thought of everything. But hold on, we

375
00:16:53.399 --> 00:16:56.320
<v Speaker 1>talked about network segmentation earlier, right, can I combine that

376
00:16:56.360 --> 00:16:59.480
<v Speaker 1>with VPNs? Like? Could I create a VPN connection that

377
00:16:59.600 --> 00:17:02.360
<v Speaker 1>only gets is access to specific parts of my network?

378
00:17:02.399 --> 00:17:05.240
<v Speaker 2>Absolutely? That's the beauty of PSNS. You can combine these

379
00:17:05.240 --> 00:17:07.680
<v Speaker 2>features in creative ways. You could set up a VPN

380
00:17:07.720 --> 00:17:10.720
<v Speaker 2>connection for remote employees that only gives them access to

381
00:17:11.240 --> 00:17:13.200
<v Speaker 2>the company file server, for example.

382
00:17:13.319 --> 00:17:16.440
<v Speaker 1>Oh wow, so I can control exactly what resources each

383
00:17:16.880 --> 00:17:20.240
<v Speaker 1>VPN user can access. Y that's a game changer for security.

384
00:17:20.799 --> 00:17:23.359
<v Speaker 1>But I have to ask, with all these powerful features,

385
00:17:23.440 --> 00:17:26.039
<v Speaker 1>isn't pfsense super complicated to manage?

386
00:17:26.319 --> 00:17:29.119
<v Speaker 2>Actually, that's one of the most surprising things about PFENS.

387
00:17:29.480 --> 00:17:33.079
<v Speaker 2>It's surprisingly user friendly. The web interface is designed to

388
00:17:33.119 --> 00:17:36.920
<v Speaker 2>be intuitive even for people who aren't network experts.

389
00:17:37.359 --> 00:17:39.160
<v Speaker 1>That's what I've been noticing. I feel like I'm learning

390
00:17:39.200 --> 00:17:42.000
<v Speaker 1>a ton, but it's not overwhelming. And I know we've

391
00:17:42.039 --> 00:17:45.039
<v Speaker 1>talked about the community support, but I have to say

392
00:17:45.039 --> 00:17:47.559
<v Speaker 1>it's pretty incredible how much information is out there.

393
00:17:47.680 --> 00:17:50.759
<v Speaker 2>Yeah, the pfsense community is a huge part of its success.

394
00:17:51.240 --> 00:17:55.960
<v Speaker 2>It's filled with passionate users, experienced developers, and helpful enthusiasts

395
00:17:55.960 --> 00:17:57.640
<v Speaker 2>who are always willing to lend a hand.

396
00:17:57.799 --> 00:18:01.279
<v Speaker 1>And because pfsense is open source, the code is publicly

397
00:18:01.319 --> 00:18:04.799
<v Speaker 1>available for anyone to examine. That means experts from all

398
00:18:04.799 --> 00:18:08.039
<v Speaker 1>of the world can scrutinize it for security vulnerabilities and

399
00:18:08.079 --> 00:18:09.599
<v Speaker 1>contribute to making it even better.

400
00:18:09.720 --> 00:18:12.839
<v Speaker 2>Exactly, it's a true testament to the power of open source,

401
00:18:13.519 --> 00:18:17.240
<v Speaker 2>and that open source nature also makes po sense incredibly flexible.

402
00:18:17.519 --> 00:18:19.599
<v Speaker 2>Remember those packages we talked about, Oh.

403
00:18:19.599 --> 00:18:21.640
<v Speaker 1>Yeah, the package manager. It's like an app store for my.

404
00:18:21.559 --> 00:18:24.640
<v Speaker 2>Firewall, right, Yeah, exactly. You can add all sorts of

405
00:18:24.640 --> 00:18:28.200
<v Speaker 2>extra functionality to pief scents by installing packages. Want to

406
00:18:28.240 --> 00:18:30.799
<v Speaker 2>set up a VPN client, there's a package for that.

407
00:18:30.960 --> 00:18:34.920
<v Speaker 2>Need intrusion detection, there's a package for that too, content filtering,

408
00:18:34.960 --> 00:18:38.039
<v Speaker 2>network monitoring, you name it, there's probably a package that

409
00:18:38.119 --> 00:18:38.720
<v Speaker 2>does it.

410
00:18:38.720 --> 00:18:41.240
<v Speaker 1>It's like payoff, sense is a blank canvas, and I

411
00:18:41.319 --> 00:18:44.839
<v Speaker 1>get to choose the tools to create the perfect network

412
00:18:44.880 --> 00:18:48.039
<v Speaker 1>for my needs. But what if I run into trouble?

413
00:18:48.440 --> 00:18:49.599
<v Speaker 1>Where do I go for help? Well?

414
00:18:49.599 --> 00:18:53.839
<v Speaker 2>The Pioffson's documentation is surprisingly good. It's clear, well organized,

415
00:18:54.039 --> 00:18:56.799
<v Speaker 2>and covers just about everything you could imagine. Okay, and

416
00:18:56.880 --> 00:19:00.480
<v Speaker 2>if you get stuck, the community forums are an amazing resource.

417
00:19:00.519 --> 00:19:02.400
<v Speaker 1>So even if I hit a snag, I'm not alone.

418
00:19:02.519 --> 00:19:05.680
<v Speaker 1>I can tap into the collective wisdom of the pfsens community.

419
00:19:05.240 --> 00:19:08.119
<v Speaker 2>Exactly, And don't underestimate the power of a simple Google search.

420
00:19:08.519 --> 00:19:11.079
<v Speaker 2>Chances are someone else has encountered the same issue and

421
00:19:11.119 --> 00:19:15.319
<v Speaker 2>shared a solution online. But even with all this help available,

422
00:19:15.480 --> 00:19:18.480
<v Speaker 2>things can still go wrong sometimes, all right, what if

423
00:19:18.480 --> 00:19:21.319
<v Speaker 2>I accidentally mess up a setting or create a firewall

424
00:19:21.440 --> 00:19:22.599
<v Speaker 2>rule that locks me out.

425
00:19:22.839 --> 00:19:25.279
<v Speaker 1>That's a great question, and it's something anyone new to

426
00:19:25.319 --> 00:19:28.880
<v Speaker 1>pf sense should be aware of. The Good news is

427
00:19:28.880 --> 00:19:32.359
<v Speaker 1>that pfsense has some built in safeguards to prevent you

428
00:19:32.440 --> 00:19:34.440
<v Speaker 1>from completely bricking your setup.

429
00:19:34.720 --> 00:19:38.400
<v Speaker 2>Right, okay, Good for starters. There's that default admin account

430
00:19:38.440 --> 00:19:41.319
<v Speaker 2>we talked about earlier. Even if you create other accounts

431
00:19:41.359 --> 00:19:44.440
<v Speaker 2>and disable the default one, you can usually get back

432
00:19:44.480 --> 00:19:47.039
<v Speaker 2>in using that default account if something goes wrong, So

433
00:19:47.079 --> 00:19:47.440
<v Speaker 2>it's like.

434
00:19:47.359 --> 00:19:49.640
<v Speaker 1>A master key that can unlock the system if I

435
00:19:49.680 --> 00:19:50.720
<v Speaker 1>lose my regular keys.

436
00:19:50.759 --> 00:19:54.240
<v Speaker 2>Precisely, and if you're really stuck, there's a factory reset

437
00:19:54.279 --> 00:19:57.119
<v Speaker 2>option that will wipe everything back to the original settings.

438
00:19:57.200 --> 00:20:00.279
<v Speaker 2>It's like hitting the undue button for your entire pf

439
00:20:00.359 --> 00:20:01.200
<v Speaker 2>sense configuration.

440
00:20:01.319 --> 00:20:03.480
<v Speaker 1>Of course, that means you'll lose all your custom settings,

441
00:20:03.519 --> 00:20:04.880
<v Speaker 1>so it's a last resort.

442
00:20:04.599 --> 00:20:07.319
<v Speaker 2>Absolutely, but it's good to know that option is there

443
00:20:07.480 --> 00:20:10.079
<v Speaker 2>if you ever need it. Now, before we wrap up

444
00:20:10.119 --> 00:20:12.640
<v Speaker 2>this deep dive into pfsense, I want to circle back

445
00:20:12.680 --> 00:20:15.319
<v Speaker 2>to something you mentioned earlier, the power and control that

446
00:20:15.359 --> 00:20:18.279
<v Speaker 2>piffsence gives you. It's important to remember that with great

447
00:20:18.440 --> 00:20:20.720
<v Speaker 2>power comes great responsibility.

448
00:20:20.920 --> 00:20:22.839
<v Speaker 1>Oh yeah, you're absolutely right. Just because I could block

449
00:20:22.920 --> 00:20:26.720
<v Speaker 1>certain types of traffic or create complex firewall rules doesn't

450
00:20:26.720 --> 00:20:29.799
<v Speaker 1>mean I should. It's all about finding the right balance

451
00:20:29.880 --> 00:20:35.039
<v Speaker 1>between security, usability, and while not driving yourself crazy with

452
00:20:35.119 --> 00:20:36.640
<v Speaker 1>overly complicated setups.

453
00:20:36.799 --> 00:20:40.519
<v Speaker 2>Exactly. The goal is to create a network that's secure, reliable,

454
00:20:40.559 --> 00:20:43.480
<v Speaker 2>and easy to manage, not to become a digital dictator

455
00:20:43.680 --> 00:20:46.799
<v Speaker 2>who rules over a locked down, inaccessible fortress.

456
00:20:47.119 --> 00:20:49.839
<v Speaker 1>Well said, It's all about finding the sweet spot where

457
00:20:49.880 --> 00:20:53.200
<v Speaker 1>you feel confident in your network security without sacrificing the

458
00:20:53.240 --> 00:20:54.720
<v Speaker 1>convenience and accessibility.

459
00:20:54.720 --> 00:20:56.680
<v Speaker 2>To make the Internet so great you cann't upset it

460
00:20:56.680 --> 00:20:59.880
<v Speaker 2>better myself. So, as we bring this pess sense exploration

461
00:21:00.039 --> 00:21:02.440
<v Speaker 2>to a close, what's your biggest takeaway? What's the one

462
00:21:02.480 --> 00:21:05.079
<v Speaker 2>thing you'll remember about this incredible software.

463
00:21:05.319 --> 00:21:08.319
<v Speaker 1>For me, it's the sheer, versatility and power that TFNS

464
00:21:08.359 --> 00:21:11.240
<v Speaker 1>puts in the hands of everyday users. It's like having

465
00:21:11.279 --> 00:21:13.720
<v Speaker 1>a team of network engineers at your beck and call,

466
00:21:13.799 --> 00:21:14.559
<v Speaker 1>all for free.

467
00:21:14.640 --> 00:21:15.279
<v Speaker 2>I know right.

468
00:21:15.319 --> 00:21:17.440
<v Speaker 1>It's truly a game changer for anyone who wants to

469
00:21:17.440 --> 00:21:20.880
<v Speaker 1>take control of their network security and explore the amazing

470
00:21:20.920 --> 00:21:24.240
<v Speaker 1>possibilities of advanced networking without breaking the bank.

471
00:21:24.400 --> 00:21:27.880
<v Speaker 2>I completely agree. It's amazing to see how PFNS has

472
00:21:27.920 --> 00:21:32.720
<v Speaker 2>democratized network security, making enterprise grade features accessible to everyone.

473
00:21:33.279 --> 00:21:35.960
<v Speaker 2>So to our listener, I encourage you to dive in

474
00:21:36.079 --> 00:21:40.480
<v Speaker 2>and discover the power of PFNS for yourself. Explore its features,

475
00:21:40.640 --> 00:21:43.599
<v Speaker 2>experiment with its capabilities, and don't be afraid to reach

476
00:21:43.640 --> 00:21:46.000
<v Speaker 2>out to that incredible community for help. You might be

477
00:21:46.039 --> 00:21:47.400
<v Speaker 2>surprised at what you can achieve.

478
00:21:47.799 --> 00:21:51.119
<v Speaker 1>Absolutely embrace the power of psns, take control of your

479
00:21:51.119 --> 00:21:53.960
<v Speaker 1>network and until next time, keep diving deep.