Settings blown away after restart
-
@Art:
Believe it or not our ISP fixes the MAC address of the box connected and every time you decide to change the hardware you need to call and inform them of changes.
That's the least of the problems. You can spoof any MAC address you need.
-
@Art:
Believe it or not our ISP fixes the MAC address of the box connected and every time you decide to change the hardware you need to call and inform them of changes.
That's the least of the problems. You can spoof any MAC address you need.
Thanks a lot.
I cannot find upgrade_log. I enabled SSH, used Putty to connect to the box and was able to find config.xml in conf but there was no upgrade_log. I also looked for upgrade_log in var/log. I can find some log files but the upgrade_log is not there.
-
I already posted where the log is.
$ ls -l /conf/upgrade_log.txt -rw-r--r-- 1 root wheel 769795 Mar 19 17:19 /conf/upgrade_log.txtSame thing, nanobsd or full install.
-
I already posted where the log is.
$ ls -l /conf/upgrade_log.txt -rw-r--r-- 1 root wheel 769795 Mar 19 17:19 /conf/upgrade_log.txtSame thing, nanobsd or full install.
In /conf/ I can find only the "backup" and the config.xml
-
"setting blown away after restart"
Well - Thats one way to become expert (-:
-
I have similar issue…..settings didn't go away, but my HAVP will go away.....leaving only a "shell" inside pfSense menu.
i.e. Everytime I reboot my machine, the group setting (HAVP group) and some executables are gone, I have no clue at all.... -
Have you tried a wipe, reinstall and reconfiguration by hand?
-
Not yet, but going to do so (since mine is a new box, still testing)
But does it matter with nanobsd? I have only 1G ram + 1G CF card, not sure if this is the issue (maybe disk full so that nothing can be sync?) -
Maybe - There are some guys here with more experience than me in that department.
-
Are you able to create a file in /conf at all? Perhaps your boot media is damaged to the extent that it's permanently read-only.
If not that then it's not even starting to upgrade so check the main system logs for errors.Steve
-
I tried to create a file in /conf and I was able to create it. I will have a look at system log once again.
-
Here is my solution. Purchased a new 60 GB ssd drive, removed the old one, installed the new drive, installed the latest version of pfsense from USB, restored settings and was ready in 1 hour and 10 minutes.
-
What you did is very sensible. Although, you have denied me the entertainment I normally get watching people jump through crazy hoops for weeks trying to save a couple of bucks. :(
