When can we expect a new 2.7 snapshot !?
-
Hmm, you should not be seeing that in 2.7 or 22.05 snapshots. It's fairly easy to test by manually loading the rule set at the command line with 'time' as shown on the bug there.
Steve
-
Stephen, I did not explicitly test this, it was just what I noticed during changes I made.
I have been tuning my rule sets significantly, since the actual 2.7 version seems to work fine (in opposite to last month version) and during that process I noticed a few times, that my PC was loosing its connection with my all-in-one printer. Something I normally only observe when I restart the router.
Also note that the GUI is in frequently terribly unresponsive, especially during logon and when it has to display the (complex) dashboard. My feeling is that the routing performance itself is OK.
Note that I have split my >small< network in 15 vlans, for security and testing reasons. Be aware I am using a two core four threads G4620 cpu with 8 GB of RAM.
What ever, I will pay special attention to this potential issue when making rule changes.
-
Even with a large ruleset that bug only adds a few seconds. It's easy to test just run at the command line:
time pfctl -f /tmp/rules.debugIt should load in a fraction of a second.
It's probably not that you're hitting though, simply opening the dashboard does not reload the filter. It sounds more like something timing out. Something on the dashboard trying and failing to reach some data.
Steve
-
No that is not what I intended to say! The disconnection errors I think I met a couple of times where related with rule changes. Nothing to do with the dashboard!
As promised I will pay extra attention to that potential problem
-
@stephenw10 said in When can we expect a new 2.7 snapshot !?:
something timing out. Something on the dashboard trying and failing to reach some data.
I suffering with the same issue a long time.
Dashboard - by determination are place where results of analytics in form of charts AND/OR current states in real-time represent.
So, logically, we may expect there are some amount (in several cases - a lot of) of measurement/calculations and request to databases would be made before Dashboard able to display most of their widgets.This situation remind me times 10 years age when iPhone 3/3S come with multitasking and Dashboard and Devs take decision to update info for each widget in background to be able immediately/as fast as possible display the Dashboard.
The same decision was made by Google ADs Dashboard (God bless, a lot of asynchronous frameworks exists already at that time!).Why Netgate not pay attention to this and only make “Not look for pfSense update on Dashboard” checkbox to speed up the Dashboard loading?
Because of rare using? If so, I sure that the worst usability tool/feature You made, the less peoples use it. (Again to the example: after Apple make useful UI for conference calling, operators see exponential increasing of this feature using by users, but before iPhone decades of years this functionality exist and only small fraction of users use it!)As a compromise solution may be ability to make several tabs in Dashboard, where each have widgets grouped around one point of view.
(For example,
one of tab may content Interface status, Gaitway status, ping/jitter graphics, small amount of in/out statistics for each interface,
another tab may content traffic graphs for each lan with small common stat
third tab - whole system info, used resources and running daemons
four tab - ARP and DHCP tables) -
Multiple dashboard layouts is an interesting idea. Or at least, an option for a "blank" landing page on initial login (would load instantly) and only show the full dashboard + widgets if the user specifically navigates to Status -> Dashboard.
-
@luckman212 said in When can we expect a new 2.7 snapshot !?:
Multiple dashboard layouts is an interesting idea. Or at least, an option for a "blank" landing page on initial login (would load instantly) and only show the full dashboard + widgets if the user specifically navigates to Status -> Dashboard.
Need to point that delay in Dashboard loading is not a such problem.
The main problem are that pfSense used by several group of users, and each group NEED AND PREFER own dataset on Dasboard, moreover, during the obtaining experience with pfSense using, this NEEDS would be changed.
-
Each user can already have their own custom dashboard. Enable per-user custom settings under System > User Manager when editing an account.
While not as convenient as multiple tabs, one could log out/back in with different users to get different views.
Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!
Need help fast? Netgate Global Support!
Do not Chat/PM for help!
-
@jimp said in When can we expect a new 2.7 snapshot !?:
Each user can already have their own custom dashboard. Enable per-user custom settings under System > User Manager when editing an account.
Thank You for reply!
When I wrote different group of users have different needs I mean that Information on a Dashboard must be reflect the needs of user and his experience level.
While not as convenient as multiple tabs, one could log out/back in with different users to get different views.
?
Why need to doing simple things so complicated? This looks like You need to go thru several screens in menu to switch Your iPhone to vibrate-only mode, or need to go thru 5-6 screens to change ISO in Your digital camera...At 90+% cases SysAdmin are only one person who manage pfSense. No such needs to producing 2-3 extra user to be flexible in everyday task...
-
Ok, is that possible to implement multitabs Dashboard conception in pfSense theme?
