@Schmeling Makes sense. I would say that you should get the UPS ASAP though. If there are outages, there are probably also brown outs and spikes that could damage the equipment, and even a sudden outage could cause file corruption on most systems (This is very unlikely on PFsense though since they use ZFS now).

Yes, it's a known bug. Ugly but harmless.

@stephenw10 Starlink is Bi Polar and does play well with others!

@jrey said in Unexplained halt / and of course lan outage.: https://docs.freebsd.org/en/books/handbook/config/#adding-swap-space True, mounting another ZFS partition eats up big quantities of system resources. Happily enough, the swap partition is of type 'swap', whatever that might be. But probably a file system way easier to handle for the system as ZFS, ext3 or ntfs. Probably close to fat32 ;) The small swap partition just exists so it can receive a oops kernel plus other crash details in file. I would trim down the system load if the swap partition was use for actual swapping.

Yes, use a VPN: https://docs.netgate.com/pfsense/en/latest/recipes/remote-firewall-administration.html#use-a-vpn

@stephenw10 Yes, the VLANS were using differents NICS I have sorted the issue!! The quad nic from my hp t620 plus did not play well in the hp t730 Once i purchased a new nic for the t730, issue has dissapeared! All is working again!!

@stephenw10 thank you

@Fabiano1 I have had similar behavior. However, CARP was still involved, which was also the reason for the problem. But from the description it sounds very similar. Therefore here is the link to the issue: https://redmine.pfsense.org/issues/14171

@Patch said in Anti lockout Setting: @phayze said in Anti lockout Setting: Hi, i just change the 2nd interface which is <lan> to <wan2>. The rest of the interface is default to <optx>. I didnt know that <lan> is important until yesterday. I had rename back to <lan> already. Assuming you have a Primary WAN Secondary WAN Local area network connection And would like you internal names to be WAN - Primary WAN LAN - Your local area network connection OPT1 - Your secondary WAN, GUI name "WAN2" I suspect you could do that by Back up your configuration so you can recover is this fails Unplug your secondary WAN Add a explicit GUI firewall rule to your current secondary Wan and Lan interface Reassign / swap the interfaces for Lan & secondary Wan (pfsense -> interfaces -> assignment) Rename the GUI names for LAN and Wan2 Correct / move firewall rules etc Save your pfsense backup again Hi, i had done it and the problem is solved. Thank you.

@SteveITS thanks Steve, I appreciate! Will remove them and perform the upgrade sometime this week. Thanks again for your time! Best Regards, Yanick

@stephenw10 The solution was a complete reinstall. although I think it could possibly also be solved by defining the variable in the file itself because that was present. If the file was not present, the error "could not include file ("....") That solution would have been less time consuming. I must admit that the response time for the tac support was very fast. If it is good, it can also be said. Case closed

Hmm, yup. Checking....

Yes you can clear the package cache using: pkg-static clean -ay

You can open a bug report for it if it's repeatable: https://redmine.pfsense.org/ Steve

I doubt it's a hardware issue causing memory use like that.

Yes almost certainly port forwards. Since this is a routed subnet you don't actually need VIPs at all, just outbound NAT rules. However it's logically easier to see what's happening if you add them and it allows for forwards later if required.

@markchen Awesome, glad that solved it!

@gregeeh said in Can't update to 2.7: [2.6.0-RELEASE][admin@pfSense.localdomain]/root: pkg info -x pfsense ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/sbin/pkg not found This is an expected error after 2.7 was release. It should not cause any problem for normal operation in pfSense where all functions use pkg-static to allow for it. Steve

@johnpoz Oh, I believe you. All I can say is it stopped working for me. I thought Comcast had blacklisted me because sometimes when I'm futzing around I create a flood of alerts, sending one to Comcast, one to Outlook.com and one to ATT.net. IIRC, there were instructions on the notifications page previously saying to use commas and no spacing between addresses. No problema.

Sorry for not being clear, not only do I not have 2 minutes these days but don't want to change anything on the router while dealing with urgent medical phone calls that go through the pfsense router. When it blows over I plan to test turning the auto rules off, and possible test an inverse rule I mentioned above. Just now is not a good time to do anything. Thanks again to all who posted options, just wanted let you know I read and appreciate the posts.