Issues installing pfSense CE on a Minisforum MS-01 baremetal with new Beta7 installer.

DrSKiZZ

@knight-of-ni said in Issues installing pfSense CE on a Minisforum MS-01 baremetal with new Beta7 installer.:

@knight-of-ni

To answer my own question, additional options do indeed appear, once you change the default password of "admin". The new password needs to be complex too, which explains the unexpected results I received the last time I tried this.

Relevant BIOS screenshots can be found here:
https://forums.servethehome.com/index.php?threads/getting-vpro-remote-kvm-working-on-minisforum-ms-01.43269/post-413075

Yep, once you change the password you can disable AMT, but doesn't resolve the DHCP issue unless I'm missing something when I went through the settings.

stephenw10

But you still can't disable vPro entirely like you now can on the ASRock board?

knight-of-ni

@stephenw10 That's what it looks like.

If I find any new information or hear back from minisforum support, I'll post here.

DrSKiZZ

@knight-of-ni said in Issues installing pfSense CE on a Minisforum MS-01 baremetal with new Beta7 installer.:

@stephenw10 That's what it looks like.

If I find any new information or hear back from minisforum support, I'll post here.

Thanks. Keep me posted.

knight-of-ni

I received a response back from Minisforum support this morning, and they are passing the request up to R&D.

Not big news, but at least they are considering this.

Danyo

@knight-of-ni Just entering this because I ran into this issue too, after a week of trouble shooting, and I'm curious to find out if they get a fix out at some point.

I could easily switch the 2 for my configuration, but my WAN line comes from the left, LAN goes to the right, and it for some reason will keep bothering me to have it reversed in the back.

knight-of-ni

@Danyo Yeah, I know what you mean... I too want nic 0 to be WAN and nic 1 to be LAN. I manage several pfsense boxes, and it will mess with my head if the ports are swapped on one of them.

Note, however, there has already been one vulnerability against Intel's vPro. That made me think twice about exposing the i226-lm nic to the Internets.

Like @DrSKiZZ , I bought a twinax DAC cable and patched SFP port 1 into my switch instead.

thewho

@knight-of-ni I really hope R&D gets back to you! Thank you for trying to get them to understand how big of a problem this is for us! Proxmox and pfSense are main reasons for me to use it..

knight-of-ni

Sorry for the late reply.

For anyone interested in Minisforum releasing a bios fix for this issue, I'd recommend you email support@minisforum.com and voice your interest in this.

Hopefully they will not state a fix is not possible, but if they do, kindly point them to the following:
https://www.asrockind.com/en-gb/index.php?route=newsblog/faq&faq_id=91

This is a competitor's board with an AMI bios and the same i226-LM chip. I am not a bios expert by any means (it probably is not as simple as this sounds), but that link did seem to get them to consider the possibility.