i have 2 netgate xg-2758 linked together in high availability sync.

Both were on 2.3.4, tried upgrading straight to 2.4.2.  Errored out, was then able to upgrade backup Xg-2758 from 2.3.4 to 2.3.5 then to 2.4.2.  So I'm confident the upgrade will work but not at all familiar with command line options.

Can still putty into primary xg-2758 and everything is still working.  I need to be either to change the update branch to legacy stable version so I can then run the update command or download 2.3.5 and install from shell.

Thanks.

And you upgraded from what version of pfsense.. If really old maybe you were not using dnssec, and whatever it is your trying to go to doesn't pass dnssec so you get no answer..

Really going to need more to go on vs kodi/flawless hosting..

Addon to what?  A browser, your roku?  Plex server - some other sort of media stick..

Impossible to even help you figure what is wrong if don't know what your even using..

Here let me give you an example.. My car is broken, after I filled up the washer fluid..  What is wrong with it - it use to be not broken, but now its broken.

Thanks Per Hansson! Now I can read most of the pfsense startup messages, do a useful pftop, display the firewall log, etc.

I know some active members of the forum have a different opinion about implementing the console interface, but my experience has always been, better safe than sorry.


Figured some kind of typo ;) hehehe

Hi all,

I followed the suggested approach (removing packages on old system, create config backup on old system, restore config backup on new system, reinstall packages on new system). All worked fine but I overlooked one thing… Thanks to a prompt reply fro Netgate support I managed to resolve this.

The issue was that the network card configuration (the network interface naming in the config backup was not compatible with the new system) and the device got stuck in the console waiting for network card assignment. Connecting through a serial connection with the console I could select interfaces and proceed.

Thanks for the support!

regards.

Thank you very much. What remains is to see what are the recommended NIC cards for the software to run omptimally.
To make the story short, I just plan to use its QoS feature.
And read a little more about LAN/WLAN/VLAN or whatever they call it.

Sorry if my english isn't that good. It's just my 4th language (learning order not preference order lol)

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...