With FreeNAS SYS interface up my client got replies, when SYS interface was down I got no replies. Neither with nor without FreeNAS SYS interface up the packets reached FreeNAS INT interface but pfSense packet capture never reported any replies. My packets where sent out correctly through the firewall and into the INT LAN, that's what pfSense packet capture reported. If this routing mechanism had stopped this unorthodox method when the interface was down and instead used the "normal" route I wouldn't have had this mess. I consider ping being a very useful tool to make sure you have contact with a network interface and when ping doesn't reply there's something wrong, I started to reconfigure my firewall to find and correct the error. >įreeBSD is of course an operating system with loads of configuration settings but I expected that if you bundle it with a product the settings would be appropriate for the product. PSU: Fractal ION 2+ 650WLike my post (or find it helpful)?. VM/Docker host, using ESXi and running pfSense alongside FreeNAS (separate Dual Intel NIC added, dedicated to the pfSense VM)Ģx Intel NUCs running TrueNAS SCALE 23.10.1ĬASE: Fractal Define 7 running TrueNAS SCALE 23.10.1ĬPU: Intel(R) Xeon(R) CPU E3-1240L v5 2.10GHz NIC: Intel EXPI9402PTBLK Pro, Dual-Gigabit Adapter (plus the 2 onboard Intel NICs, 1x 210, 1x 218) Corsair Commander Pro to control the fans (see script and code)ĬPU FAN: 1xCorsair H60 CPU Radiator - Front OS: 1 x Kingston UV400 120GB SSD - boot driveįANS: 3xFractal R3 120mm - 3 Front, 1 Rear. SSD: 4 x Samsung 850 EVO Basic (500GB, 2.5") - VMs/Jails
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |