@WAR10CK said in Intel gigabit ct Desktop not detected: AHCI enclosure management bridge OK, pfsense recognizes the netcard, but why is it saying : AHCI enclosure management bridge under interface em0. There is no link when I plugin the cable to em0. The cable works fine in em1.

There are no FreeBSD drivers for the RTL8125 so you will not be able to use those NICs. The 2.5GbE options currently are to use a Broadcom NIC with modified firmware or wait for the Intel i225 as far as I know. Steve

I have to disagree on one thing only.. "planned obsolesce" is a fact not a myth, not everyone applies this policy of course but there are alot of example out there proving this the more evident one is for example to limit the life of a light bulb Apple's use of pentalobe screws in their newer devices is an attempt to prevent the consumer from repairing the device themselves Non-user-replaceable batteries Smart chips in ink cartridges to prevent them from being used after a certain threshold constitutes "planned obsolescence" when you design a board and you put capacitors in a place where the temperature is hot you know that the capacitor itself would last no more than 3 years. there are alot of triks to make everything with "planned obsolesce" in mind last example ... server grade vs consumer grade

There are ways to do this by sending logs to a remote syslog server and using third-party tools to scan the firewall log entries. However, be forewarned this will get very old to you very fast (getting alerts/emails for every unwanted firewall access attempt). A normal firewall will see dozens to maybe a few hundred connection attempts per day on the WAN side. Even if you limit the alerts to just a handful of ports, you will soon grow very tired of your email app "dinging" with new mail messages ... . I say this in a nice way, "you must be new to firewall administration"... . This is usually the first thing a newly minted firewall administrator thinks he wants until he has it, then he quickly turns it off.

@johnpoz I use IPSec to create a site-to-site tunnel should the wireless bridge go down. (Hilariously, this is no longer working, but that is a different problem for a different day). I wanted to use the pfSense for the VPN clients but had too much problems setting it up with the win 10 clients. I only have two VPN clients so it is not really a problem at the moment. But I will probably sit and redesign the whole network. Or I should just get some hardware routers. The win 10 hosts are giving me hell as well.

Does anyone have a way to resole it? Please help.

I imagine you will fine routing at the firewall between the internal subnets. That hardware is probably far in excess of what you need. Steve