I think i found. pkg unlock pfSense-kernel-pfSense pfSense-kernel-pfSense-2.3.4: unlock this package? [y/N]: y Unlocking pfSense-kernel-pfSense-2.3.4 Then : pkg upgrade Installed packages to be UPGRADED: pfSense-kernel-pfSense: 2.3.4 -> 2.4.2_1 [pfSense-core] You were right. Kernel mismatch.

Should work. You might have to use some creativity in booting to make sure it tries to boot from the correct USB drive depending on the hardware. LiveCD and Nano are no longer options in 2.4.X. LiveCD was eliminated in 2.3.X as well.

Problem was a switch in the line which didn't had the vlan

Those devfs filesystems are virtual/pseudo filesystems for access to device nodes. They always show 100% full. You cannot write to them. Your 50GB drive is 2% full.

After moving HDD it can be needed to reassign network interfaces. It is not trivial to do without display. Try pfSense image for serial console, then you can install pfSense directly and as bonus you will be able to access your firewall any time independent of the network. P.S. I hope, you do not need to change BIOS settings…

@Mr.Si: However, I feel as though if an update is made available as a release and is reported as successfully updated, then the thing should work. Or is that too much to ask? Did you read the individual release notes of the updates? Did you remove all aditional packages before updating, as advised? Why where you that much behind with your pfSense version? Did you do any custom modifications off the OS and did you undo them before trying to update?

Hi there, this was a clean install from a USB key.  The LAN works to browse and DHCP and everything else (outbound NAT, etc) just not on the web configurator. I'll see about a dmesg.

A perfect question for this place : https://forum.pfsense.org/index.php?board=72.0 Btw : what about calling Netgate - the guys how build the machine ?

@The: It works but its far from ideal having to turn off TLS. It's using StartTLS on port 587 by default, so not an issue.

ditto with xma111's comments….from there you can add geo blocking, malware IP blocking, ad blocking, open source with transparent code demanding updates when needed, IPS. Pretty rich...

If you're getting a 169.254 IP address then the client is failing to contact a dhcp server. You should see link LEDs even if pfSense is not booting fully. That video is of an older ALIX device so it may not behave the same as an APU. Did you install pfSense on this yourself? Try connecting to the serial console to see what's happening at boot: https://www.netgate.com/docs/pfsense/vk-t40e/connect-to-console.html Steve

@Derelict: Wrong image. Select VGA console in the downloader or connect terminal software to the correct serial port if that's what you really want. You probably want this one: pfSense-CE-memstick-2.4.2-RELEASE-amd64.img.gz Ahhhh. I totally overlooked that. Thanks for pointing that out. I will re-download and try again. Thanks!

the routing seems to be o.k. Strange. Are you sure, that tcp packets did come to port 80 of the firewall and the firewall answered (you can see the answers e.g. in wireshark)?

Normally it would use the hostname assigned to it, but I did see once where a host was receiving a hostname via WAN DHCP and it used that instead. Though the exact circumstances escape me at the moment, I don't recall it happening recently though. Usually the most you'd need to do would be a reboot. Where is it exactly that you're seeing the old hostname? In the logs on the firewall itself? Or on a remote log server? If it's the latter, it could be a (reverse) DNS or host file issue on the log server.