I can't believe we're here.
We've reached the end of this module and course,
and I hope you really enjoyed yourself and learned a ton of new skills.
Before we go, though, let's do a quick review over everything that we've learned.
First,
we learned how a simple misconfiguration syntax can create massive issues for
either allowing unwanted traffic or blocking required traffic.
We then learned how important the placement of firewall
directions are within your rule sets.
Without proper direction,
you could inadvertently create an inefficient firewall rule,
which blocks traffic much later than required, causing unneeded CPU
overhead. With enough direction provided to satisfy a GPS, we then pivoted
to zones. During our troubleshooting of zones, we learned and saw firsthand
what happens when zones lack parity between each other. Within TCP, we then
learned firsthand how incorrect rule order affects a firewall and can cause
legitimate traffic to be blocked or accidentally allow bad traffic into your
network.
With our firewall issues thoroughly covered for TCP,
we then pivoted to TCP DNAT.
During our discovery of DNAT,
we learned and saw firsthand how imperative it is to not have
multiple services utilize the same DNAT port.
That is, unless you want broken services. Then you're good to go.
Finally, for the last section of TCP,
we learned how MTU and MSS could cause major issues,
especially when dealing with a WISP network or a
VPN, in the worst‑case scenario, a VPN connection running over a WISP network.
Lastly,
we pivoted to UDP and learned how misconfigured firewall rules
severely impact both DHCP and DMS, due to an engineer's lack of
understanding of proper protocol operation.
Finally,
we learned how restarting a UDP service may clear up odd transient
issues, when we're positive it's not a firewall issue. Well,
everyone, it's come to that time once again. I want to wish everyone
well, and hope that they have thoroughly enjoyed this class as much as I have had teaching it