Hmm, now I'm confused. Your screenshot above shows two igb NICs. That's a 1G Intel NIC. It can't link at 10G. Are you using different NICs there now? I expect the idrac to show the real hardware MAC for each port. The internals only vtnet ports should show a MAC generated by Proxmox.

@stephenw10 bingo...its a 10 for you sir

Failed to reproduce it here so far. So, yes, I think trying ctl+t there would be the next step.

Almost certainly this: https://redmine.pfsense.org/issues/16362

OK continuing there instead.

@jay_k indeed :) , glad you were able to resolve your problem

Yeah you cannot have two DHCP servers. You must choose one and I would use the DC for that. Configure it o use the same subnet as pfSense and pass the pfSense LAN address as a default gateway to clients.

@patient0 said in Where to report a security vulnerability in Pfsense Admin GUI: https://www.netgate.com/security Thanks mate

@joelwhrs I will bump this a bit. Not sure if you figured a way to create custom SMTP triggers, for instance: link goes down, link comes up, no internet, ACL event, etc. I'm also looking for a way to create simple event trigger. From what I understand, all notifications are "fixed", I get one when device is booting or when it finish booting, or cert about to expire. On that note, where to find list of notifications? I just upgraded to 25.07.01.

You might be hitting this bug: https://redmine.pfsense.org/issues/16362 Do you see the syslogd service stop in Status > Services? If so check for a connection refused message in the main system log against the remote server.

Yes geoip blocking is never 100% accurate. Check the alias table in Diag > Tables. Make sure it actually contains the subnets you're trying to block. It's often better to pass traffic based on an alias rather than trying to block alias. But that really depends on what traffic you need to serve there.

You may edit the PCI ordering of the devices in the vmx config file of the VM to ensure the nics stays like before and the newly created Nic will be the next available vmx<N> adapter. ethernet4.pciSlotNumber = "40" ethernet3.pciSlotNumber = "39" ethernet2.pciSlotNumber = "38" pciBridge0.pciSlotNumber = "17" pciBridge4.pciSlotNumber = "21" pciBridge5.pciSlotNumber = "22" pciBridge6.pciSlotNumber = "23" pciBridge7.pciSlotNumber = "24" scsi0.pciSlotNumber = "16" usb.pciSlotNumber = "32" ethernet0.pciSlotNumber = "33" ethernet1.pciSlotNumber = "34" ehci.pciSlotNumber = "35" vmci0.pciSlotNumber = "36" sata0.pciSlotNumber = "37" This is an example of a VM in HW Version 21. It may look different on previous versions. Key is to have the pciSlotNumber of ethernet<N> adapter in order and no conflicts with other devices.

@stephenw10 said in Reboot via ssh does not work?: Hmm, weird. Well definitely check the logs after trying and failing to reboot via SSH. So far I could not reproduce it. So will keep my eye on it.

I updated the redmine with a new patch. Let us know if that helps.

@Qinn FWIW, if you want the loader.conf.local file backed up in the config, you can create a custom patch in System / Patches. Since you are patching against an empty file, be sure that you do not enable Auto Apply.

@stephenw10 Swapped in Unifi gateways at 4 of 5 locations and setup site magic. Dead simple, reboots fine. Going to test that for now. Big PFSense fan here, bought 2 6100 max and 2 8200 max. this wasn't an easy choice but these ongoing reboot issues are not sustainable. Thank you stephen. If I roll back, ill msg back here for some help.

@Gertjan Thanks for this. It worked in 2.8.1 CE. I appreciate it.

@newUser2pfSense said in pfSense Computers Rebooting: I don't have a serial connector on this new machine. It's a "PC" type device right ? So it has a VGA build in, and USB for a keyboard ? Then good news, you don't need the serial console port at all. You already found it. The 'VGA or DHMI' screen + usb key board were the equipment you used to install it in the first place, is your 'console' access. This 'console' access works even when NICs are not initialized and not known yet .... this is the access you need. Btw : your old PC with pfSense : get out the disk, hook, it up to another PC (now : remember : this drive won't have any 'Microsoft ' partitions ... ^^), mount the drive in the OS, and you can 'inspect' it.