The traffic graphs are in the process of being redone with nvd3 so that the styling can stay within the stylesheets.

Nice work, but this won't end up in the main repo because of the way it was (read:  had to be) implemented.

Glad that was it. It could really use a better message in that case, rather than looking like it was successful and leaving you wondering what the deal is.

worked like a charms!! thank you!!

I made some tests and I encoutered very strange issue :

Connecting from Lan or Wan on a Linux platform it's not working with Chrome but it's working with Firefox

Adding a second nav tier is a discussion worthy of another thread, although the implementation could be somewhat involved. It would still be nice to have the thought exercise of what a potential 2-tier nav could like like (without confusing existing users).

edit: Another option is to see if there are any pages that can logically be combined into a new page that page has them as tabs instead. For example, moving Status > DHCPv6 Leases into Status > DHCP Leases and creating v4 and v6 tabs (I have not idea how hard or what implications that might have)

Thanks luckman, clearing the cache solved the problem

Yes, clearing the cache made it working again…
Poor of me.
I mark the thread as solved.

@Tracktor:

try remount the root partition as read-write
mount -u /
and role back…

I just read your reply. I end up installing a new one and restoring latest backup.

I'll take note of your suggestion, thanks!

kind regards,

Linux Mint 17.1.  I just ran an update and it did update to 46 now (I still can't believe how fast they're pushing entire new versions now, 46 lol.. just crazy).  I don't run it every single day, it gets a little tedious, so I do it whenever I don't have much going on and can reboot. (some updates want to reboot).

bug report created: https://redmine.pfsense.org/issues/6378

I see that it kind of works, but it still creates a lot of double typing. When you create alias of any type, you hide the original value - like IP in my case (but same goes for ports!). So if you see a log entry of a certain IP and wonder where/what host it is, you can't just hoover over the alias-group to quickly isolate/find the host. Alias is often a good way to help find Host Alias->IP, but the interface ignores the other way, IP->Host alias.

The hoover should contain the alias value as well, like IP, port or whatever the original value is. A work-around is to enter the IP in the alias, but this creates a possible difference in real value vs textual description and a lot of extra work/confusion.

Hope this is fixed in later versions.

Another usefull feature developers could implement, is the number of referenced IP, hosts etc. in the fw rules, from Aliases. This is how Fortigate does it (if an alias is used three times, it has a link with number 3 that leads to fw-rules).

Is this fixed or still present?

Is it just when using NAT it occours or is it for all rules?

Curious, i've got a similar issue (but i found that is related to a particular configuration on Suricata). But from the package list you provide i can see that you're not using it…right?
What is the hardware of the NIC you use?

@luckman212:

Thanks for this!! Just found this and am using it now.  Like it very much.  8) The other default themes just have way too much whitespace for me.

I use the dark theme to eliminate the whitespace.  ;)

Another option would be to wear sunglasses.  8)

@virgiliomi:

Another reason why I zoom out 10%… so that when I snap to one side or the other, I still get two columns on the dashboard.

That's cheating and not everyone what's to accelerate their becoming a Magnivision customer.  8)  Also it's inconvenient if it affects other browser windows and has to be changed back and fourth frequently.

They seems fine in size to me. I have 4 columns and it all fits nicely on my monitor. Could just be an issue on a small monitor / resolution.

I just wish they matched the Dark Theme, they are white and don't match at all…

The config upgrade process modifies the quality RRD file to add the RTTsd. Did you restore only the RRD data? In that case it won't go through the config upgrade process and hence won't update the quality RRD to have the RTTsd.

If you edit your config with viconfig and back-rev it to version 14.5, then go to Diag>Command and in the PHP Execute box, run:

It'll go through that upgrade process. It'll also run through all the other config upgrade steps again, but that should be safe as it won't make any changes that were already done or aren't necessary.