After recently doing a video on PF blocker and G, I realized a lot of people are a little confused and I'm making this video clear this up because they're always asking PYHOL or PF blocker and G. You just have some posts on Reddit. Another post on Reddit can PF blocker replace with a PYHOL or PF blocker and G versus PYHOL or all the people commenting on my YouTube. Same question. Alright, let's define the two projects very quickly. PYHOL network wide add blocking a black hole for the internet advertisement. So PF blocker and PYHOL do a similar service. They work as well. PYHOL specifically works as an external DNS server. So you have your router, which frequently in most home networks would be serving up the DNS or you use an external DNS server as for name resolution for websites. What the PYHOL system does is DNS blacklisting or sync holding of a site. So it creates a black hole hence the reason kind of like a black hole can thing behind here and calling it PYHOL. And you're basically going through and saying, these are sites I don't want to resolve in my browser because they track me or I just don't want to see them. Therefore they go away. This requires that when you set this up, when you configure this that you use PYHOL as your DNS server. And so here this is an example and some type of router, probably a consumer router reminds me of the old link system one. I think that's what screen shot is from. You go to your DCP servers, you build your separate device, the PYHOL and it will run on a Raspberry Pi hence it's namesake and you plug in the DNS settings for it as this to be your server. Cool, awesome. It's a nice little system. I like it. It's cool, but it's not necessary with PF blocker. Here's the PF locker project. Now there's different prerequisites for PF locker. First one is you got to have a PF sense box. PF locker is an add on for PF sense. It's a package that you load. The feed system and everything is the same as it is for PYHOL. It's using a different list that you have on the internet and you can say, hey, I want these things to be black hold sink hold and like in the screen shot they have here settings. That one data that's the Microsoft telemetry server. Maybe you want a black hole of that. Well, you do that with PF locker. Now PF locker is not itself a DNS server, but PF sense has a DNS server built into it. This is an add on it works within the DNS server of PF sense. In that respect, they're the same. There's not a need to run both. For me, and my opinion on this is that it's more convenient if I'm already running PF sense to run PF blocker and problem solved. It's doing the same things. I can go here. I can update the list. I can add feeds and sink hold different things. But PF locker also has an advantage of not just being a separate device that you have to manage or change DNS servers because you still leave PF sense as your DNS server. This is just an add on to sink hold those. This also does IP blocking and creating firewall rules. This is where PF locker goes beyond. You have the same functionality of DNS and the extended functionality of working with the firewall to do blocking of sites and feeds. You can go here and we'll use, for example, G O A P blocking and you can say block these domains. Now this is doing it at the firewall level, not the DNS level. The IP address is themselves become unreachable, whether they're inbound or outbound because it supports both. This is like I said, working in conjunction with the firewall. This is not a firewall on top of a firewall. This is just rules that's being built inside the firewall itself. Therefore you're going to see rules such as these. It's a PF B for PF blocker top four and some of the G O A P blocking. Now we've created firewall rules in addition. To me, like I said, PF locker is something more advanced than PIE hole. It is a system that's doing both DNS and IP filtering and creating firewall rules dynamically based on the list that get load and showing you what the states and things that are blocked are. It's a much more advanced system compared to the simplicity of PIE hole. For some people, if they're just running a basic and like the screenshot was here, you're going through and you have a link sister out of you don't plan it up creating any of your really basic routing. You're not going to go to PF sense. Then PIE hole makes perfect sense to use it as your DNS server internally so you can sync all things. But if you want to go with something like PF sense, which I'm obviously a fan of that firewall and you use this as an add-on, now you've gone a step further and also you don't have to have two separate devices. All of it can be done in one device and in the video demo, I did recently of the latest version of PF blocker. I'll leave a link to that down below. It is fully supported and runs quite well here in 2019 on an SG 1100, which is one of the relatively inexpensive PF sense and that gate appliances. It kind of makes one nice small turnkey solution for a lot of home users to be able to have all these advanced features all in one box and not have to deal with the poor quality is what I can do with some of the consumer firewalls, especially if you're still running one of those really old links as firewalls. It's not really if this that or I can't really come up with a use case to run both unless you like the reporting in PIE hole better because you like the way the graphs look in it. I haven't looked at the PIE hole project in a while since I did a video on it almost I think two years ago. I think it's a great project, but it's redundant to run PF blocker and PIE hole at the same time. It's just kind of a futile effort at that point. There's not really any advantage unless you're trying to run different lists and you want to see if one misses, but the reality is you've done the same list. They're not going to do anything different because they're the same feed list. These are only as good as the feed list that you put in there and all of the tuning or all the headache of either black listing certain sites or having to go back and wait list certain sites because you broke some functionality that you need of sites you can't get to. All of that is going to occur on either one of them because that's more based on the list than the device for methodology used to do it. Hopefully this clears that up real quick about the difference between them that there's really not a lot other than PF blocker does more. They both do the same ad blocking. They both do it based on lists and they both are going to have the same challenges if you make those lists too restrictive of having to remove things and put them back on wait list to gain functionality. Hopefully that cleared things up and hopefully people find this and it's a shorter question before they go through and start down a whole path and buy a whole separate system and build a separate pie hole to find out that it was just a quick plug-in and PF sense that they're already using. All right, thanks. And thank you for making it to the end of the video. If you liked this video, please give it a thumbs up. If you'd like to see more content from the channel, hit the subscribe button and hit the bell icon if you'd like you to notify you when new videos come out. If you'd like to hire us, head over to launchsystems.com. Fill out our contact page and let us know what we can help you with and what projects you would like us to work together on. If you want to carry on the discussion, head over to forums.lorencsystems.com where we can carry on the discussion about this video, other videos or other tech topics in general, even suggestions for new videos they're accepted right there on our forums, which are free. Also, if you'd like to help the channel on other ways, head over to our affiliate page. We have a lot of great tech offers for you and once again, thanks for watching and see you next time.