bolo, please let me now which script did you add. Thanks in advance.

NAT type 2? or are you double NATtd?

@Mr_AJ I haven't given the matter thought since. Turning off the TLS check solved the problem. The risk of a bad actor causing an attack, presumably through man in the middle, doesn't concern me. If there's a reason I should be concerned, I'd appreciate learning of it.

Good info, I'll have to try this tonight.

I'm having this same issue with the Intel PRO/1000 MT Desktop Adapter .. never had an issue with these nics in our DC's before ... I've also tried different PCI ports to no avail UPDATE: it seemed as if my NIC card was completely dead. nothing to do with pfsense

Tested the issue further, added another ethernet card and guess what worked flawless with dhcp getting picked up, tried it many times and it and I don't need to add any Reject leases from 192.168.100.1 entry. Maybe pfsense just hates my onboard ethernet ports, either way issue sorted.

@shooters running into the same problem. Were you able to hunt down a solution?

@stephenw10 thank for your reply

All, Thank you for your responses. After trying various things you suggested i figured something wasn't right - i removed all my rules to default and FTP connection worked right away. I do not know why FTP didn't work yet other things from LAN->WAN did but i guess i will learn these next few months. Appreciate the support - thank you Jon

Do you have any IPv6 connectivity? Some partial v6 connection can cause massive issues as things have to timeout v6 if it's broken before falling back to v4.

Perfect, thanks for the info. I'll look around online for more details

Hmm, GRE tunnel to where? Between the amplifi nodes? To some cloud location? More info needed there. Not really sure how that might be used, though it probably could be.... Steve

@jimp Seems to be working - thanks so much! Will keep an eye on it, let you know if I come across any issues. Much appreciated!

@ibbetsion said in sshguard complaining about an attack from the pfSense system itself?: 192.168.1.2 is assigned IP of the pfSense firewall from my ISP router. It is the only device connected to the ISP router This is a WAN interface ... 192.168.7.1 is the IP of the pfSense firewall itself (WAN1) Another WAN interface ... 192.168.5.2 is the assigned IP of the second WAN port on the pfSense firewall (WAN2) And another WAN interface ... No LAN(s) ? Remove all rules on all WAN interfaces. The default action will be block all (DROP) - so sshguard won't be bothered again.

@Sasil-M said in how to avoid daisy-chain 5 unmanaged switches my setup is 285m.: My second option is to use High-Gain, Directional, 2x2 MIMO Antenna. You can get something like this, which is designed for the task. https://www.engeniustech.com/engenius-products/enturbo-outdoor-5-ghz-11ac-wave-2-ptp-wireless-bridge/

Thanks! I'll give that a shot!

Looks like a type of bug that was fixed in a more recent release anyhow. Upgrading to a current release is the most likely solution.