So…what's the verdict on 2.3?
-
Well, at least the color-theme of the old interface would be nice to be back - this all-white and all-black are the two extremes. The old one was much more human-friendly - I'm talking about the colors here.
I think the main issue with the new GUI for many people is the color scheme - dark gray text on a light gray background is just a poor design and the vertical white space probably does help on the mobile view but it's not good on a large monitor. I'm sure that all this will get sorted out eventually.
FYI - I'm finding that playing with the monitor brightness and contrast controls does help.
-
Well, at least the color-theme of the old interface would be nice to be back - this all-white and all-black are the two extremes. The old one was much more human-friendly - I'm talking about the colors here.
I think the main issue with the new GUI for many people is the color scheme - dark gray text on a light gray background is just a poor design and the vertical white space probably does help on the mobile view but it's not good on a large monitor. I'm sure that all this will get sorted out eventually.
FYI - I'm finding that playing with the monitor brightness and contrast controls does help.
System > General Setup, change to the Dark theme. Some people much prefer that, I find it difficult to read in most cases, whereas the light theme reads perfectly for me.
Anyone is free to make new CSS themes, it's pretty easy to do now.
-
I am having several issues and will be rolling back to the last version. I love the new lay out. But, I have had several crash reports in the last few days. Never had an issue with the last version. But, 2.3 looks promising. I'm relitvly new to pfSense about 8 months now. Haven't had any problems until now. I'm guessing a few tweaks here and there and 2.3.1 will be just fine.
I too have had several crash reports since the upgrade, and did not have any with the previous versions. They don't seem to affect functionality and don't cause a reboot.
I have had an issue with Gateway monitoring indicating that one of my gateways was down, even though I could ping the gateway uses pfSenses ping and from a workstation. Workaround was to disable Hardware Checksum Offload. However, I try the payload size fix. I had tried editing and re-saving the Gateway before.
Also had this https://forum.pfsense.org/index.php?topic=110438.0
No issue with Squid
Had a notification re an alias. But this was resolved after editing the alias and the relevant rules.
Otherwise seems to be pretty good
-
They don't require repeated attempts at creating a firewall rule - at least not like I often do.
The mod/apply/test cycle with the new ui requires a lot more steps.How so?
Is there a toggle somewhere I missed to add the Clear and Filter buttons back to more or less where they were?
With the Rule as a column, and entries limited to 20, it wasn't too bad to keep refreshing as you made changes.
The new layout is kind of awkward.
To which screen specifically? The logs? System > General Setup, check "Log Filter" and "Manage Log" and it will show the panels on the page. Though if you only want to see if traffic is hitting a rule, just look at the hit counters on the firewall rule list now.
I'm not sure if the change to the way var usage is displayed would have save me from myself earlier.
The real problem for me in 2.2.6 was that I wasn't paying attention - and 3.4mb is NOT enough for /var/run when a crash dump lands there.
The disk usage display for /var/run has been the same since 2.2.x. It's random that the php core ended up there, it doesn't always land there if it crashes.
Given that I use squid at that site, 512MB isn't nearly enough, though I suppose I can buy a little time by dialing the cache back.
On a full install /var/run is a tiny RAM disk that only holds PID files and some other small flag files, it doesn't contain data. The squid cache is in /var, which is typically a part of / unless you have done a custom install or activated the option for /var in RAM.
Is there a non destructive way to move var back to the hd?
See above, /var/run/ is not all of /var/ – If you did activate /var in RAM, it's under System > Advanced, Miscellaneous, and would not have changed automatically.
No - I get that - now - I just jumped the gun and set /var to a ram drive because I misread the screens and was in a hurry.
Now I have to blow it out again because I was also in a hurry on the reinstall - reset to factory defaults didn't seem to clear the whole config
-
Thought I've never had issues with the updates in the past, this one has been nothing but problems. Random hardware lockups, pfBlockNG crashes, etc. (See pfBlockerNg issue here https://forum.pfsense.org/index.php?topic=110458.0)
-
Thought I've never had issues with the updates in the past, this one has been nothing but problems. Random hardware lockups, pfBlockNG crashes, etc. (See pfBlockerNg issue here https://forum.pfsense.org/index.php?topic=110458.0)
If you submit that crash to the devs for pfBlockerNG, I may not see it… If you have any future pfBlockerNG errors, send me a PM with that error...
I see the issue with the De-Install script, and plan on submitting a Pull request today to fix that...
-
I've noticed the cron's for Snort are also not removed with the package.
-
I've noticed the cron's for Snort are also not removed with the package.
I will check into this. I am working on another Snort problem right now and can incorporate any needed fix into the upcoming release. The package makes system calls to remove cron tasks, but that process may have changed under Bootstrap. The entire package install/uninstall process got changed with the move to pkg and away from the old XMLRPC stuff. Just a guess since I have not investigated yet, but it could be some of the uninstall triggers us package maintainers formerly depended upon may not be happening the same as they used to.
Bill
-
I've manually removed the packages, cron, and anything I can find from the pfSense config file and am going to see if that solves my problems. Is there anything I can do to remove any files that might be lingering from Snort of pfBlockerNG? I plan to try to reinstall the packages at some point but want to ensure everything is re-installed.
-
I've manually removed the packages, cron, and anything I can find from the pfSense config file and am going to see if that solves my problems. Is there anything I can do to remove any files that might be lingering from Snort of pfBlockerNG? I plan to try to reinstall the packages at some point but want to ensure everything is re-installed.
Other than consume a tiny bit of disk space, the files can't really cause any issues. The cron tasks will generate errors because they will attempt to execute files that may have been removed. You can manually remove the cron tasks using the cron package.
Bill
-
Thank you. I'm not worried about the disk space; just wanted to ensure when I re-install, everything will be reinstalled.
I've already cleaned out the cron tasks.
