2024, Endian Community 3.3.26 and the warnings still pop up ..read more

Anyone knows when Intel i225 support will be integrated in Endian Community edition ..read more

Does Endian Community support the Intel 211 driver ..read more

I have a DNS server running behind Endian and it works fine. But I can't see the client IPs of those who make requests to this DNS server; because Endian proxies DNS requests. That's why all I am seeing in my DNS server logs is that all the DNS requests are coming from 10.0.0.2 which is Endian's local IP. So how can I disable DNS proxying of Endian to let my DNS server see the real client IPs? I tried enabling transparency in Proxy -> DNS but it didn't work. (I have only GREEN interface enabled so I can enable transparency on GREEN zone only ..read more

SSH protocol flaw – Terrapin Attack CVE-2023-48795: All you need to know see jfrog.com//ssh-protocol-flaw-terrapin-attack-cve-2023-48795-all-you-need-to-know ..read more

Hello. how can you fix the bug. Ad line to $ nano /etc/snort/snort.conf.tmpl portvar FTP_PORTS 21 and $ jobcontrol restart snort --force I hope it helps ..read more

Hello, Is there misconfiguration on blackholedns.conf file on yesterdays update? There is address=/google.com/75.125.225.163 marked on that list. br, sakari ..read more

Good morning, I have several firewalls that restart themselves for no reason. Sometimes it happens when main uplink is faulty. Other times for no reason. Even with a new power supply. It happens with version 3.3.23 3.3.24 and 3.3.25. Even with a new power supply. This is the error: This notification was sent by the Endian UTM device named efw-xx on 2023-12-19T10:47:05+01:00. The email has been generated from the event described below: The system has started. This happens to me on 6 out of 30 devices. Is it due to malfunctioning uplinks? Thanks to those who will help me by sharing their ex ..read more

Good afternoon, I'm using the transparent proxy, everything works, blocking sites like YouTube, Facebook, the problem is that even putting the Mac or even the IP of the machine to which I want to allow access through the Bypass transparent proxy, it doesn't accept it, it continues to block and it's worse if I change the DNS to 8.8 .8.8 on the machine is released how do I get endian to just accept its proxy which in this case is 192.168.0.240 and how do I release access via Bypass proxy transparent on the transparent proxy I'm on the latest version 3.3.25 ..read more

Hi all community! I'm new on this forum so I'll try to explain my problem as clear as possible. I've setup my Endian as follows: RED network: 10.0.0.2/24 (behind a router, but the WAN IP of the firewall is on DMZ on router so all traffic will be forwarded) GREEN network: 192.168.1.0/24 I also have an instance of PiHole installed, which I use for DNS resolving and network ad blocker. It's IP is 192.168.1.80. Everything works perfectly while inside the GREEN network. I also enabled the IPS, and the HTTP proxy as well. Several clients connects and will navigate with proxy and Pihole as DNS. I ..read more