Looking through more comments on that PR, it looks like for some people still seeing the issue it was actually a clock/timekeeping problem and not a bug. Maybe it hasn't hit pfSense because nobody is using that specific hardware or setup that had the clock issue.

On paper that makes sense. In the real world, it doesn't. People still unplug equipment. They see an outlet and yank out whatever's in it so they can charge their iPhone. They don't care if that plug is attached to a huge important-looking box with LEDs and a big battery icon—they gotta check their Instagram! So, it's still best to have a layered approach. Since installing ZFS on our firewalls that support it, I've not had a single issue with filesystem corruption. With UFS it was happening everty couple of months at some locations.

@jimp said in SG-3100, Wi-Fi options or not?: I would say it's technically possible in a pinch, but a firewall case is generally a bad place to put a radio. Say no more. If you say it's not a great idea, that's enough for me! I'll stick to the tried and true. But, I still cross my fingers and hope that one day there will be a decent option here. If not for the cost savings, then simply for the smaller footprint and less things to stick on the wall...

Thanks for that Derelict. I guess I will just have to wait until the new server arrives and see what happens then. Appreciate your help.

Thank you Steve. Updating Coreboot fixed my issues with the card. /Thomas

I thought this issue had resolved itself but looks like I was wrong. Just had another unexpected reboot. Nothing in the logs and nothing captured via serial console messages. Oct 14 08:10:12 php /usr/local/pkg/apcupsd_mail.php: Message sent to walterstarks@icloud.com OK Oct 14 08:11:25 apcupsd 33988 Communications with UPS restored. Oct 14 08:11:27 php /usr/local/pkg/apcupsd_mail.php: Message sent to walterstarks@icloud.com OK Oct 14 13:10:02 snort 33227 invalid appid in appStatRecord (4385) Oct 14 14:25:00 snort 33227 invalid appid in appStatRecord (4385) Oct 14 16:30:01 php-fpm 22709 /diag_backup.php: Successful login for user 'backup' from: 10.0.1.20 (Local Database) Oct 14 18:24:06 syslogd kernel boot file is /boot/kernel/kernel Oct 14 18:24:06 kernel Copyright (c) 1992-2018 The FreeBSD Project. Oct 14 18:24:06 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 14 18:24:06 kernel The Regents of the University of California. All rights reserved. Oct 14 18:24:06 kernel FreeBSD is a registered trademark of The FreeBSD Foundation. No idea where to go from here.

Re: SG-3100 GUI Broken Thanks @JeGr and @jimp for the suggestions. Looks like I had been on 2.4.3 prior to installing pfBlock. Ended up doing the recovery, back running again.

Hi Mate. Thanks for your response. I don't think so , the wan is set up statically and supplied by a data centre. The connection will be coming from another firewall VLAN. When we plugged the older pfsense in with the same config no issues were occurring. Just trying to look through the logs using shell due to the fact they only show a certain time in the GUI. Thanks

@jimp Thank you -- your answer here and earlier makes sense, particularly that direct plugins of non-switch devices on the OPT ports is not the same as plugging in a switch that is prepared to manage the assigned VLAN segment. There is no further action necessary on this thread. Thank you for your time and attention here!

That looks fine. The APs are expecting VLAN 8 tagged? Did you add firewall rules to the lagg0.8 interface on pfSense?

sorry I was meant to create a topic for the XG-7100, please ignore last message or delete it

If the unit replaced an older supported device then the support crew will need to update your records to point to the new device. Drop them a line at https://go.netgate.com and include the device ID from your new unit.

@chrismacmahon thanks again for the recommendation. Though I will be without it for a little while support already messaged me back. I appreciate you pointing me in the right direction.

I appreciate the suggestions. I put it on a UPS for a more clean supply of power. The heat seems to hover around 60-63°C. However, through some further research followed by some trial and error, I have narrowed the issue to having a traffic shaper on a VLAN. Seems to be a common issue for some. I have since removed all VLAN traffic shapers and I've been up for nearly 24 hours. It was rebooting every hour before. Thanks for all the help!

No reason to delete it, just not sure how much help we can give when not understanding what your actually asking.

@lugie said in XG-7100 - 2.5Gbps ISP: It appears the only confirmed way to do this is an ES-16-XG combined with a separate 10G Ubiquiti router. That's a lot of $$$. It would make more sense to have one rack mount device to do both jobs. You do not need separate 10G Ubiquit. router, you can use pfSense with 10GB nic in it. This is what i am using. ES-16-XG - pfSense, works like a charm. For pfSense (to pull current 1.5GBit from Bell), you do not need anything fancy, even old Core2Duo will do the job.

Yes, i did the run recovery with a USB stick that had the 2.4.3_1 firmware written to it. I would really like to stay on 2.4.3_1, but it appears that upon restoring the XML config file, it downloads package data for 2.4.4 and messes itself up because of PHP version mis-matching. What a cluster! How do I set the boot env manually (and have it be persistent)?

Thanks, worked like a charm. I appreciate the help.

@jimp said in Recover Soft Bricked SG-1000: If you remove all power and cables from the device for a few moments, and then only plug in the console and power, do you get any output at all? Or does the serial device not even show up on the client OS? Your safest bet is to contact support so we can check into that problem deeper -- use https://go.netgate.com to reach the support team. Hello jimp, Thank you for your response. I tried what you suggested to no avail. On a Windows box with Putty the connection just fails. Using a Linux box with minicom I did notice something interesting. If I try to make the connection and then pull the console cable, minicom does state it lost connection with the device. Even though I never made a successful connection with the device to recover it. So there is some hope. I will do what you suggested and reach out to the support team and see if I’m not holding a paper weight due to my stupidity.

Write the ADI version to a usb stick and take a mini usb cable for the console. Save the config, load a fresh copy of 2.4.4 and restore.