@derelict Good idea. I checked, but the pins look good. [image: 1646767635789-6cc5cda1-76f5-4286-a5e1-a8f542e29cd7-image.png]

Yeah, I reviewed it with the support agent and we agreed it was an issue that required further testing of the hardware. Steve

@stephenw10 Nice! Thank you again!

@stephenw10 Thank you.

@stephenw10 Okay, thanks for the info. I'll keep on with the 5100 for now. It would be nice to see some PPS support return whenever the next generation happens...

@rcoleman-netgate Thanks for your reply!

@rustydusty1717 said in SG-1100: @keyser said in SG-1100: If it posts, get the recoveryimage an try to re-image it, to find out if it can be salvaged. not necessarily, it has come back 4-5 times however it has taken up to 3 days for it to come back. But that makes no difference - it’s still useless, and just waiting for it to come back online makes no sense. You need to re-image it to see if it’s actually hardware thats defective, or just the OS/Filesystem/install that is broken

If you created the symlink you can just wait for the next release. Either that or the patch will restore the LED function and neither will cause a problem at the next update. I'm not aware of an issue with WoL on the 5100, do you have a redmine number? Or a link to previous discussion. WoL is not a function the 5100 is expected to have, it's untested. It may work. Steve

Nope, something like this or this.

@mmapplebeck said in SFP+ Problem after 22.02 upgrade on 1537: I powered the unit down via IPMI, and powered it back on, no go. Mmm, that may not be sufficient. Because the NIC remains at some level still powered when the unit is shutdown it may not clear that state. We have seen devices they required removing power entirely to reset. Obviously that would only be possible if you have remote access switched power of some kind. or with on-site hands. It seems more like the module itself but I can't see why it wouldn't be supported in 22.01 when it was in 21.05. Steve

My SG-1100 is now fixed and running the latest OS and U-Boot firmware. Thanks for everyone's help. before forcing update: U-Boot 2017.03-armada-17.10.2-g6a6581a-dirty (Nov 01 2018 - 16:04:57 -0300) /usr/local/share/u-boot/1100/u-boot-update.sh -f after forcing update: U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Oct 07 2021 - 18:20:55 -0300)

@rcoleman-netgate Thanks! I just completed the replacement and went kinda painless. Outside of cable modem issue, the firewall replacement process was a breeze!

Open a ticket with us and out support guys will come back to you quickly: https://www.netgate.com/tac-support-request Steve

I'm sorry about that. Looks like you were hitting this: https://redmine.pfsense.org/issues/12796 I thought that was fixed but apparently more digging required there. Steve

Much better than pushing it through the FW. Glad my wrong idea helped.

Thanks all! I thought it would probably be fine but I just wanted to check before a potential purpose. Regards, Andy

Yes, that's pretty much it. So it's possible (but almost always wrong!) to have several VLANs untagged on a port but you can only ever tag back one VLAN ID the other way. Steve

@stephenw10 said in Netgate 6100 firmware 02.02.00.00t-uc-15: It has updated CPU microcode to address CVE-2021-0146. Steve Thanks!

I have not seen anyone do it. It would be easy to restore pfSense though, just boot the installer and install as normal. Steve

@stephenw10 Awesome. Thanks.