You might be able to prevent it loading by running at the loader prompt: set hint.i915kms.0.disabled=1 boot Assuming you're talking about the graphics driver. Steve

I assume you have no native IPv6? If you left is configured you ISP may have enabled something that is still broken for example and it's trying to use that in preference. It seems more likely that the remote end point was disabled. I know if nothing that could have changed like that in pfSense base. If you have anything that auto-updates like Snort or pfBlocker that might have started blocking traffic. Steve

There is no way to do that as far as I know. You might suggest it via a feature request on https://redmine.pfsense.org Steve

thanks,

You might want to ask that here: https://forum.netgate.com/category/11/espa%C3%B1ol Steve

@emammadov Enable the TLD option which will Wildcard block domains/sub-domains

@stephenw10 Hi, I saw that too and checked for "SU" and "Su" and only "Internal_Subnets " exists so I have no idea where that came from either. I clearly must have accidentally clicked on on the Wizard at some point in the last few days and not noticed leading it to get very confused. It all seems good now though. Thanks again for your help G

I'm not sure what you're asking me. I personally use squid + squidguard in explicit mode with no SSL interception.

@hasan_ciit said in network subnet access between multiple tunnel: i have pfsense at azure cloud @hasan_ciit said in network subnet access between multiple tunnel: i have zabbix nms at azure Are both those things true? Without adding any additional P2s anywhere or using some sort of proxy at the pfSense site I don't think this is possible. Even with adding one P2 you could NAT the connection on one leg but that would then only allow opening connections in one direction and I believe Zabbix usually requires both. Steve

For VNC viewer to work in a locked-down LAN, you need to allow access from the client on tcp/5900. http://www.uvnc.com/onlinehelp/11.html

Looks like it's 192.168.88.18. I suggest that AP is not configured correctly. Try turning it off and see if that removes the problem. Steve

It may have come from a different subnet. Either way I did end up tracing it down to a faulty DIMM :) Thanks

Mmm, I mean it looks like an ACPI problem, like bad tables. You might update you BIOS if an update is available. You could try running vmstat -i see if that shows a device with high interrupt rates. You can also try booting in verbose mode and see if that shows any useful ACPI errors. Interrupt the boot at the boot loader and then enter boot -v. See also: https://www.freebsd.org/cgi/man.cgi?query=acpi&apropos=0&sektion=4&manpath=FreeBSD+11.2-RELEASE&arch=default&format=html Steve

Great. Thanks for confirming, might help others. Steve

It is probably time to consider more current hardware. It is definitely time to consider upgrading to more current software.

@stephenw10 said in pfSense has detected a crash report or programming bug.: Yup, copy and paste the error here and we can try to assist you further. Perhaps he can provide a crystal ball to assist us.

Probably no detectable difference.

For the firewall to resolve 192.168.1.100 for example, the PTR has to exist somewhere.. Be it unbound via dhcp registration, static lease registration or host override. Or some other dns that the clients are registering in, etc. Say for example if your AD shop, you should prob be using your dhcp and dns in your AD. Then just create a domain override for IP ranges so that you can go ask for PTR from your AD dns, etc.. There are multiple ways to skin this cat - but somewhere involves a PTR lookup from DNS somewhere your clients IP is listed.

Well that's no problem, just install pfSense with one interface and install Squid on it. Though you might consider running Squid just on FreeBSD instead if you don't need everything else that pfSense brings. If you want to run transparently you need port forwards in Mikrotik to redirect traffic to it. Otherwise you need to configure clients to use it directly. Steve