Thanks again. Needed to concretize / formalize my knowledge / understanding of firewalls & firewal rules, in order to realize a solution to bring our public IP address range traffic at datacentre onto targeted VLANs; as part of an initial datacentre migration for several hosts and workloads. Ended up getting exactly the understanding I required, having completely architected the "public IPs > firewall > VLAN > service_interface" solution about 10 minutes from the end of the second video of the pair. The comment about network address translation actually brought it all together. Also got a lot more than I bargained for, and now have a base methodology for configuring my firewall rules @ datacentre. So once again many thanks. 🤝
Thanks for the feedback I've built up a lot of knowledge about IT over the years and I'm still finding out new things So I'm happy to share that so it can help others
You are a thorough teacher and seem to present a lot of scenarios for different use cases sir. I'm honored to be able to listen to your knowledge. I'm currently trying to figure my way around pfsense and it's been really hard for me since I'm changing over from an ISP owned router. Thought it would be a walk in the park, but boy was I wrong. Thank you for your help and taking your time making this video sir.😁
Very comprehensive, excellent video. If there are more port, firewall, network security, or virtual networking videos I am looking forward to seeing them. Top notch content!
Thank you for creating this video. This is exactly what I needed today. What would the broadcast address need to be for IPv6 if i wanted to ignore those requests?
ipv6 doesn't have broadcasts as such You might see multicast traffic going to ff02::1 which is for all nodes instead though it's not encouraged to use it There might be other traffic though to ignore depending on the IP addressing I just allow what I need and block the rest If something like a broadcast shows up in the blocked logs, and I want to ignore it, I add it to an ignored rule That sits somewhere above the explicit deny rule, drops that type of traffic but it doesn't log it
It's just the wall behind my computers at home After a while the walls or even entire rooms end up with themes After buying a print of Audrey Hepburn, this side of the room became Hollywood actresses
I'm confused. The PFSense firewall isn't routing between the 192.168 and the 172.16 LANs, so how is it blocking/allowing access between them (the DNS rule)? Is the traffic going out across the WAN interface and then back in?
Good question The video is only meant to cover the basics of firewall rules It wasn't intended to cover the mechanics of how a firewall forwards traffic from one network to another So this firewall was only given some basic interface settings so I could provide practical advice on how to structure firewall rules
I have a Linux computer so I'm using drawio www.drawio.com/ You can run it on a Mac or in Windows though And you can even run it online using a web browser for free
This channel is extremely useful and clear. Thanks David!
Thanks for the feedback, it's always appreciated
And good to hear you're finding the videos useful
Both of these new videos are very helpful. Thank you.
Thanks for the feedback
And good to know the videos helped
Thanks again. Needed to concretize / formalize my knowledge / understanding of firewalls & firewal rules, in order to realize a solution to bring our public IP address range traffic at datacentre onto targeted VLANs; as part of an initial datacentre migration for several hosts and workloads.
Ended up getting exactly the understanding I required, having completely architected the "public IPs > firewall > VLAN > service_interface" solution about 10 minutes from the end of the second video of the pair. The comment about network address translation actually brought it all together.
Also got a lot more than I bargained for, and now have a base methodology for configuring my firewall rules @ datacentre.
So once again many thanks. 🤝
Thanks for the feedback
I've built up a lot of knowledge about IT over the years and I'm still finding out new things
So I'm happy to share that so it can help others
You are a thorough teacher and seem to present a lot of scenarios for different use cases sir. I'm honored to be able to listen to your knowledge. I'm currently trying to figure my way around pfsense and it's been really hard for me since I'm changing over from an ISP owned router. Thought it would be a walk in the park, but boy was I wrong. Thank you for your help and taking your time making this video sir.😁
Thanks for the feedback
Firewalls can be confusing when you first look to set them up
So good to know the video was helpful
Very comprehensive, excellent video. If there are more port, firewall, network security, or virtual networking videos I am looking forward to seeing them. Top notch content!
Thanks for the feedback, I appreciate it
I'll add these requests to my list
Superb video thanks David
Good to know the video was useful
networking+ pbq's killed me, thanks for these.
Thanks for the feedback and good to know this helped you with your studies
Thank you for creating this video. This is exactly what I needed today. What would the broadcast address need to be for IPv6 if i wanted to ignore those requests?
ipv6 doesn't have broadcasts as such
You might see multicast traffic going to ff02::1 which is for all nodes instead though it's not encouraged to use it
There might be other traffic though to ignore depending on the IP addressing
I just allow what I need and block the rest
If something like a broadcast shows up in the blocked logs, and I want to ignore it, I add it to an ignored rule
That sits somewhere above the explicit deny rule, drops that type of traffic but it doesn't log it
good info, weird chosen background for IT prep lol
It's just the wall behind my computers at home
After a while the walls or even entire rooms end up with themes
After buying a print of Audrey Hepburn, this side of the room became Hollywood actresses
I'm confused. The PFSense firewall isn't routing between the 192.168 and the 172.16 LANs, so how is it blocking/allowing access between them (the DNS rule)? Is the traffic going out across the WAN interface and then back in?
Good question
The video is only meant to cover the basics of firewall rules
It wasn't intended to cover the mechanics of how a firewall forwards traffic from one network to another
So this firewall was only given some basic interface settings so I could provide practical advice on how to structure firewall rules
@@TechTutorialsDavidMcKone understood. Thank you.
What diagram tool are you using? This is excellent content!
I have a Linux computer so I'm using drawio
www.drawio.com/
You can run it on a Mac or in Windows though
And you can even run it online using a web browser for free