Where can I find the non-"Community Edition" image?
-
Just received an SG-2220, and promptly attempted to restore the config file from my existing ALIX 2D3, rendering the internal SG-2220's SSD unbootable.
I downloaded the "Netgate ADI" USB stick image and was able to get the unit back to where it was. However, the web page now identifies itself as "Community Edition".
Can I download the image used to make these "Netgate ADI" boxes, or would I have to send the unit back?
Thanks in advance
-
As far as I remember its just a JPEG file.
-
As far as I remember its just a JPEG file.
I was thinking the same thing, that the functionality is equivalent (identical?), so I shouldn't care that I'm running the "Community Edition".
And it looks like I will have to "activate" support on the unit before I can begin the process of chasing down a non-"Community Edition" image.
Or perhaps I can just delete that JPEG file and move on.
-
You can access the "factory" memstick images at portal.pfsense.org after activating support for your SG-2220 at https://www.pfsense.org/activate.
Restoring your config should not render your device unbootable. It might very well contain a serial console setting of 9600 baud instead of 115200. Try waling through the common speeds in your terminal software (9600, 19200, 38400, 57600).
It should also trigger an interface reassignment from the reX (rlX??) interfaces in the ALIX to the igbX interfaces in the SG-2220.
-
You can access the "factory" memstick images at portal.pfsense.org after activating support for your SG-2220 at https://www.pfsense.org/activate.
Restoring your config should not render your device unbootable. It might very well contain a serial console setting of 9600 baud instead of 115200. Try waling through the common speeds in your terminal software (9600, 19200, 38400, 57600).
It should also trigger an interface reassignment from the reX (rlX??) interfaces in the ALIX to the igbX interfaces in the SG-2220.
Ok, will reluctantly "activate" the support. But you've given me some things to look at. And you're right about ethernet device naming and serial port speed compared to ALIX.
But I assure you, it just froze when loading the kernel after the config file restore. But I'm not discouraged. If it wasn't hard, it wouldn't be pfSense. :)
-
Many times it appears to "freeze" on boot but it is just a serial speed change. Happens all the time.
-
Many times it appears to "freeze" on boot but it is just a serial speed change. Happens all the time.
Fair enough. I didn't try 38400.
-
A follow up:
There was indeed a baud rate mismatch when transitioning from BIOS boot messages to kernel boot messages. But in my defense, the presence of that mismatch seemed to make the kernel "want" a carriage return to continue to load. So yes, it's possible that loading a config file that causes that console baud rate mismatch can cause the system to hang. YMMV of course.
