All For what it's worth, I just thought I would share my experience of my SG1100 failing to boot after a local power outage 2 days ago. After power was restored to the house, the SG1100 power LED came back ON, but with no activity on the console & the boot LED was OFF. After six attempts at power cycling the device, only once did it actually boot. So I took a punt at putting a voltmeter across the connector of the 12v power supply while off load and the reading was 11.8v. Decided to swap out the PSU for a equivalent 12v / 2A spare I have. The spare gave a voltmeter reading of 12.2 volts. Connected the replacement PSU to the 1100 & it booted first time. Has been working just fine ever since even after several halt commands/power cycles. I'm impressed with the resilience of my two year old 1100.

@dominikhoffmann See https://forum.netgate.com/topic/177872/sg-1100-black-diamond-led-always-off-in-23-01/

@stephenw10 Thanks Steve.

To close the loop: disabling VLAN_HWFILTER on the igb port solved the issue. Put this in Early Shell Command using the Shellcmd package: /sbin/ifconfig igb0 -vlanhwfilter -vlanhwtso I can now get a DHCP address on the igb0 WAN port from the Azores Networks WAG-20D ONT.

@thatguymark said in Netgate 2100 update to 23.01 from 22.05 issues: In the process of trying to install some packages on my Netgate 2100, I was prompted to update the firmware to 23.01. Don't install packages if a later version is detected/offered. Select Previous Stable in the update branch, so you're installing 22.05 packages on 22.05. (that said, 22.05 repos are offline temporarily, but it sounds like you already upgraded) @thatguymark said in Netgate 2100 update to 23.01 from 22.05 issues: CPU usage is all but maxed out Was one package pfBlockerNG? There was a bug in an initial 3.2 release when TLD Wildcard blocking was enabled in DNSBL settings. Resolved in a package update that was probably after your post.

Were you able to resolve this? For clarification the fact it shows as unregistered on the registration page is unrelated to not being able to pull in packages. It is correctly shown as an eligible device on the System Update page so should see pkgs if it's able to reach the pkg repos. If you're still seeing it try running at the CLI: pkg-static -d update and see what error it returns. Steve

8200max 2 Protectli FW6E and 1 Zotac ZBOX CI662 Nano in a Proxmox cluster. 1 Mac Mini Intel 2 QNAP TVS-h1288X NAS Power cable of netgate unit was dangling as it was freshly installed ;) [image: 1677666829770-69810040066__597b7506-ab09-4fb8-afaf-c97d5e5f3cd7.png]

@stephenw10 here in australia, its only really in the last few years that properties are upgrading to 1gbps internet connections as previously 100 would have been considered good. In addition, guests are only now seeming to stream and cast, rather than use the tv systems provided by the hotels. We are seeing a lot more throughput now, but nothing like other countries like America. But there is often a lot of scope creep where they want a simple network, and then they add on cameras, iptv, admin networks, public networks, zigbee, etc... So its important that i don't run out of routing and switching hence why I'm trying to read up about the new models. But it seems from the feedback that the 8200 is very capable, even though it looks like a desktop style router. Not needing VPN, ipsec, or any b2b configurations, we don't really need the expandability of the 1537 for now, so i think the 8200 seems like the smart choice

In the 2100 the SFP combo port has very limited configuration. It will appear as a 1000baseSX link whatever is connected to it: [admin@2100-2.stevew.lan]/root: ifconfig -vvm mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:b6:13:59 inet6 fe80::2e0:edff:feb6:1359%mvneta0 prefixlen 64 scopeid 0x1 inet 172.21.16.220 netmask 0xffffff00 broadcast 172.21.16.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> So it will either work or not with no real options tweak if it doesn't. Steve

@stephenw10 That said... I have an 1100 out in the field plugged into a Netgear GS110TP and it works without issues. Standards-compliant hardware will not pass power. YMMV when using hardware that isn't one of the 10-15 major manufacturers but if they state that the hardware follows the 802.3af/at/bt standards then you really should be fine.

@steveits Gotcha. I never realized that the 1100 has a switch.

@integrityrv In general yes. If the source had a built in switch (1100/2100/3100) you might need to have Netgate support convert the config for you which they will do for free. Otherwise it will ask to assign interfaces during the restore. The new one must be the same or later pfSense version.

@rustydusty1717 said in SG-3100 OPT1: I see this currently: mvneta2 (WAN) mvneta1 (LAN) and then I do have a mvneta0 - is this the opt1 port? Yes https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/io-ports.html Did you import a config? Or May delete the interface?

@stephenw10 Thank you!!! Problem resolved!!!!!

I have the drive we fitted to various devices which unhelpfully shown as 'NT-32'. There are a few threads here with other users reporting the drives they used in 5100s. I don't really have anything I can recommend personally.

You should be able to do it either way but I would also do the firmware update first. If only because the vast majority of updates will have been done (successfully) in 22.05. Steve

@rloeb I started this thread and suggest closing it :-) Tech support was very prompt in providing me with a USB firmware recovery image for the 5100, which installed easily and then upgraded the installed packages. Been working very well since then. Upgraded last night to the new Snort and pfblockerng packages and everything is copacetic. Rare to find a tech support team that responsive!

Re-reading this if it actually says that on the System > Update page rather than the System > Register page you should open a support ticket: https://www.netgate.com/tac-support-request All Netgate hardware should be automatically enabled for updates. Some older devices might require intervention though as they predate the introduction of the NDI. Steve

@bmeeks True! This happens when one is "new" to pfsense.

[image: 1677060845713-c914ae12-8147-489f-a96b-31228e8fe89c-image.png] [image: 1677061153517-a77d129a-e93b-4848-a5c8-a3f3476a192d-image.png]