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.

Why are you running 2.6 in an XG-1537? Do you see the same thing in 22.01? What module are you using? Steve

@stephenw10 Hi all, after first reboot i recovered the normal LED behavior (LED pulsating as heartbeat). Thank you so much ! Best regards Angelo

Thanks, power cycling did indeed clear it and I have now been able to update to 22.01.

@quasaur said in All IPv6 Home Network: Enjoying my SG-1100. I wish to switch everything to IPv6 using each host’s MAC as the last three segments of the interface ID. Unfortunately, it appears that pfSense requires the DUID of a DHCP client to assign it a static address, and no one on the planet seems to know how to get that from a MacBook running Monterey…not even Apple! PLEASE HELP! [image: 1645127681956-screenshot-2022-02-17-at-19.49.55.png] Run the following from the terminal:- sudo plutil -p /var/db/dhcpclient/DUID_IA.plist andyk@mac-pro ~ % sudo plutil -p /var/db/dhcpclient/DUID_IA.plist { "DUID" => {length = 14, bytes = 0x000100012743ca95003ee1c1af07} "HostUUID" => {length = 16, bytes = 0x8d4aa329f7175da2ac8fc3e713f04f63} "IAIDList" => [ 0 => "en0" 1 => "en1" 2 => "en2" ] } andyk@mac-pro ~ %

That would be the same. Once you've updated to Plus you will have access to the additional packages etc only powerd would need to be enabled. Steve

All I can say is this has worked for 2+ years with all versions of pfsense prior to 22.01. I either run tip from csh in an xterm window or run tip in a screen session and access the screen session from an xterm window.

@stevie_0815 We're looking into a fix.