So I reinstalled pfSense from 2.4.2-RC snapshot (20171117) and used a different boot drive (some spare WD Red spinning NAS drive). After some time I experienced a first panic, "Fatal trap 1: privileged instruction fault while in kernel mode". I applied options mentioned by @Birke, and rebooted the system. Sysctl complained that all hw.igb.* tunables are read only, but the system ran without a crash for over 30h. Not sure if these options helped of if I had luck. To get a better use of my systems CPU I enabled PowerD (Hidaptive) and AES-NI acceleration for crypto. Some time after that I experienced another crash, similar to previous one + mentioned "Fatal trap 12: page fault while in kernel mode". At this point I have no idea where does the problem come from. I contacted another forum member that owns this motherboard and he told me that his system runs stable without any tunable changes :(

That doesn't happen here when choosing the auto options. It sounds to me like it either went into the manual install or something was wrong with the existing disk layout that auto couldn't handle.

So, apply https://forum.pfsense.org/index.php?topic=138656.msg761867#msg761867  (first line) to have a fast, positive result ;)

@Jed: Appartently something is wrong with the DNS entry for pkg.pfsense.org Nothing is wrong. SRV records do not work that way. https://forum.pfsense.org/index.php?topic=130708.msg719850#msg719850

It was the netmasks wot did it. It wasn't clear - to me - what that netmask represented, so I left it at /32. After all, the interface only has one address, doesn't it? I suppose what it represents is the subnet that interface is connected to as well as the address of the interface itself. Changed it to /24 and all the VLANs suddenly appear. Thanks for the tip. Apologies for the late response, I have been rather unwell. The network(s) just about functioned without the use of VLANs but I do want to set things up properly. Again, many thanks.

@Jailer: PfSense doesnt support DHCP reservations. Assign static IP’s outside the dhcp range for anything you want the IP address to remain the same. Since when??  I have IPv4 addresses mapped to MAC addresses on my network.

I see you have one post.. so you are new. But why is always need to ask people to put every information needed for the problem? can you just spit the specs of the machine/laptop? and the config of what you think is important? What version 2.3.4 you had (vga, serial, nano ….) and what version 2.4.1 you update, from the gui directly? have you try backup config and do a clean install of the 2.4.1 version? and maybe then restore config? What machine (specifically) you have (with CPU and GPU)? If you want help, you should help us with your problem. Should be cultural by now, i think. If you don't have replays don't blame the community. Thanks

I am also having this issue following along with the conversion guide. I click the button and wait, finally I just get a blank web ui view. Update: I did an ls on /dev after pressing the button and saw that it created an new sa1 Went ahead and ran the script, updated, and let it reboot. It did take longer than normal to boot but I believe it was doing a filesystem check. Don't know for sure, as I don't have a console cable available. Just did the update to 2.4.1 from the web ui and everything rebooted again just fine.

FWIW, I recently re-loaded a half dozen old Alix boxes (2D3 and 2D13) with 2.3.5 I used the 2g-nano and they all worked fine. You really need a null-modem cable if you use an Alix.

I just found this thread.  I have this same problem! https://forum.pfsense.org/index.php?topic=140014.0 I can't find much about this or how to fix the error.  It's either because it doesn't like a self signed cert, maybe it doesn't like httpS on an alternative port of 10000 or something else. I did notice I had to put the credentials in this format on the last version "admin" for the user instead of "root".  I haven't tried root… Any insight?  Not much is logged other than it failed in the pfblockerng.log file in /var/log/pfblocker/

@mikeisfly: Duo means it's hyperthreaded, if I remember correctly. I also believe it is 64bit. As far as a single port you can use a switch but the switch will have to support vlans. That's assuming the computer supports VLANs.  Not all do.

Early next week is the current target

I feel relieved and embarrassed that the tool was in my hands all this time…that's how the learning process works, I guess! Wasted all that time searching and researching yesterday!

Provider is Altibox (Norway), and they have both TV and phone, but I just have internet from them. They are sending internet through VLAN 102 and TV signals through VLAN 101. I have IP phone from other company. For TV I use the satellite receiver. It gives better picture quality. Thanks for the tip regarding internal NIC.