Hi johnpoz, I will verify my connection and try to connect my two subnets to my primary pfsense. Thank you and regards for your answers.

@provels I havent managed to get it connected to the internet just yet, but a new network switch I picked up yesterday should be coming in tommorow. I'll hook it up and try it. Otherwise I did try manually downloading and installing the 2012 drivers; but as I made note of above it only displays the cards model, no luck getting it to work. Will try using online windows update though. I'll report back tomorrow. @Mats I got win server 2019 running normally now; headless. I control it with RDP over LAN.

XG-7100-1U ... envy that grows and don't forget Firewall / NAT / Outbound to set the correct ip to go out for every VLAN

Thanx a lot :)

I still don't have the HP yet but on the current Supermicro board and the two onboard intel NIC, it would drop ping every 20-30 seconds. I'm using the latest build and only the two onboard NIC. However, when it did work, my speed test yield much better performance than the Asus router that I'm using now. on my 200mbps connection I've only yield 160 ish down but when using PFSense I'm getting closer to the advertised speeds so it's definiteyl a good start.

i replaced my sg2220 with a mbt 4200. every pfsense update i boot up the sg2200 and update and then put it back just in case...

Mmm, that implies something was opening things using upnp that somehow broke opening new states perhaps. Hard to see how it could do that though. Was it open to requests from WAN maybe? Something local to the device triggering it would explain why the same setup appears fine on other hardware in other location. Steve

I advise you to make the captive portal work without this "firewall2". Add "firewall2" only when everything works perfectly.

I have found solution The issue was in /usr/local/etc/pkg/repos/FreeBSD.conf where I previously added FreeBSD: { enabled: yes } After disabling it starts working fine

It's not a package we make available. I don't know that anyone is working on it, either. With VPNs being easy and ubiquitous, there is little need for anything as crude as port knocking these days.

@JKnott changing the pfsense box to 192.168.2.1 fixed this. Thank you everyone!

This : [image: 1563168479953-29b49aa8-8aa8-4369-9401-8e7febf29ed2-image.png] means : a 5 Mbits limit is maintained for the entire /24 network, like these devices 192.168.1.1 to 192.168.1.254. If you select a /32 (as equivalent to /128 for IPv6 - but you are probably not using IPv6) then the limit is set per device.

It's better now than it was earlier today, but could be better still.

@SparkyRih said in Unable to find *.so libraries after power loss?: I would expect software like this to handle a power failre, not? This sofware is actually an OS, using a writable disk storage. Try ripping out the power of any OS (one from Microsoft, Apple, any Linux based one) and you have big chances it will complain when you reboot. If pfSense was ROMable with some RAM as a scratch pad, like your ISP router/modem device, than it would handle better power outages.

Yeah that looks like dhcpd is enabled. If you had picked /32 you wouldn't of been able to enable dhcpd. If your device can not get an IP, then its never getting to the internet.. Do you see dhcp requests from it in the dhcp log? If not then no dhcpd would never hand give it an IP. You sure your connected to the correct interface - and the cable and this device are good?

Something like the Limiters defined here: https://forum.netgate.com/post/807490 There are a number of posts in that thread detailing similar arrangements. Steve

@Vincent_28 said in How to block torrents: use wireshark. to see the port of torrents and syn. seeds of bitorrent That is a wack a mole game that will keep you busy to the end of time.. And as already stated - it can be ran over ports that you require to be open. 80/443.. The most effective method is application detection via your IPS - which again as the tech evolves signatures can change depending on the p2p product being used.. Which your IPS might not detect, analysis of traffic flow patterns can help in detection as well, etc.. But blocking of ports is not going to stop someone that knows what they are doing and how the protocol can be used. Good way to stop it is only allow your proxy outbound.. where clients have NO direct outbound connection capability... And block lists on your proxy to prevent connection to p2p networks even over the proxy, etc. Trying to control user access once you have given them even 1 port outbound is going to be a never ending battle ;)