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

Try going to System > Updates/Firmware and selecting the 2.3.X security/errata branch. No go back to the Dashboard and to force an update refresh. Check branch is still set to 2.3.X, set it again if it updated back to 2.4.X.
If it offers you 2.3.5_2 as an update go to that first then update to 2.4.3.

Steve

Hi jimp,
some good news here.

Your statement that "pkg can't reach the pfsense servers" pointed me to the right direction; I haven't understood it fully, but I found a way at least to unlock the pkg issue.

In my case, it was due to a double stack IPv4/IPv6 issue: to solve it, I had to temporaly disable the network interface linked to the GIF port; removing IPv6 name resolution plus removing the IPv6 default gateway and firewall rules to route IPv6 traffic didn't suffice.

I don't like to be so inaccurate in test results, but as IPv6 connectivity was actually working, defining this problem will require some more tests and I meant to find a quick workaround for everybody experiencing this kind of issue.

Let me know if this rings a bell.

@chris1bass said in pfsense not receiving a WAN address:

it did do a DHCP discover. But looks like it never got a response from the modem.

Well there you go explains why pfsense doesn't have a WAN IP, if it asks dhcp server for IP and doesn't get an answer - then no its not going to have an IP ;)

Work upstream to why offer is not being sent.

Thank you for your time Derelic. I looked at the interfce settings and found out, that I had left the subnet-setting for the interface at /32 instead of changing it to /24.
Maybe this setting is bit confusing, because if I should set a single IP-address for the router interface and not a subnet. I suggest giving this setting a separate line or at least a caption "subnet size" or something similar.
Anyway - excuse my dumbness.
Best, Karl

Okay, there really wasn't any way I could figure out how to deal with this through the GUI. I plugged in a keyboard and monitor, and reset the LAN's IP address after the machine went through startup. That's the only way that made sense and was straightforward.

Since there is no internal connection between the host and pfSense, that's an expected behavior.

You may configure the eht2 as a virtual bridge instead of passthrough and give the host an IP on it, or add an additional virtual network and interfaces to both the host and pfSense for management access.

@luckman212 seems like you have a solid background with WAN IP issues on devices. My FiOS connection keeps dropping on the WAN interface and comes back when I reset the interface. Is there any way to solve this ?

I posted in detail here what is happening:
https://forum.netgate.com/topic/133896/wan-drops-connection-3-4-times-a-day-to-r210-ii-verizon-fios

Thank you!

Sorry for necroposting, but to resolve the installer looking all funky, in putty:
Window -> Translation.
Set "Remote Character Set" to "Use Font Encoding" (it's at the bottom of the list).
Leave "Handling of line drawing characters" set to "Use Unicode line drawing code points."

0_1534523880961_2018-08-17 10_15_38-PuTTY Reconfiguration.png

I'm understand complexity of task, and because of it I ask this at forum before destroy my pfSense ☺ . Obviously use pfSense for build bins is really not good idea. About simply use NAT: I really like how in pfSense work Squid (for proxy) and HAproxy (for reverse proxy) and how I can combine HAproxy with pfBlocker aliases and GeoIP, and it will be awesome if them will support at least mainline OpenSSL version like optional plugin, and LTS line 1.0.2 by default that goes in FreeBSD. Or maybe some paranoiac guys do this already and have how-to in home wiki 😃

@nogbadthebad said in Restore from AutoConfigBackup without user information:

Guess you need to do a fresh install, then recover everything from a backup except System as that contains the users & groups.

Try it on a different PC first.

What is the device pfSense is running on?

it is an older Dell server with complete oversized hardware. 3 network cards.
I already started with the reinstall. Copied the config.xml down from AutoConfigBackup services and started to restore one by one service through the "standard" backup/restore function.
Looks good so far! Services and all rules etc. are restored including the snort stuff and so on. Found there a problem or may a bug during restore:

after restoring the config of the package manager the list of the manager shows the services which where installed what is good.
But just once! Will say everytime you choose to reinstall of a not yet complete restored package the list disappears again and you have to restore the package manager config again. This is taking time if you need to reinstall a lot of services.

So I guess the list is updated everytime a package has been installed too with the packages which are completely installed already.
Better would be if the package manager just updates/modify the list of installed packages instead overwriting it with just complete installed packages.