Errors After "Factory Default" Reset
-
Actually it should not reboot when done, as there should be no need to do so. If the new IP isn't fully applied, that is the problem.
-
Either way, at the end of the wizard it doesn't work properly with a custom IP for the LAN interface.
Now I am curious if it does this on a fresh, "new" install, and not a factory default. I honestly do not remember. I'll get the snapshot from today and do a fresh install to see if it mimics this behavior.
-
You are all lucky guys, since a long time now (tested with alix and full install on "real" hardware) resetting to factory defaults resulted every time in a completely broken machine, which doesn't boot till end but stalls somewhere and has to be reinstalled completely. :-(
That happens now since last summer.
Looking at the disk/cf-card with another freebsd showd that there was a completely broken config.xml which did that failing. Replacing the config.xml with a new "empty", say original config.xml, i could start the pfsense again. Maybe that helps out. -
I reset to factory defaults a lot, and I haven't had any problems in quite some time. I reset the config in VMs fairly often when testing, and there is zero difference in the factory reset on a VM from a full install. Unless you can provide more detail with specific errors and behaviors, it doesn't help.
-
I reset to factory defaults a lot, and I haven't had any problems in quite some time. I reset the config in VMs fairly often when testing, and there is zero difference in the factory reset on a VM from a full install. Unless you can provide more detail with specific errors and behaviors, it doesn't help.
was that at me or igor?
-
I didn't save a broken config, but mostly the config.xml is empty. Its a 0byte-file or the only xml-tag is the first one, followed by an opening tag. Nothing more. Sorry that i cannot help out more.
-
It was for igor
If you can't replicate it, and nobody else has noticed it, it may be something corrupt in your install or something else that was done. Seems fine to me.
-
I'll add one last thing since I think we are on the same page now.
A fresh install, clicking on the "Setup Wizard", specifying a custom IP (ex. 192.168.0.1/16) will do the same thing as the "Factory Default"; the difference is the wizard starts automatically after a factory default. (and by wizard I mean the webConfigurator, not the local console interface/vlan assignments)
Dashboard shows 192.168.1.1, Interfaces->LAN shows 192.168.0.1. Web Interface is accessible on 192.168.1.1, but not 192.168.0.1.
-
and one last thing…i hope (lol)
the last page of the wizard, the "Finished Reloading" page, there is a link that says something like
"Click here to continue on with the webConfigurator" or something like that. the link points to the default IP instead of the new IP given in the wizard.cheers.
-
Some notes to add as I was testing out our production settings on the latest snapshot today.
It seems this bug is only related to the Setup Wizard. Entering everything outside of the wizard things work as expected (without reboots)
-
https://github.com/bsdperimeter/pfsense/commit/44a4d54dd367ff80de93eb63ddebd2aa88c7554b
-
I did a test with a completely new install, restored my config, installed packages and then resetted to factory defaults: pfsense booted and hangs (last message was that em0 and em1 changed state to up). Rebooted twice but it hangs at the same point. Maybe because of the installed packages? I think i'll test that without packages to get that clear. Thats just for your info. Thanks
-
Thanks jimp :)
A nice, easy fix.
