Yep, all good.  Not sure what the original problem source was, but am sure that once I went in via console, reset and reconfigured, it was receptive and behaved as expected.  Thx for the follow up!

Hmm, 71da does not appear to be listed as a USB PID anywhere I can see. Some drivers can seemingly attach based on the config type though such as urndi but without seeing the out full config dump there's no way to tell. And even if it does attach if the phone just shuts it down that won't help. We really need the phone to present a stable device to pfSense. Steve

That does not sound like the expected behaviour. Which ports are showing the blinking LEDs? Did that happen as soon as you installed the expansion card or some time after? Steve

oops.  posted in HW instead of Official HW.  Please move this thread.

Great to hear. Glad you're good to go.

You cannot use CE image for SG-1000, it's for x86-64 architecture. Download the SG-1000 ARM based image from portal.pfsense.org. If access to your portal expired after first year, it will be renewed automatically. Let me know if that's not the case. https://www.netgate.com/docs/pfsense/sg-1000/reinstall-pfsense.html

Found it. Had to register the device first… Using NDI and not S/N.

No OS is installed on Minnowboard.

Can I add a Mini PCI Express slot for an LTE Modem. OTG just don't give me reliability

Ok thanks!

Thank you, I missed that thread.  Ours had crashed or something (had to pull power) so I wasn't sure if orange was some sort of warning.

It can. See for example: https://forum.pfsense.org/index.php?topic=140301.0 Steve

This will disable the normal slow pulsing blue LED: gpioctl 2 duty 0 Steve

@stephenw10: … cross-over cable ... if the phones are not auto-MDIX ... Which means that the ports in the SG-3100 do not support auto-MDI/MDX as well? Seriously, in a 2017 design?

Thanks, it was a newbie mistake from me:) What happened is that SG-3100 stopped at startup in the "Syncing OpenVPN settings.. Enter Auth Password: enter the password for the OpenVPN user, that i tried to setup. it started normally. Deleted the OpenVPN user, and tested a reboot now, everything normal.

When are new x86 models coming out. I'm concerned about being able to run only arm binaries on these new models.

The shellcmds will continue to work though the gui will look like dot1q is not selected. The GUI works fine as long as you are aware of what that save button on the VLANs tab does. You ONLY need to use it to save the switch from port based to dot1q VLANs. The confusion is resolved in current 2.4.3 snapshots. Clicking the save button no longer does anything if the VLAN mode has not been changed. Snapshots are currently almost identical to 2.4.2 so you can run that if you wish. Steve