@jimp Cool, thanks. I'll give it a shot over the weekend, hopefully it'll go ok :). Thanks again! -- Leif

A reinstall is probably easiest. If your WAN is DHCP you might be able to get away with running dhclient em0 where em0 is the actual WAN interface. If it's static or something else it could be done but it would be more difficult. When you reinstall, choose the option to recover config.xml and it will pull your current settings back in.

So you are routing the /30 to pfSense, from the the edge router? And then routing it to the Mikrotik? None of that is Layer 2. We are going to need a full diagram here with all the interfaces on each device and the IPs shown. It's not at all clear what you have here. Also a clear definition of what you trying to achieve. Steve

That's the only file you should need. If you had any packages installed it will try to re-install those at the first boot after uploading the config. If you don't have a valid WAN at that point it cannot do that. How exactly did it 'brick'? Do you still have access to the console? Steve

For refernce you need to use a FAT32 formatted USB stick for PFI or ECL. Since the installer image is UFS that generally means using a separate USB stick to hold the config. Packages should be re-installed automatically when you restore the config. If you didn't have a valid WAN interface at that point that process would fail. The package config is retained though. Steve

@derelict Host a web server, mail server, etc.

thank you i even searched for it, thanks man !

I just installed the latest 2.4.4 Development FreeBSD 11.2-RELEASE-p2 and its working with Apollo lake. No more HPET error. Also restore from previous backup from 2.3.5 and everything work pretty well. Package running on OpenVPN, Suricata and PFblockerNg.

I had a little spare time to test few things. restore config.xml (2.3.5) with fresh install of 2.3.5 = fail restore config.xml (2.3.5) with fresh install of 2.4.3 = fail edit config.xml (2.3.5) and removed the ACME package = worked in 2.3.5 and 2.4.3 uninstalled ACME package prior upgrading from 2.3.5 to 2.4.3 = worked So the ACME package was breaking the upgrade/restore, it should be obvious, because ACME depends on a php56 package, which is causing a conflict.

We "image" the pfsense routers once a week. As far as I remember none of the pkg commands worked - pkg-static ..etc, and thats why we werent able to install any packages either. But as said before, since I have reinstalled the server it works again. If it happens again I will try and look at the image and see what changed and maybe get an idea why it stops working. Thanks for the help anyway.

Out of interest what version was it you needed and what reason do you have for needing it? I can't think of anything of hand that should not on 2.3.5 at least. Steve

@callmejacklogan Great . Appreciate if you can share steps to do this .

Thanks. Now I put the pfsense in Proxmox and with this system I resolved my problem. Thanks for your support. Andrea

@jonanddad said in Trying to upgrade from 2.3.1 issues: Shell Output - echo yes pkg-static install -f pkg yes pkg-static install -f pkg Not like that. I was only checking if your "y" key on your keyboard is working. I presume you entered y or Y here : @jonanddad said in Trying to upgrade from 2.3.1 issues: Proceed with upgrade? (y/N) read: read error: Socket is not connected and then you had the error: Socket is not connected message. Seems more like some network error, occurring when the upgrade starts. edit : I just ran pkg-static install -f pkg [2.4.3-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: pkg-static install -f pkg Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: pkg: 1.10.5 -> 1.10.3_1 [pfSense] Number of packages to be downgraded: 1 3 MiB to be downloaded. Proceed with this action? [y/N]: Y [1/1] Fetching pkg-1.10.3_1.txz: 100% 3 MiB 233.2kB/s 00:13 Checking integrity... done (0 conflicting) [1/1] Downgrading pkg from 1.10.5 to 1.10.3_1... [1/1] Extracting pkg-1.10.3_1: 100% You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed. As you can see, I hit "Y" and the install (downgrade ;) ) continued. Btw : I'm using 2.4.3-RELEASE-p1 - surely not the old 2.3.1. edit 2: check out the forum, and you will find many issues when upgrading from old versions. Keep it mind it will take a couple of seconds to download the latest pfSense version. Some more seconds to export your config. A minute or so to build a bootable USB stick. Some more minutes to install from the USB stick. A minute to have LAN working. A couple of seconds to import your settings. A couple of minutes for pfSense to re install your packages, if you have been using any. And your done.

Hi, So, @fuzzywuzzy said in Cant ping LAN interface: 192.168.0.1 is the IP of pfSEnse. What did you enter as mask ? "24" ? Something else ? Did you change the DHCP pool in consequence ? What happens if you redo the initial setup using console access, and keep everything tod default (this works soooooooooooo good - that's probably the reason why they decides to take these values as default).

Hi , Yes the model is Zotac CI327 and yes the CPU is Intel N3450. I've tried Ubuntu and it's installed and works just fine , I have the problem with pfsense only. I can't find where to disable "Monitor M-Wait" in BIOS.

Everyone starts somewhere. It's a simple mistake. I don't have a 2.4.3 box I can easily test that on but in 2.4.4 the console reports this when you set an interface IP: You can now access the webConfigurator by opening the following URL in your web browser: https://192.168.87.1/ Either way the subnet should not be part of the URL. Steve

Hmm, weird. I've never seen that before. Hard to imagine filesystem corruption causing that directly. Perhaps you had an unapplied change there? It seems more likely it got part way through a boot at some point but I still can't see how it would have ended up with those ram drives. Another admin attempting to recover the firewall? Steve

The certificate probably doesn't match the server name. You need to add the fqdn as an alternate name. I also added an IP address in there so I can connect either way. It worked here for me in Chromium after I imported the CA that signed the new cert. Steve

What version of pfSense are you running? libssh2 is not in the default install on 2.4.3_1 or 2.4.4 as far as I can see though so it was probably installed as a dependency of mc or someother package. If you upgraded since it may have been removed. Or if another package was removed that originally installed it. It is in our repo though so you should be able to install it using: pkg install libssh2 Steve