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.

@q54e3w said in SG-3100 - which cellular module: Curious to any further progress made since the last post. Im using a external Sierra Wireless ES450 which works brilliantly but would be interested to move to an onboard solution to reduce hardware. External solution still seems to be the best bet. It hangs off the firewall vs being inside but with something like the Nighthawk MR1100 you get an ethernet connection for WAN and the possibility at some point of up to a gig service.

The C letters appearing on the console indicate that it can't locate any valid boot media. Reinstalling from USB or SD card recovery should get you running again, assuming it isn't a hardware issue. Contact support at https://go.netgate.com and someone can get you access to the firmware image for the SG-1000.

Please open a support ticket at https://go.netgate.com include your serial number or NDI. Steve

We have something like that on the roadmap for the future, a "switch wizard" of sorts that will do what you're after there. Still in the planning stages so no ETA.

@davidology Thanks, but it's already on the way back for an RMA. Worked with support and could not get it to recover.

Thanks, I will stick with portal.pfsense.org, the image download worked fine. And I understand that this is only needed for recovery. I may have been under the wrong impression that the above site is being discontinued with the gold membership going away.

It sounds like a hardware issue. Drop a note to support at https://go.netgate.com/support/login and someone can help you out.

It may be as simple as getting it connected and running pfSense-upgrade from the console shell manually. There are more suggestions here: https://www.netgate.com/docs/pfsense/install/upgrade-troubleshooting.html

More than one way I suppose. If you want to keep the Cisco, just go with your 2nd plan. May need to configure a trunk/uplink port on the Cisco for the SG-3100. If you want to get rid of the Cisco, you'd have to directly connect the switch to the SG-3100 and configure all the VLANs there. Perhaps some other folks can chime in with their experiences and/or recommendations.

@jimp Thanks! Will probably go with the 5100.

That makes sense. Thanks!

Start a new thread for your issue. It is not the same. Post your interface settings, output from ifconfig -a, output from etherswitchcfg and as much information about your version as possible (uname -a, pkg info -x pfSense, etc). This thread is not the same as your issue. Similar, perhaps, but not identical. Do not assume it is the same.

If you are not able to interact with the console connection, either the settings are incorrect, or the cable used is not working properly. I know you have exchanged the cable out for a different one, we need to get another USB console cable. The few times we have seen this the USB cable was bad.