Thanks for your help. I will investigate further on those grounds. I'll keep you filed. Thierry

Hi, i tried 16) Restart PHP-FPM and now is working. Thanks.

Did you get the batch file created successfully?

For what possible reason? So your on the LAN but your hitting your public IP to access the web gui?  Makes zero sense to me..

I asked on IRC and got an answer pretty quickly, and it worked! <piba-nl>vrelk, hardware offloading , turn it off <vectr0n>system -> advanced -> networking, if unsure of where it is :)</vectr0n></piba-nl>

Sigh. Hopeless. Bye.

Ok - its still borked.. Maybe someone else be willing to help.. Contact pfsense direct for support would be my suggestion if you have paying customers with Gig Mpls connections you should be able to pay for some official support ;) That is not how it should ever be setup.. I don't help people configure borked configurations ;)  Just makes it look I would condone such a configuration, which I would never do.. There is a reason they are not enabled out of the box… https://www.pfsense.org/get-support/ If you do not want to use cycles on the pfsense to route the traffic as it should, then put in a host route so you host knows to talk to .3 out of the gate vs having to wait for a redirect to tell him he is going to the wrong place for that destination.

I was actually thinking that it might have to do with my ISP/line. I just switched from 50/5 to 150/10, have never had problems before. This happened two nights in a row at about the same time in the evening for the same period of time. So I'm thinking it might be something like you described. Do you or anyone else have any idea how I could trace the problem without asking everyone on my street about their internet usage routines?

Nice to see freebsd having 3.17 of iperf, but there was not real change from 3.1.6 - .7 was just some typo/doc changes nothing operational. If you want the current windows version I compile a new version when it comes out and make it open to the public internet.

I can get to the pfsense gui from the clients.  I can get to a webserver on the 192.168.20.n subnet from the devices on the 192.168.20.n subnet. All interfaces on the pfSense are up, with no errors. The only errors I see in the logs are: System, General (right after a reboot): Mar 27 15:35:41 dhcpleases: kqueue error: unkown Mar 27 15:35:40 dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process. Mar 27 15:35:40 dhcpleases: /var/etc/hosts changed size from original! Mar 27 15:35:38 dhcpleases: /var/etc/hosts changed size from original! While maybe not an error, I do see these in the DHCP logs: Mar 28 05:23:28 dhcpd: uid lease 192.168.20.243 for client b8:27:eb:1c:bc:3e is duplicate on 192.168.20.0/24 Last gateway log entry: Mar 27 12:44:38 dpinger: send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 71.123.236.1 bind_addr 71.123.236.4 identifier "WANGW " The firewall log does show this periodically, which I think may be odd: x Mar 28 05:31:10 WIRELESS 0.0.0.0 224.0.0.1 IGMP

I have turned off the "forwarder," in "services -> DNS resolver," and that seems to have completely stabilized my firewall. No more notifications, no more errors, no more crashes (so far).

I recently bulk added 256 VLANs / Interfaces to an existing pfSense box with some python script and had this exact same issue, web panel slows to a crawl on certain pages and delivers 504 on interface_assign.php Figured it was my own dumb fault and tbh it's taken me far longer than it should have to find this thread and that bug report!  ::) Thanks for posting, saved me half a day of bother. :)

That is exactly what I am afraid of.  Maybe I will see if I can lock the router in a cabinet.  Not perfect, but probably better than nothing.