Hi, I fixed this another way.  Here is my post about this:

http://forum.pfsense.org/index.php/topic,10975.0.html

(No idea if editing the all.css file for Nervecenter will fix the issue as I don't have Opera but you could always give it a go)

If you want the exact steps, here they are:

1 - Go to Diagnostic: Edit file (you should still be able to click this one)
2 - In the Save/Load from path box, type in /usr/local/www/themes/metallic/all.css and click Load
3 - Scroll down until the / Style the List / section.
4 - Change the line that reads width: 800px; to be width: 802px; and click Save
5 - Clear your FF cache and reload the pfSense page to check it worked

The ticker is only there if you have events.
And only errors count as event.

The logout-button is the x on the top right-side of your browser.
If you have issues with stored passwords: configure your browser correctly.

I have seen where people can modify the prompt for username and password when logging on to state additional info.  Maybe something like this.  Where in pfsense to set this I do not know.

untitled.PNG
untitled.PNG_thumb

1.3 already has this feature. (usermanager)

Got it!

It's in the etc/rc.* files

New footer to celebrate going over to FreeBSD 7

footer.png
footer.png_thumb

i fugured it out i had to set the lan ip address

The graphs are only generated when  viewing the webpage.

Alternatively you can use curl and download the images directly onto your webserver by linking to the status_rrd_graph_img.php

The picture clearly says, 1 minute average for the 16 hour graph and 5 minute average for the 2 days graph.

It's exactly what it says, the amount of traffic over 5 minutes, then divided by 5 minutes. Which is not the same as 1 minute averages ofcourse.

To enable a larger LAN MTU (jumbo Frames) in the absence of a menu option can I just add the following to the interface section of the config file? (driver permitting)

<lan><if>re1</if>
        <mtu>9000</mtu>
<ipaddr>192.168.100.254</ipaddr>
<subnet>24</subnet>
<media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<bridge><disableftpproxy></disableftpproxy></bridge></mediaopt></media></lan>
<wan><if>ste0</if>
<mtu><blockpriv><media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<spoofmac><disableftpproxy><ipaddr>dhcp</ipaddr>
<dhcphostname></dhcphostname></disableftpproxy></spoofmac></mediaopt></media></blockpriv></mtu></wan>

There are a ton of bindings and customizations in the way things start up, the way things are configured in FreeBSD, etc. You'd need to either use our whole build system (which is a real pain), or write your own init and make a lot of customizations to the pfSense code. Might be better to start from m0n0wall depending on what you want to do. Or if it's something related to pfSense, it would likely make the most sense to just create a package and avoid the pain and many, many hours that go into creating your own system like this from scratch.

Found my answer when i did some research on the forum.

http://forum.pfsense.org/index.php/topic,4365.msg26796.html#msg26796

I've seen this happen before on BSD systems where realtek interfaces had issues staying on the network unless traffic was always flowing through them.  In that case, it was a driver issue.  What kind of card are you using?

yes, i could ping the monitor ip through wan 2, and no info in sistem logs.

but i works now, for i  dont know somehow.

thanx for your concern….