Version 12 logs five times the number of events per second on the same hardware and features Google Drive integration for offsite data storage for daily logs as well as configuration backup. Version 12 adds a Device List which tracks devices on the network by MAC address and gathers pertinent data about them, enabling administrators to create rules and alerts to manage them. Let’s take a look at Untangle 12 installation and configuration.Ī few of the more notable features of the new release of Untangle are the following: The product has definitely come a long way since then and has matured in form and function especially with the recent release of version 12. I have been an Untangle fan for several years and have used it since around version 7. Leave logging on, leave logging off…totally up to you.Īgain, this Pihole setup is working well for me right now…but it depends on what all you’re trying to accomplish.I am constantly on a quest to keep finding the better or best firewall/UTM appliance for home/lab purposes as well as for small business use cases where installing a virtual appliance or other whitebox appliance makes sense. After a lot of searching on these forums I discovered that internal to internal traffic like this is considered bypassed, so you have to explicitly log it to ensure it’s working. Now, IF you want to see these redirects in the Reports->Network->Port Forwarded Sessions…you’ll need to turn on “Log Bypassed Sessions” in the Advanced tab. Next step, at least for me, was to see if I could send those hard-coded requests to Pihole anyway.ĭestination Address is 8.8.8.8,8.8.4.4,208.67.220.220 (Note: these are the only hard-coded DNS IPs I currently have an issue with) Maybe you care, maybe you don’t…but for me that crap is filling my Firewall block report and I don’t want to look at it anymore.
So next logical step is to setup a firewall rule to not allow that:ĭone….well, hang on….now the Roku and other devices are freaking out and trying to ping 8.8.8.8 many many times throughout the day. For example, Roku and most FireTV devices are hard coded to use 8.8.8.8 and they do not respect your above configuration.
Now the fun part…just because you say to use it, doesn’t mean everything will. Important to note for the following - I do not use Google DNS: As TirsoJRP and sky-knight indicated, you have the easy part done: Config->Network->Internal DHCP DNS override set to the internal Pihole IP. Setting up Pihole is fairly easy, but there are nuances depending on what exactly you want to do.
0 kommentar(er)
