It can wait there for a long time trying to start the Resolver if there's no upstream connectivity but it should eventually pass that even with the WAN disconnected. Steve

@perfectbake420 Firewall rules apply to the interface they enter, not exit. Also, existing states are not affected by a rule change. You need to clear the states of the specific clients/devices your new rule applies to before they will obey the new rule.

@ogghi I think I'll try and debug on the windows server/NPS side. The packets arrive at the windows server as seen on Wireshark. But nothing is ever logged on NPS. So it might be some really stupid bug here..

@rameshk said in Ugraded from 2.5.1 to 2.5.2 and a few services stopped working: DynamicDNS - Didn't update the WAN IP and every time I force update it returns an error "mismatch credential" About this issue, here there is a possible solution/workaround.

I have encountered the same pppoe error in 2.5.2, without using a local subnet similar with the gateway address. What now? IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists

@stephenw10 said in NG 3100 forgot which port used: That will return the ports nginx is listening on. @stephenw10 thank you, fixed it!

@julio12345 I was also going from 2.5.1 sorry didn't make that clear that's why the top warning was so confusing for me. Plus those lib errors and in 2019 directory and I do remember having problems when there was a big PHP upgrade in the past so maybe they are not relevant?

@lucasg said in What the "Timeservers" field (in the general setup) does?: I have two XG-1541. In System > General Setup, I have added my internal NTP server's IP in the "Timeservers" field. What are your internal servers using for a source? I have pfsense configured to use 3 stratum 1 servers and 1 stratum 2.

well it died again this morning. I connected to the pfSense console and was able to ping out to 1.1.1.1 but couldn't connect to anything on my home network. A reboot fixed it. What can I look for to find why this is happening? btw: I upgraded to 2.5.2 a few days ago but can't change the title of the original post

@jimp All the detail is in the Config History section. Feature request submitted: https://redmine.pfsense.org/issues/12118

I made the changes again since the previous config save. Then downloaded the xml for safe keeping. Attempted to put the device in production but it wasn't working. So I took it back down and tried to see what's up. Now it's bootlooping, orange LEDs flashing every minute, never comes up. This is a brand new device and even if it could be wiped, reloaded, I'm not gonna put such an unreliable device in production. RMA requested.

@p32spaceblaster so I just noticed this has stopped again. It may have to do with performing updates on my Ubuntu log server and when I do a reboot but I've done this the same way for some time and had never noticed it. I feel like this is something new. I'm going to monitor further and see if I can replicate it. I think pfsense fails to ship logs sometimes after I reboot my log server.

@JKnott @NogBadTheBad Thanks for your help. Indeed, the hardware was limiting our bandwith. Exact same configuration with the Netgate 7100 and we reach the 500/500 easily.

@terrencettibbs said in Calling all "MR BEARDY'S" Help needed for config migration from 4 PORT 1GIG NIC to 2 SFP+ NIC: As there is an apparent insufficient supply of MR BEARDY'S left in the world to answer my post, I thought I would give it a go and I must say I am rather impressed with myself. FKN GOLD

@kom ok, I understand you ... I'm using DNS Resolver, I already had my website added to the Host Override list ... I don't know if my problem is the consequence of some protocol conflict between my proxy and Cloudflare, because it was just after having added SSL certificates for using HTTPS on my website, which presented me with the problem ... I used HTTP before.