sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN
-
Hello,
My netgate sg-1100 WAN does not acquire IP address from the ISP box dhcp server, nor gives IP on dhcp request on the LAN port. USB console shows the whole boot process up to:pfSense 2.4.4-RELEASE (Patch 2) arm64 Wed Dec 12 14:40:29 EST 2018 Bootup completebut no menu shows up.
I was able to access this console menu before importing a 2.4.4 config file. WAN was not getting IP either, until I tried to update the firmware... WAN then acquired an IP, and I could access the webconfigurator (to import the config file).
I'm stuck with this booted-up but unusable sg-1100 device. What may I do next ?
Thanks for your help !
-
That is an ancient firmware version. I would reinstall 22.05 clean and restore the config again.
Open a ticket with us to get the installer image: https://www.netgate.com/tac-support-request
Steve
-
Thanks for your answer.
How works the installer, as I can't access the device in any conventional way?
Is there a way to have the installer for the 2.5.1 CE for compatibility with other systems I manage so that i can use the same config file? -
It will boot the installer from USB and allow you to complete it from the serial console.
There is no 2.5.X image for the 1100. After 2.4.4p3 the factory images moved to pfSense Plus with the new numbering scheme.
Unless you have a very good reason though you should use the current firmware which is 22.05.Steve
-
@zephred said in sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN:
so that i can use the same config file
Some are compatible depending on the pfSense version:
https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html -
Yes, there should be no problem restoring a 2.4.4 config from an 1100 in 22.05 on the same hardware though.
-
@stephenw10 OK, thanks, I just submitted a support ticket request.
-
@stephenw10 said in sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN:
Yes, there should be no problem restoring a 2.4.4 config from an 1100 in 22.05 on the same hardware though.
Is the config file hardware-dependent ?
A 2.4.4. config file from a CE version on a standard PC won't be able to be restored on a sg-1100 with 22.05 software ? -
It would restore into the 1100 OK but it will ask you to reassign the interfaces since the 1100 has only one mvneta NIC and whatever you are restoring from almost certainly does not have that. Normally that's OK between hardware if, for example, your old box has em NICs and the new one has ix. You just reassign them before the reboot and and it comes back up in the new config. But in the 1100 the 3 ports are all VLANs on the one NIC it has which makes re-assigning much more complex.
If you are importing a config into an 1100 (or any of the devices with an onboard switch) it's often easier to modify the config file directly before importing it. We can help with that if you open a ticket.
But if your old config was from an 1100 then that problem doesn't exist.Steve
-
@stephenw10 said in sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN:
It would restore into the 1100 OK but it will ask you to reassign the interfaces
That's what I had to do when I imported the 2.4.4 config. It's not that complicated, much less than re-configuring the whole pfsense-software.
Any explanation on why the device is usable after this simple config import ? (no console menu, no IP acquired on WAN, no IP offered on LAN for webconfig)I have downloaded / sha-checked / gunziped the pfSense-plus-SG-1000-recovery-22.05-RELEASE-armv7.img image. flashed it into a USB-stick according to https://docs.netgate.com/pfsense/en/latest/solutions/sg-1000/reinstall-pfsense.html, plugged it into the sg-1100 (tried the 2 front USB-plugs) and booted the device. But no flashing process starts, it just boots the 2.4.4 OS up to the "Bootup complete" message (still without any menu). PLugging / unplugging the stick nevertheless triggers messages on the console.
I tried with another USB-stick in case that one was bad (a badblocks run shows it's not).
I noticed the /dev/sda5 partition is non-mountable (wrong fs type).Writing this message, I notice a "netgate 1100" device in the left menu of https://docs.netgate.com/pfsense/en/latest/solutions/sg-1000/reinstall-pfsense.html, guess it's probably the sg-1100, click on it and notice the reinstall procedure is different than the one on the page I was given in the email I received... Yet another 2 hours down the drain trying to make this device usable...
So I press the key to get the Marvell>> prompt, and type "run usbrecovery" which also fails:
Marvell>> run usbrecovery ** First descriptor is NOT a primary desc on 1:1 ** switch to partitions #0, OK mmc1(part 0) is current device MMC erase: dev # 1, block # 0, count 4194304 ... 4194304 blocks erased: OK reading efi/boot/bootaa64.efi ** Unable to read file efi/boot/bootaa64.efi ** ** Unrecognized filesystem type ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ## Starting EFI application at 05000000 ... WARNING: Invalid device tree, expect boot to fail efi_load_pe: Invalid DOS Signature ## Application terminated, r = -2Re-tried with the stick on the other plug:
Marvell>> run usbrecovery ** First descriptor is NOT a primary desc on 1:1 ** ** First descriptor is NOT a primary desc on 1:1 ** switch to partitions #0, OK mmc1(part 0) is current device MMC erase: dev # 1, block # 0, count 4194304 ... 4194304 blocks erased: OK starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found reading efi/boot/bootaa64.efi ** Unable to read file efi/boot/bootaa64.efi ** ** Unrecognized filesystem type ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ## Starting EFI application at 05000000 ... WARNING: Invalid device tree, expect boot to fail efi_load_pe: Invalid DOS Signature ## Application terminated, r = -2 -
@zephred said in sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN:
Any explanation on why the device is usable after this simple config import ? (no console menu, no IP acquired on WAN, no IP offered on LAN for webconfig)
I would still expect the console menu but you would not see any interface IPs there unless you also configured the VLANs and switch. It's almost always easier to add the required config sections to the file before importing it. We can convert that for you if you open a ticket:
https://www.netgate.com/tac-support-requestThe SG-1000 is not the 1100. The 1100 is arm64. You need to open a ticket with us to get the correct image.
Steve
-
@stephenw10 said in sg-1100: no menu on console, no dhcp server responding on LAN, no address acquired on WAN:
The SG-1000 is not the 1100. The 1100 is arm64. You need to open a ticket with us to get the correct image.
My concern has always been with the sg-1100, not sg-1000... Even the email giving me the URLs to upgrade talks about sg-1100... I've already lost way more than a full working day simply trying to make this device work.
I was asked for the S/N of the device when filling in the ticket, why was I given a sg-1000 image if it's different !? -
I have no idea. Do you have the ticket number so I can review it?
-
@stephenw10 #1037563769
-
Thanks.
I apologise it looks like human error. The form was submitted as an SG-1000 but we should have caught that.
I have sent you the correct firmware image for the 1100.
Steve
