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

Worked perfectly! Thank you!

Thank you Steve for the insight. That was very helpful.

@kiokoman thanks!

That's a Hyper-V issue, not pfSense.

Probably a boot option like "Secure Boot" you can disable to get past it.

@Nullity, I was facing the same problem, " CAM status: Command timeout" and your answer worked for me on pfsense 2.4.4 installation using a pendrive:

I've add "set hw.ata.ata_dma=0" on boot options and install proceeded with no errors.

Once pfsense installed, it was needed to edit the /boot/loader.conf file and add the same option so that persist it on next boot.

Thanks.

The switch issue appears to be a general problem on 2.5.0 right now, at least on the 3100.

@robina80 said in Installing mSATA on APU board:

i have succesfully done it

downloaded and put the image on my usb stick using "win32 disk imager"

inserted it in free usb port connected serial cable to laptop,

opened up putty and changed baud rate to "115200" to see the boot menu and boot of the usb

closed/opened putty again and changed the baud rate to "9600" so i can install and follow the on screen instructions

once done i changed my boot order so the first option was my mSATA

once i could log back in the webgui i restored my settings so it was like how i had it before

Hi !
I faced up to a BIG trouble while upgrading to the latest version of pfSense (2.4.4-RELEASE (Patch 3) ) : unable to boot, something to do with CPU microcode update ?

# service microcode_update start If the CPU requires a microcode update, a console message such as the following will appear: Updating CPU Microcode... /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done. Done. >>> Setting vital flag on pfSense... done. External config loader 1.0 is now starting... ada0s1 ada0s1a ada0s1b Launching the init system...Updating CPU Microcode... Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x800e29000 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff81189dde stack pointer = 0x28:0xfffffe0035f2a940 frame pointer = 0x28:0xfffffe0035f2a940 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 608 (logger)

I proceeded like robina80 explained, booting from USB with "pfSense-CE-memstick-serial-2.4.4-RELEASE-p3-amd64" version, USB keyboard attached, Serial port to 115200 ==> Everything went back, pfSense is now able to boot ;-)

Hello.

I have re-installed the squidguard package and re-booted the firewall. Now I can see squidguard on the services menu. And I have not lost the previous configuration for the service. Next step: play with the ssl url filtering.

Thanks for your help.

basically my routers are aging and instead of going with expensive home network crap i want to build my own network solution out of my old workstation
why because find me a router with a 3.2GHz core 2 quad 8GB ram and i was originally goig to use x86 ddwrt but then i found pfsense and saw how much i could improve my network security and how i could seperate my server and home network

I know this topic is quite old, but did anyone resolve this issue?
I am running into the same thing.

[2.4.4-RELEASE][root@att.com]/var/run: ls -l total 144 drwxrwxr-x 2 root operator 512 Sep 29 03:08 .snap srw-rw-rw- 1 root wheel 0 Sep 29 03:08 check_reload_status -rw------- 1 root wheel 3 Sep 29 03:08 cron.pid -rw------- 1 root wheel 3 Sep 29 03:08 devd.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:08 devd.pipe srw-rw-rw- 1 root wheel 0 Sep 29 03:08 devd.seqpacket.pipe lrwxr-xr-x 1 root wheel 19 Sep 29 03:08 dmesg.boot -> /var/log/dmesg.boot -rw-r--r-- 1 root wheel 5 Sep 29 03:09 dpinger_WAN2GWv6~2001:1890:c03:960::11e5:95e2~2001:1890:0c03:0960:0000:0000:eee5:95e2.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:09 dpinger_WAN2GWv6~2001:1890:c03:960::11e5:95e2~2001:1890:0c03:0960:0000:0000:eee5:95e2.sock -rw-r--r-- 1 root wheel 5 Sep 29 03:09 dpinger_WAN2GW~206.121.142.210~206.121.142.209.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:09 dpinger_WAN2GW~206.121.142.210~206.121.142.209.sock -rw-r--r-- 1 root wheel 6 Sep 29 03:09 expire_accounts.pid -rw-r--r-- 1 root wheel 25478 Nov 5 14:18 filter_reload_status -rw-r--r-- 1 root wheel 6 Sep 29 03:09 filterdns.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 filterlog.pid -rw-r--r-- 1 root wheel 6 Nov 5 14:20 haproxy.pid -r--r--r-- 1 root wheel 230 Sep 29 03:13 ld-elf.so.hints -r--r--r-- 1 root wheel 129 Sep 29 03:13 ld-elf32.so.hints srw-rw-rw- 1 root wheel 0 Sep 29 03:09 log srw------- 1 root wheel 0 Sep 29 03:09 logpriv -rw-r--r-- 1 root wheel 6 Sep 29 03:09 nginx-webConfigurator.pid -rw-r--r-- 1 root wheel 5 Sep 29 03:09 ntpd.pid -rw-r--r-- 1 root wheel 6 Sep 29 04:19 openvpn_server1.pid -rw-r--r-- 1 root wheel 5 Oct 14 11:17 pfSense-upgrade-GUI.pid -rw------- 1 root wheel 25 Nov 11 11:46 pfSense_version -rw-r--r-- 1 root wheel 1 Nov 11 11:46 pfSense_version.rc -rw-r--r-- 1 root wheel 3 Sep 29 03:08 php-fpm.pid srw------- 1 root wheel 0 Sep 29 03:08 php-fpm.socket -rw-r--r-- 1 root wheel 6 Sep 29 03:09 ping_hosts.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 radvd.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:08 sshd.pid drwx--x--x 3 root wheel 512 Oct 14 11:17 sudo -rw------- 1 root wheel 5 Sep 29 03:09 syslog.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 unbound.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 update_alias_url_data.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 updaterrd.sh.pid -rw-r--r-- 1 root wheel 0 Sep 29 03:08 utmp -rw-r--r-- 1 root wheel 394 Nov 11 11:47 utx.active -rw-r--r-- 1 root wheel 6 Sep 29 03:09 xinetd.pid drwxr-xr-x 2 zabbix zabbix 512 Oct 14 11:17 zabbix-agent

I am also having an issue with the /var/run folder getting filled up due to Zabbix.
I have to uninstall Zabbix from pfSense and the file goes from being really small to about 3 megs in a week.

[2.4.4-RELEASE][root@att.com]/var/run: cd sudo [2.4.4-RELEASE][root@att.com]/var/run/sudo: ls -l total 4 drwx------ 2 root wheel 512 Oct 14 11:17 ts [2.4.4-RELEASE][root@att.com]/var/run/sudo: cd ts [2.4.4-RELEASE][root@att.com]/var/run/sudo/ts: ls -l total 3168 -rw------- 1 root wheel 3211264 Nov 11 11:53 zabbix [2.4.4-RELEASE][root@att.com]/var/run/sudo/ts:

I was not having this issue until I updated pfSense to 2.4.4 release p3 about 2 months ago.

Thank you for any help you can provide.

@stephenw10 ntopng is the only thing's broken i think

Bad drive maybe? Can you drop to the command line and check dmesg for errors?

the big mystery part is that the wan is always online and only the virtual lan go off.

Solved! I reinstalled and all work!

Hi,

The subject is known.
Bad WAN, bad files system, broken DNS, etc.

Use a the magic keyword "repo-pfSense-core.sqlite" and put it in here :
c7ac8ca7-70f6-415c-bf73-61d4c9791943-image.png