@teamits said in Change IP:

@pama said in Change IP:

The local IT has disconnected pfsense nics from vsphere

OK but then the symptom of slow web GUI and inability to access updates is to be expected. The slow GUI happens because DNS isn't working and each try must time out on all DNS servers before the GUI moves on.

I was assuming the NICs were being reconnected after the IP change.

Not sure where to go from here. The only issue I've had with changing IPs is the rebinding check not allowing the new LAN IP but I think that bug was fixed a while ago.

pfsense can query the dns without any problem...

Will install again then, just for sure, thanks!

I don't get it, so what then? Just open the port in the firewall rule and allow any guest to connect to any host if they match the protocol or port?

@smartersolutions said in Garbage console output from new:

I was wondering if you could provide step by step how to add this as I am also at this stage and would like to be able to try this for myself. Many thanks. James

Be smart and you'll find solutions, RTFM: https://www.netgate.com/docs/pfsense/hardware/boot-troubleshooting.html#disabling-acpi and adapt it to your current needs.

I saw another post almost identical to this recently where the problem ended up being a bug in the terminal software (minicom, perhaps) where it failed to update/scroll when maximized. Restoring it to a smaller window allowed it to work.

Maybe it's a client-side issue?

Thanks @viragomann for the answer, When I ran the function it did fix something in the records in the fs but it did not fix the boot issue, after using Dr. Google and some keywords in the search I came across this.

TL;DR:
Same process as you but they used the following command
/sbin/fsck -y /
This seemed to have fixed the issue and got all of the machines online.

Thanks for your help, It definitely helped me.

it's done !

and it's working :)

thanks @jimp your plan worked as expected, upgrade VM "in place" was a good advice.

I only have 30 seconds of timeout in my RDP Session when disable / enabling CARP between nodes.

See your logs :
@electricshock said in pfSense 2.4.4 (latest) and OpenVPN organisation:

certificate verify failed

About the video : have a look at the official "Netgate" videos

No errors in system log.
No relevant errors in resolver log (only a few failed to resolve host : new_name.internal , due to devices that are already configured on the firewall but not on the dns server. Those entries have no concern with the void tables.)

Regards

I apologize for the post earlier and believe I ended up finding the answer. I should have dug a little harder into the forum. The answer looks to be that it won't restore without modification to the XML and applicable interfaces at a minimum. Not sure about the other options in the config backup, but I'll play it safe and manually configure.

Thanks!

Sorry for the delay, we have been busy: https://forum.netgate.com/topic/139375/pfsense-2-4-4-release-p2-is-now-available

Thanks!

Hi Jimp,

there was an ext-20-xdebug.ini there. I moved it out of the way, error seems to be gone.

Thank you and kind regards,

SnakeZZ

Ok, and you are able to boot the installer and complete the install but it fails to boot after that?

Or it boots and plays the startup beeps at that point but just shows nothing on the console? What is the last thing shown there?

Steve

The HA won't be live since the pfsync version is different but CARP failover works between them.

Generally better to put the primary node into maintenance mode / disable CARP and then upgrade or reinstall. With older primaries it's easy to accidentally break the config since older versions didn't have safeguards like we have now.

It seems the issue was more banal than i thought.
Removing completely the pfBlockerNG solved the issue, once removed a fresh package installation worked perfectly with no further issues.
Note: Reinstalling from the Installed Packages tab didn't work, i had to completely remove it.

Thanks
Nicola

It seems that everyone's methods are different.
Has no one ever done that ? https://www.iseepassword.com/create-bootable-usb-dvd-on-mac.html

Use the Mailreport package to get regular updates on the zpool and schedule a monthly scrub with the Cron package, it's not that hard.

@jimp This was the fix. I removed the SD card, and the installer worked fine. It does seem a bit bizarre because I did specify the SSD drive during the install wizard. The other weird detail is that the busted SD card did not prevent me from installing v2.3.5. Anyway, you win all the cookies.