SSH in and look at /var/squid/logs/access.log and it should tell you what it was getting at the time.

ooooooppppsssss! was trying to put the lan in the same range as my wan…....

Not the actual mac, but its a TalkTalk tv box, not even windows, but I thought I'd give the windows suggestion ago before calling TalkTalk support to see what they suggest. I had looked on the actual draft web page earlier but couldnt see anything but wanted to double check anyway as a null for me is a 0 as in long pointers normally.

Thanx a lot !! It did the trick  ;D

future ref.. If your running pfsense on vm infrastructure you might want to mention that in your original post ;) But can not really tell if pfsense is on the esxi host, or your 2k12 client?

Ok thanks for that update.  I think MS made it by design (in terms of making the expiration date that far in advance for the default root certificate) due to the fact that the cert is tied to some core services (backup, dashboard console, etc) and since the essentials version is tied to market SMB's, it's probably a pain to re-create the cert after x amount of years…just my 2 cents.. Anyways, it still seems to function even though I import it and it displays that PHP error..is it still safe to use (ie, for OpenVPN RA) and that I won't run into major issues or will the system crash or have some adverse effect from me from forcing pf to use a cert it can't half read?

This guy made a kernel module for via nano temp: https://forum.pfsense.org/index.php?topic=52194.0 Although it was posted to various FreeBSD mailing lists it doesn't seem to have made it into FreeBSD. Steve

I've just updated to 2.2 and it seems to have resolved it. [image: Capture.PNG] [image: Capture.PNG_thumb]

I'll see what I can do. Still learning what I can and cant do on pfsense at the moment.

@johnpoz: Love to help but if I gave you "But I must explain to you how all this mistaken idea of denouncing pleasure and praising pain was born and I will give you a complete account of the system, and expound the actual teachings of the great explorer of the truth, the master-builder of human happiness. No one rejects, dislikes, or avoids pleasure itself, because it is pleasure, but because those who do not know how to pursue pleasure rationally encounter consequences that are extremely painful. Nor again is there anyone who loves or pursues or desires to obtain pain of itself, because it is pain, but because occasionally circumstances occur in which toil and pain can procure him some great pleasure. To take a trivial example, which of us ever undertakes laborious physical exercise, except to obtain some advantage from it? But who has any right to find fault with a man who chooses to enjoy a pleasure that has no annoying consequences, or one who avoids a pain that produces no resultant pleasure?" Could you help me? ;) :o :-[ ( ;D )

It's unlikely.

The GUI example helped me in the past… Since you know the IP, does either the external port or internal port stay the same? If so, you could create a rule like the one I have below. deny external port IP internal port deny 443 192.168.0.100 443

Given the very short backtrace and that is panicked in ACPI, I'd go with BIOS/hardware. Check for a BIOS update. You could try to disable ACPI, but I'd be surprised if that actually helped these days.

Looking at that list, most of those don't affect pfSense at all (like DTLS stuff), the others are fairly minor. Don't try updating that library yourself as it's likely to break things.