I would search google for samaccountname and pfsense and see what other have done. All about configuring the authenticator with the requirements for your LDAP server.

Fiber or DSL?  What Modem??  NAT or Bridge?

searched further .. Looks like i'm having a similar issue "ingenium" had in march 2017 with pfsense 2.3.3 => https://forum.pfsense.org/index.php?topic=126742.0

Well, that was incredibly stupidly easy in the end … went to my FIOS box outside the house, unplugged and replugged the network cable that leads to the pfSense box, and all is fine now. And yea, I guess my new project is to replace that cable. Thanks for the help! -rob.

Enabling it in pfSense prevents users/processes access the memory regions of other users/processes by exploiting the Meltdown vulnerability. As I understand it that only affects users/processes running in pfSense not pfSense as a VM. You need to be looking for a fix in the hypervisor for that. In general Meltdown/Spectre has minimal impact for most pfSense use cases where there are not multiple users with different privilege levels running on the firewall. IMO  ;) Still better to have it available than not though. Steve

@mdes So you're probably aware of the following but it does cover what i understand to be the most relevant aspects of GDPR in relation to a pfSense device. https://www.firewallhardware.it/en/gdpr-pfsense-opnsense/ You'll know what you are using the device for, so some aspects will affect you more than others.

Control internet as per user (student) Are you talking about an URL filter here?  Squid + squidguard can do AD auth. You should try it out in your lab or test environment, and ask questions as you go if you get stuck.

Of course I figured out the answer myself once I started digging around a bit more.  I'll leave this here in case anyone else comes looking for something similar. The solution… In OpenVPN custom options, add...``` --route-up "/sbin/ifconfig bridge0 span ovpnc1" Bear in mind, I'm using this to carry the output of a span switchport over to another network in another location, hence 'span' in the command above.  If you just need to join the bridge, use 'addm' instead of 'span'.

It's that simple.

I will try this at work tomorrow. Note: I am using vSphere Client to connect to VMware ESXI machines.

The firewall can't do that on its own. Something had to trigger it, most likely the hypervisor sent a shutdown to the VM. Check your hypervisor logs.

My eyes! All that's missing is a scrolling marquee. Unless you have a sight issue, then I apologize, could you try to use a normal sized font? Speaking of fonts, it's like a variation of comic.

So we got everything working fine. When we use vpn we can connect to our server on opt1 and everything. But now we want to get external access to our server using the opt1 interface. But when we forward the port it doesn't work. we want to forward a port to our server that is n opt1 interface. example: external ip:poort x ->to our server that is connected to the opt1 interface

Veeam 9.5 vmtools installed Not sure if quiescence was enabled, I've already scrapped that pfsense instance and deployed a new one, had to reconfigure everything from scratch I don;t think it was a write issue, I had 30 days worth of backups and every single one of them had the same issue. I restored alreayd a few other pfsense firewalls and none had this issue restoring from Veeam. Bear in mind this was one of the first pfsense devices I deployed like 4+ years ago so it could be that some update screwed it up. I tried file level restore but I could not get the appliance working, as it was a urgent matter we just ended up reconfiguring it from scratch

You probably want to ask godaddy what they require for nsupdate on whatever service you have with them, then make the acme package do that.