SG-1100 current firmware version? And DHCP troubles?

imark77

@SteveITS
Factory edition, now? Then there's CE which I assume is consumer edition. Sure add a plus but everything is getting confusing. After a long time of running an dell Omniplex with the downloaded ISO ( so simple only one option unless you want an older version or needed the arm variant ). I wanted some more powerful "quiet" less power-hungry hardware and I ordered 2 units 3 years ago that kept going on the shelf due to not being able to focus on configuring things. One of them updated fine when I pulled it back out and got started again and the other one decided it couldn't see anything to Update to. Just seems like a corporate policy is to push everything to the cloud subscription model and not care about the users that made the platform good successful and implemented it everywhere. Not necessarily arm related.

@stephenw10
Net install interesting not sure if that's good or bad. I hate getting these download stubs that doesn't actually let you get a hold of the download file for an archive, sometimes you just need to reinstall something and you don't have Internet.

I can't remember if I've mentioned but I am attempting to set up a mobile event Wi-Fi hotspot system due to the poor Internet coverage at our state park. They have events where a lot of vendors come in and they can barely get connections between phones with the user density and the park Wi-Fi is fed by consumer frontier DSL I believe. Came up with the idea last year thinking it wouldn't be that hard to get a few more pieces and put everything together. i was originally planning to use PFSense + Omada controller virtualized on a semi low power industrial system, ended up using Proxmox and that requires an ISO to upload.

I Planned to have a whole year to put it together ended up doing it Thursday before the weekend. Ended up going with plans c. Grabbing an AP, travel router and a hotspot. apparently it worked out well and umm I might've accidentally? ordered some overkill Wi-Fi equipment. Got the outdoor TP-Link stuff. I used the smallest outdoor AP and managed to cover the whole front of the park it's a semi small-medium in Town Park and that wasn't the really big crazy outdoor AP which I just found the other day that the box slipped down and got buried I thought I had another one.

Nearly having nightmares about VLANs. follow instructions, read things, watch videos, I think I have an understanding implement exactly as described and then have nothing work second-guess everything and go back to the beginning and repeat. Just finally got things figured out last night I think. I was trying to Bridge Main LAN control network to a VLAN control network and somehow that was causing a loop configuration on the trunk port of the switch. Assigning it as a separate interface and IP works but I really want the two segments to essentially be identical at least I'm finally feeling like I made progress.

That's on the 3100 and then most of this gets duplicated to the 1100 which my plan has been to make as a fully featured travel router that can do anything when I need more power than the small travel router I have that also doubles as a access point with a click of a switch. And now I'm gonna have a third network so I am hoping to keep it 90% similar so that the underlying structure is very similar. like using all the same the VLANs with similar names. Public equals guest IOT (yeah I don't trust them) otherwise naming is consistent.

SteveITS

@imark77 said in SG-1100 current firmware version? And DHCP troubles?:

CE which I assume is consumer edition

"community edition"... From the link I posted:
"Netgate announced the creation of pfSense Plus software, and the renaming of the open-source project to pfSense Community Edition (CE), in January 2021."

Netgate never really labeled the Factory Edition anywhere in the software IIRC, it was just "pfSense" and was considered FE on Netgate hardware.

https://docs.netgate.com/pfsense/en/latest/releases/versions.html?highlight=factory%20edition#understanding-pfsense-plus-and-ce-software-version-numbers

imark77

@SteveITS interesting so behind on things.

I've ran into a few things so far but not that announcement. There's at least two Reddit posts that have a few hundred comments with interesting opinions and a note on Wikipedia.

Looks like I'm running into a "Invalid DOS Signature" problem flashing the image. Back-and-forth with Support starting to get annoying. I flashed it three different times 2 different ways and about the try a 3rd. And no windows doesn't help next I need to dig out another thumb drive.

stephenw10

What exact image? How are you flashing it? Where do you see the error?

stephenw10

On an 1100 that has not been updated like that it may still have an old uboot version on it that requires a compatibility recovery image.

It may also show that error if you try to boot an amd64 image instead of aarch64.

imark77

@stephenw10 thanks, that information seems legit and makes sense. Finally got in contact with Support spelled everything out they sent me the image sort of, two separate emails one with a link & instructions.

pfSense-plus-Netgate-3100-recovery-24.03-RELEASE-armv7

Tried two different USB sticks and three different programs including DD.
Forgot that they no longer have a file upload within the GUI so had to follow the instructions with the serial terminal. Mentioned I was having an issue to Support haven't heard back from them.

## Starting EFI application at 05000000 ...
WARNING: Invalid device tree, expect boot to fail
efi_load_pe: Invalid DOS Signature
## Application terminated, r = -2

and

Marvell>> usb reset   
resetting USB...
USB0:   Register 2000104 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Marvell>> run recovery
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

imark77

@imark77 never mind just found the email from yesterday. They want me to run a command and send the result.
"run this command:"

printenv

stephenw10

You have a 3100? I thought you had an 1100?

pfSense-plus-Netgate-3100-recovery-24.03-RELEASE-armv7 will only boot on an 3100.

Marvell>> run recovery
reading efi/boot/bootaa64.efi
** Unable to read file efi/boot/bootaa64.efi **

That tells me this is an 1100 or a 2100 and not a 3100.

So it looks like there has been some confusion here in the image request.

You need the 1100 compat recovery image. If you have your support ticket number I can get that sorted.

imark77

@stephenw10 yes/no. sorry about that I tried to be as clear about it as I could.

I have both, full stop.

They were both sitting on different versions. I bought them at the same time, so it was confusing as why one was wasn't updating the 1100 when the other one 3100 was on a newer Version.

I got sidetracked and I need to check if Support replyed yet but most of the comments were about the 1100. The 3100 was working part from DHCP which was related to Kea DHCP failing to hand out IP addresses to some of my devices, disabling Kea and returning the "end of the world ISC banner" mentioned in another thread elsewhere. solved that issue which came up in some of the conversations.

So far I am stuck waiting for Support for the 1100 as I am not sure the firmware that they gave is the correct one.

well guess what they gave me the wrong firmware!
That explains so much! grrrrrrr. I didn't catch that when I copied the file name. Now I don't feel like as much of an idiot.

I reread my previous posts And Spotted some typos grrrrrr.

And lots of frustration, and rambling thoughts.
I solved my 3100 VLAN issues apparently port 5 of the integrated switch needs to be tagged as well. I think when I originally did this 2? years ago the documentation did not say that, it does now hmmm.

@imark77 said in SG-1100 current firmware version? And DHCP troubles?:

"it was Wi-Fi or Internet"

Internet should be ethernet.

@imark77 said in SG-1100 current firmware version? And DHCP troubles?:

"Yeah I'm going education"

should be
Yeah on going education

stephenw10

So you got the correct image and recovered it OK?

The 3100 internal switch port would always have required tagging there to pass tagged traffic to the internal NIC. It's possible the docs were updated but it wouldn't have worked without it.