I found that I can get to the GUI using http://192.168.2.1/system.php.

I went right to System/Update to try to fix the update but it reply's with

Retrieving      Unable to check for updates

same here. GRE under ipsec. I setup a cronjob every minute correcting the mtu when needed, my tunnels are up now. I'm running 2.4.2.

@MainSail:

No known way for me fix this failed upgrade! FreeBSD showing 11.1 but still showing 2.3.4-Release-P1 as the current version/"up-to-date". I later noticed that all F/W logging had stopped so at that point the only solution was to just reinstall. I had 2.4.0 ready to go on a thumb-drive and then upgraded to 2.4.2 through the console and restored my configuration from backup. All looks fine now and happy with what appears to be a noticeably faster VPN.

If someone else have this issue, backup your config and try this -
https://forum.pfsense.org/index.php?topic=135582.msg742380#msg742380

Yep you're right - that was indeed one of the problems.

fetch -v https://www.google.com resolving server address: www.google.com:443 SSL options: 83004bff Peer verification enabled Using CA cert file: /usr/local/etc/ssl/cert.pem No server SSL certificate fetch: https://www.google.com: Authentication error

I thought I had fixed it by SCPing over cert.pem from the source tar.gz and updating the symlinks everywhere, but that wasn't working reliably. Two consecutive fetch commands right after one another would have different results, one would connect over TLS successfully and the second would fail. I think I've messed up horribly somewhere when tweaking the box.

Finally gave up and restored factory settings, and everything seems to be good again - was also able to upgrade to 2.4.2 without issues.

Thanks Gertjan for all your help.

RTFM https://www.netgate.com/docs/sg-4860/reinstall-pfsense.html

Wanted to finally update this.  Remember this error:

Waiting for Internet connection to update pkg metada and finish package reinstallationUpdating pfSense-core repository catalogue…

Essentially, it was FreeRadius.  It needed to be re-installed but, with the previous problems I was having, it was not working.  Once I resolved those (i.e. Internet and Internet VPN working), I was able to reinstall this package.  That took care of this.

Hopefully, this helps someone dealing with the same/similar situation.

Pretty sure it went well then..

If you really want you could re-install all packages with a 'pkg install -f' or perform a complete reinstall from installation media if you want to be 101% sure.. but seems like way to much work for highly likely no gain..

ZFS snapshots are also usefull, if you do one before you screw up.

Currently I have 2.4.2 installed, i might have had another issue prior. Now i have another issue, basically i'm capped at 100Mbps whereas the DSL service is 250Mbps Up & Down. My NICs are both gigabit so i'm wondering what is causing the loss of performance? Could it be the PCs specs? Duo Core..

Thanks again for all your help :)

@Jordan10:

@bimmerdriver:

@Jordan10:

The pc is running Windows Server 2016, sorry i should of mentioned that before, it also meets all the hardware requirements needed for pfsense apart from the dual nics which is why I've ordered another nic today :)

Okay, that's another matter. I'll explain how I have my system set up and you can see if that makes sense for you.

My system has 3 nics, wan, lan and other. The wan and lan nics are externally connected to the bridged port on the modem and and a physical ethernet switch, respectively. Internally, they are connected to virtual switches. The lan switch is set to allow the management operating system to share the lan nic. The wan nic is also set to enable source mirroring so I can connect a virtual pc to the switch running wireshark.

With this configuration, I can have multiple pfsenses connected to the wan switch and I can even have a completely virtual lan and virtual clients. I can also have physical clients on the physical lan switch. I've been using this configuration for several years and it works well.

The "other" nic is connected to a lan port on the modem so I can access the modem GUI from the hyper-v server. (I bumped up the routing metric on this interface so no traffic will exit.)

Feel free to ask more questions if you have any.

Thanks for the info, so from what you've said wan and lan nics can go to the ethernet ports on my router and i can still let the router handle dhcp and the wan connection? Or do i need to have a physical switch as well in order to do this? Obviously I'll have the wan and lan nics connected to the virtual switches running in hyper-v as well.  New nic is arriving tomorrow so hopefully I'll be able to access the web configurator again at least which is what I'm struggling to do at the moment even with the existing nic i have which is set up with pfsense too  :-\

I attached a picture. Maybe it helps. The AP, along with pcs and other devices are on the lan switch.


I'm saying that, barring any problems unrelated to the 7551, any upgrade will work on it. In other words: If the upgrade failed, it wasn't because it was run on a 7551.

The only specific failure that affects the 7551 is a fresh installation of 2.4.x, which can be worked around as mentioned in the wiki.

So if your upgrade failed, post about that instead with more detail because it doesn't have anything to do with the hardware.

OK, Thanks for you insight!!  8)

I came upon that very thread. I left it for over 2 hours without success.

BUT, the system is not frozen. I came back after 2 hours, and short-pressed the power button - and the "Syncing vnodes" message came up and the system powered off gracefully. If it is indeed hanging because of pfBlocker (which incidentally, I do have installed), then there should be some log entries somewhere surely?

Is there some way to access the "console" mid boot to see what is going on? I'm using the "vga" version of the image so I don't think the info is going to the serial console or anything.

Basically after I restored my config file the pfsense became a brick. No ping to the LAN interface at all, no boot, no response from keyboard if I press enter or anything (but numlock works). The only fix was to reinstall (or to manually edit the config.xml I suppose but that doesn't fix the underlying problem).

@luke1018:

…. there are errors ....

Bad news  ;)
Billion exist already - and people report nearly daily new ones.
Next time, take some more time to compose your question, and add the error with all it's details.

It's normal that you don't see the card anymore in windows after writing the pfSense install image on it. MS Windows has no clue of the BSD partitioning scheme or the UFS filesystem used.

@Thierry69:

Doesn't seems to want to boot on the USB stick …
Thx

You have to make some changes in BIOS.

https://forum.pfsense.org/index.php?topic=43574.0

http://www.triebwerk23.de/joomla/index.php/firewalls/watchguard-xtm-5-xtm-505-515-525-545-pfsense-64-bit

I finaly upgrade to 4.2 with command shell
login to the box with ssh (user admin pw : ….)
go to command shell
type command : "pfSense-upgrade -d"
it take a long time and finaly the upgrade is done.