Yes it should not be enabled on the SG-3100 because, as it says, there is no driver cpufreq can use for the ARM processor there. It does not hurt trying to start it though beyond that error message. Steve

@provels my NIC came 4 days ago. Its an HP one. Guys, I think you were right. The intel nic is up and running without a glitch for 100 hours now! (I use net uptime monitor software) I downloaded a large file from nvidia and I had a long time to see a smooth graph like this (without disconnections). [image: 1591795510012-30263510-e667-47c7-a926-1e9d9aecf9c9-image.png] I think my problem was the network cards. Now I have only this HP NC365T Intel I340-T4 working with 3 ports NIC Teaming and one port for the "gateway" of pfsense. THANK YOU guys! I will never use a cheap nic again. Promise.

the interfaces are E1000e (aka intel board I think). without UEFI I don't leave. i have both an old pfsense intaller that is in BIOS with the E1000e and it works for me. and strangely I miss update does it. it gives me error in the search: Unable to check for updates

I have a generic J1900 Black box [image: 1591788871906-2fd5cae3-b2e1-49b0-9c38-44532fc5de32-image.png]

@90Ninety Super I told you " is UPNP still working? don't do that, instead use your own port forwarding, choose from a good high port range outside (F.E. 57443 to 443)" there are still issues with UPNP, although more significant with gameplay https://forum.netgate.com/topic/154153/test-request-upnp-fix-for-multiple-consoles-playing-the-same-game-static-port-outbound-nat

@Gertjan said in Question re slow DNS resolution/General DNS Resolver Options setup/Troubleshooting: @Gertjan said in Question re slow DNS resolution/General DNS Resolver Options setup/Troubleshooting: clog /var/log/resolver.log | grep 'Restart of Followup : Since the last Jun 9 09:29:03 pfsense unbound: [31040:0] notice: Restart of unbound 1.10.1. posted previously, I had no more unbound resstarts. That is : I update pfBlockerNG-devel feeds every 3 days, or less frequent (if they are themselves updated every week, I respect that time frame - no need to update all feeds every hour as seen elsewhere) as pfBlockerNG will restart unbound if one or more of the lists changed. Thanks for the update @Gertjan - I'm not 100% sure what happened, but I think that I might have had a problem with one of the feeds. I did a bit of a cleanup, and got rid of a couple of feeds. The system still restarts, but just once an hour, and it doesn't seem to cause problems with DNS resolution now. I have a script running as we speak that does a dig microsoft.com every 5 seconds until such time as an error occurs. It ran for several hours yesterday, and I have it running again now.

@Clouseau said in Dyndns client fatal erros: [0_1591770268498_PHP_errors.log](Uploading 100%) That error is you failing to upload something to the forum. Like an image : [image: 1591776003251-fb8a71d1-87f4-4196-8857-5b3fd820920b-image.png]

@DaddyGo ISP router with IKEv2 passthrough (NAT1) + pfSense IKEv2 passthrough(?) (NAT2) + Win10 with VPN client SW) Yes the above is the current setup. As is apparent, I don't know enough about this, but I was trying to apply the same principle to my separate, unrelated internal OpenVPN server. Where I had to passthrough ports on the ISP router for it to work. Win10 (work administered) is using Win10's built-in IKEv2 VPN. I read pfsense cannot be set-up as a IKEv2 client with username /password authentication?

What is your pfsense build running on? Is it virtualised by any chance? It may not be the same issue as mine, but I had EXACTLY the same symptoms you are seeing with Virgin Media and their 'super hub' - turned out that it was the Virtual NIC driver which was causing the issues. I wasn't using the latest VMNX3 driver on this specific VM, so I changed that and just like magic all those issues disappeared. As i say, it may be totally unrelated to you but I thought I'd share in case it helped.

I haven't received any E-mails today so lets hope so

I've resolved this using: https://github.com/jaredhendrickson13/pfsense-automator

@Alanesi There is a method where the header is examined for the original URL and the connection forwarded based on that. However, I have no experience with that and it would require something beyond the basic pfSense.

You probably don't need to go higher than 1M IMO. Currently, at least. Larger tables will cause more effect from 10414 if you're hitting that too. Until 2.4.5p1 is released. Steve

Look at the output of netstat -LaAn and see what port number that pcb corresponds to, and then look at sockstat and see what is listening on that port. That one process is being overloaded with requests, whatever it may be.

The two pfSense boxes can ping ALL of each others' interfaces. But the hosts within each respective Subnet can not be pinged. I think I may have taken a step back in terms of making things work. Here is a new more accurate diagram with some pfsense parameters attached. [image: 1591643514763-untitled.jpg]

John, will scope those variables out, thanks.

Could be any number of things. What error do you see? https://docs.netgate.com/pfsense/en/latest/routing/unable-to-access-some-websites.html Steve