@allinarush said in Cannot get WAN port to light up: There is no error Goto console mode. Option 8. Type dmesg and look for any NIC messages . Something there ? Another test : connect the WAN cable to another device like a switch. Use another cable that works on another interface. Worst case : WAN port out. Not a big deal because you have spare - identical - ports (the OPT1-OPT4) - pick any and declare it WAN..

Hello again, I have resolved the second "no boot device" issue. I had to disable AHCI. It works fine in IDE mode with Legacy boot. I'd LIKE to resolve these problems if possible as I'd preferably like to run with UEFI and AHCI enabled.

Thanks for your answer. Indeed when I reboot, I don't see the error coming back.

I have occasionally seen that. That page is what shows when it is running a firmware upgrade since that is also pkg based. If you see that page it is because a pkg update is already running and it's trying to show you the output from that. When I have seen it it's because the process has stalled for some reason. I would expect a reboot to clear it or you can usually manually kill the existing update process and restart it. Steve

UP

Thank you for your help. It does seem to be up and running now! Thanks.

I was able to log into the console and restore to a previous configuration (not a backup)

Looks like that's probably pre-UEFI so I doubt that's a factor. Yeah there was some odd stuff when SATA first started to appear, like appearing as IDE devices... I would look at the device modes available in the BIOS for the SATA ports. Steve

The first two interfaces would be igb0 and igb1, did you mean LAN is on igb1? The WAN should never hand out DHCP leases. It might itself be a dhcp client though. LAN is the only interface defined by default and the only interface configured for DHCP by default. Have you configured all 6 other NIC as interfaces and enabled DHCP on them? Steve

Yeah you should not use the ADI image for that the com ports are standard I imagine. What sort of bad performance are you seeing? Steve

I've tried disabling acpi in the bios and well - it seems to work now. Sometimes the solution is so easy you just don't think about it. Thank you for your help!

Thanks Steve, Agreed double NATing is not whats wanted. The Draytek has a DMZ, I will give that a try. Mark

After switching to a modern USB 3.0 stick the interaction with the motherboard seemed better. The Corsair USB stick showed up in the BIOS as a USB hard drive. I was able to use only the new UEFI boot settings in the BIOS, boot and install pfSense 2.4.4 using ZFS file system to the NVME SSD, configure the 1Gbase-T WAN and 10Gb SFP+ LAN interfaces, connect the Netgear CM1000 DOCSIS 3.1 cable modem and Ubiquiti US-16-XG switch to pfSense and connect to the internet using a 10G/1Gbase-T port on the Ubiquiti switch connected to a 1Gbase-T laptop. So it works at a basic level without configuration of either pfSense or the Ubiquiti switch, including the 10Gb SFP+ fiber ports. Lots of configuration work to look forward to, especially the Comcast dynamic IP to IPV6 VLANs.

When you unboxed your 1100 it already contained the latest version. @troch said in SG-1100 setup issues: I changed the ports to the specified mvneta0.4090, etc. You mean : you edited the saved config.xml from your PC pfSense, and imported it like that into the SG-1100 ? True, editing a backed up config.xml file from system A using processor Y can be used on system B, processor Z. Note : processor in not important here ^^ Also : export an identical pfSense version. You could upgrade from an older pfSense version but then you should check out ( == read ) the upgrade noties. "What I would do" : Power up the new SG-1100 hooked up only to it birth-line : the micro-USB-serial cable. No Ethernet cables - nothing else. Just the console and the power. See how it boots. For example : check if both LAN and WAN are already assigned. Take a look at the config.xml file of the new SH-1100 (i will be small). Use the command line option, command "viconfig". You can always reset to "factory settings" with the console menu. You could hook up a LAN device, goto the Web GUI and import your original (from old PC° config.xml "as is". When done, use "reboot" from te console. When it comes up, the boot up process will ask you to assign interfaces, as drivers names for the NIC's changed. When these are setup up, it should finish booting, installing packages you used on the old PC pfSense etc (this could take some time). Basically, that's it. edit : what I don't know .... because I do not have hands on experiences with the SG-1100 : it could include 'other' hardware devices like build in switches that need settings in the config.xml - which will not exit any more when you copy over that file from another system. That's why I mentioned above : compare initial config.xml files first

magic!!!!!!!!!!! ti work !!!!!!!!!!!!!!!!!!!! thanks you so much for helping me