Sorry to revive an old thread. I have been looking at the code for Endian 3.3.2 and have been modifying for dynamic zones. I am tired of the limits created by R,G,B,O zones. I hope to completely eradicate the fixed zones and move to dynamic zones and expand DHCP to cover each zone. nothing published yet, but I plan to setup a github spot for the build. I see a lot of strange python redirecting to perl/cgi in this version so I assume Endian plans to move to a python based platform at some point. I will keep the original perl/CGI and get rid of the python since it is barely implemented. I am curious if anyone has done this before i recreate the wheel? I see netdeep has created some type of ipcop/smoothwall for (possibly Endian) but it is still locked into the 4 zones.

Thanks,
Bryan

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

Anyone knows when Intel i225 support will be integrated in Endian Community edition?

Does Endian Community support the Intel 211 driver?

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.)

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/

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.

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

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 experience. Sorry for my translated English.

same issue, same resolution. Thank you.

Andrea.