2.1.5 to 2.2 BETA
-
other minor aesthetic bug i noticed in serial console was, after finishing boot, it usually lists all the interfaces with their ips and then the serial console option list but misses a empty line between the interface list and console options
That blank line was removed in this commit:
https://github.com/pfsense/pfsense/commit/a3cc8dcc600d105d73eb4729c32433d40d72cab7
I have no idea if it was really intentional - 2 (echo "") were needed to make a blank line, the first one just puts a new line at the end of the rc.banner output and list of interfaces, the 2nd one made the blank line. -
Just wondering what I will see using the Firmware Auto Update URL? Will it simply download and install the upgrade and just reboot into the GUI where I would just login and go? Are any settings/packages lost? Do I need to uninstall any packages before the upgrade? Sorry for all the questions and thanks for your help.
It runs like any normal upgrade - download and install of base firmware image, reboot, download and (re)install all packages.
You should be able to just do it - make a backup first, other than that no special preparation needed. -
Just wondering what I will see using the Firmware Auto Update URL? Will it simply download and install the upgrade and just reboot into the GUI where I would just login and go? Are any settings/packages lost? Do I need to uninstall any packages before the upgrade? Sorry for all the questions and thanks for your help.
It runs like any normal upgrade - download and install of base firmware image, reboot, download and (re)install all packages.
You should be able to just do it - make a backup first, other than that no special preparation needed.One last question. How large is/are the download files? I have 15Mbps down and would like to have an idea how long the whole process might take (Have to keep the wife happy lol and she wll be out for awhile).
Thanks!
-
http://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_HEAD/updates/?C=M;O=D
76MB for the nanoBSD upgrade
86MB for the full install upgradeInternet still works during the download. (Of course, slowed by the fact that pfSense is downloading in parallel with users) It is only the reboot and package install time that really takes you off-line.
-
http://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_HEAD/updates/?C=M;O=D
76MB for the nanoBSD upgrade
86MB for the full install upgradeInternet still works during the download. (Of course, slowed by the fact that pfSense is downloading in parallel with users) It is only the reboot and package install time that really takes you off-line.
Does the install automatically detect the install type? I have a full install amd64.
Update: The installation was flawless and I am very happy. The new firmware seems snappier. My first impression :) :) :)!
Update2 - To show my respect, support and appreciation for this project, I just became a Gold Member.
Cheers!
-
other minor aesthetic bug i noticed in serial console was, after finishing boot, it usually lists all the interfaces with their ips and then the serial console option list but misses a empty line between the interface list and console options
That blank line was removed in this commit:
https://github.com/pfsense/pfsense/commit/a3cc8dcc600d105d73eb4729c32433d40d72cab7
I have no idea if it was really intentional - 2 (echo "") were needed to make a blank line, the first one just puts a new line at the end of the rc.banner output and list of interfaces, the 2nd one made the blank line.well the blank lines just made it look more pretty and well formated, i vote for it to return :)
-
other issues im facing as of now is the SSH daemon wont start at all, on reboot i get announcement that ssh keys will be created but then when i goto services the daemon wont start at all
-
some more bugs under system->advanced->System Tunables
the list shows the entries with just default without the actual default value and that's causing sysctl errors in the boot process saying non zero values and im guessing if u remove some values it doesnt restore the default list which is present on a fresh install -
some more bugs under system->advanced->System Tunables
the list shows the entries with just default without the actual default value and that's causing sysctl errors in the boot process saying non zero values and im guessing if u remove some values it doesnt restore the default list which is present on a fresh installi figured out what the issue with this, in older pfsense the default entries r stored in config with value as default which when upgraded make the system think to take value as default and thats y the non zero error, what i did is delete those entries and rebooted and the newer pfsense recreated the same with their actual default values rather than just showing and storing default in the config
-
Upgraded to 2.2-BETA on the weekend and have received this crash message:
Crash report details:
PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 253I submitted the report but not sure if there is something I can do to fix the problem.
-
Upgraded to 2.2-BETA on the weekend and have received this crash message:
Crash report details:
PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 253I submitted the report but not sure if there is something I can do to fix the problem.
Hi wbennett77,
Do you get this error often? Is it a particular list that is failing?
You can suppress the error by adding an "@" in line 253 as follows :
$url_list= @gzfile($row['url']);
-
Upgraded to 2.2-BETA on the weekend and have received this crash message:
Crash report details:
PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 253I submitted the report but not sure if there is something I can do to fix the problem.
Hi wbennett77,
Do you get this error often? Is it a particular list that is failing?
You can suppress the error by adding an "@" in line 253 as follows :
$url_list= @gzfile($row['url']);
I get the error constantly. Anytime I log in to the dashboard the error appears. Anytime I go to one of the other menu areas and then come back to the dashboard the error appears. I have tried reinstalling Pfblocker with no change. Pfblocker has also disabled itself a couple of times and on other occasions a certain list becomes disabled. This would seem to be an error that is causing problems with the package.
I am curious. I am using a couple of lists from I-Blocklist in the CIDR file format and gz archive format. Would this have any effect? This was all working in 2.15.
Thanks!
-
This should really be a separate topic!
Look in your config for $config['installedpackages']['pfblockerlists']['config'] (Diagnostics->Edit File, /cf/conf/config.xml - look for pfblockerlists and config under that and row and url under that. config.xml is in XML format.) Those should point to some files. In the file/s there will be loads of URLs…
I guess one of those files has a huge number of entries and it is exploding PHP memory.