red blinking or not ... ?
-
This post is deleted! -
@furom On the 2100 the reset button resets to a default config.
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/factory-reset.html(on many other models it does a hardware reset and does not touch the config)
You can also use the Diagnostics menu to reset the config.
I've not tried partial restores, however, pfSense will show errors if aliases are invalid. It won't really break anything but those rules won't work until the aliases are valid. I've not had a problem with full restores. It will boot and install any missing packages.
-
@steveits Well... I am not so impressed as I once was...
Having reset it to red blink, I find that not only all apps I had installed before is still there, but worse, an IP from the LAN dhcp range I had before is lingering... And no, since the reset I have not been connected to any network, at all in fact, only to a laptop (that of course got its own address)...
On top of this I hit a snag with the "DNS Rebind Check"... It could well be mentioned on that nasty red page that one obvious trigger for this is having a SSL certificate installed, but the wrong hostname on pfSense. It took me a couple of hours and way too much of my evening. I am grateful for everything pfSense does and is, but sometimes things get screwed, this was one of those times. Easy things should never be too hard, for any reason. Easy as pie... ;)
-
@furom said in red blinking or not ... ?:
Having reset it to red blink, I find that not only all apps I had installed before is still there, but worse, an IP from the LAN dhcp range I had before is lingering... And no, since the reset I have not been connected to any network, at all in fact, only to a laptop (that of course got its own address)...
Better option is to always use the console.
-
@rcoleman-netgate said in red blinking or not ... ?:
@furom said in red blinking or not ... ?:
Having reset it to red blink, I find that not only all apps I had installed before is still there, but worse, an IP from the LAN dhcp range I had before is lingering... And no, since the reset I have not been connected to any network, at all in fact, only to a laptop (that of course got its own address)...
Better option is to always use the console.
Using the USBrecovery you mean? In that case, yes, I think I should've done that. I somehow thought the "red blink" was more thorough, but probably not
-
@furom No, using the console menu as detailed in the documentation here: https://docs.netgate.com/pfsense/en/latest/config/console-menu.html?highlight=console%20menu
-
Is that in 23.01 or 23.05-RC?
-
@stephenw10 said in red blinking or not ... ?:
Is that in 23.01 or 23.05-RC?
Still 23.01, I usually don't use RC's, but this is perhaps time to change that. Is there anything I should know before trying it?
-
@rcoleman-netgate said in red blinking or not ... ?:
@furom No, using the console menu as detailed in the documentation here: https://docs.netgate.com/pfsense/en/latest/config/console-menu.html?highlight=console%20menu
Ok. I do use it for usbrecovery flashing, and restoring a bad config change occasionally. What advantage would the factory reset through console have over reset button? I suppose result would be the same?
I don't mind using the console, in fact, I'd use it more if it for example allowed more granular backup restore.
I find the backup in pfSense a bit crude. It assumes all or just a single thing. I would have use for free selection into one file... -
@furom The menu works 100% of the time. The button on the back requires good timing.
-
@rcoleman-netgate said in red blinking or not ... ?:
@furom The menu works 100% of the time. The button on the back requires good timing.
Agreed. But don't get what I did wrong? Or do you just mean this as a general recommendation? If so I will of course
-
@furom it's a general recommendation because the back button requires timing and maintaining the button pressing for a period of time - the console is instantaneous.
-
This is an outstanding issue in 23.05: https://redmine.pfsense.org/issues/14378
But I have not seen it in 23.01. Yet.Steve
-
@stephenw10 said in red blinking or not ... ?:
This is an outstanding issue in 23.05: https://redmine.pfsense.org/issues/14378
But I have not seen it in 23.01. Yet.Steve
Ok, I suppose it's a matter of confirmation and recreation in lab.
in hope it would improve things I upgraded to 23.05 RC. Upgrade took a while to say the least, but no shown errors, but now I have another more severe issue though. I cannot by any means ssh to pfSense. Ports are open, ssh to anything else works fine, on same subnet... Prompt just hungs
-
@furom I'm almost lost for ideas... Have I "bricked" it sort of? It kinda works, but much isn't. If a reset won't really reset it fully, what will? A hammer? ;)
One would hope that the reset really wipes all and does a full format of all media, but parts of the system is not affected by that, is it?
-
After upgrading from 23.01 to 23.05?
You can still fully reset it using the 'factory default' option from either the console menu or the webgui.
You can always reinstall pfSense clean if you have to.
Steve
-
@stephenw10 said in red blinking or not ... ?:
After upgrading from 23.01 to 23.05?
You can still fully reset it using the 'factory default' option from either the console menu or the webgui.
You can always reinstall pfSense clean if you have to.
Steve
I have done that a couple of times already, but always end up in the same weggie-state. I havent restarted on 23.05 yet, I don't want to be negative, but don't think it'll do much good. If I do a usbrestore it will format everything not leaving anything behind right?
I'm almost at the state where I want to enter all data manually, from scratch... Just enough to get the basics up, switch, needed vlans etc. Is there any way I can print all running conf? or export it in a printable way?
SSH hung on 23.01 too after the weird dual-group-thing. So thought 23.05 might do it some good. Will wipe it again as soon as I know how to export all my config. Perhaps the xml is the best bet?
-
Yes, just back it up from the gui in Diag > Backup/Restore. That's why the config is all stored in on xml file.
