The link to my interface is at this post…http://forum.pfsense.org/index.php/topic,35384.msg183476.html#msg183476

If you mean the firewall rule list, that's all in /usr/local/www/firewall_rules.php, the icons are printed around line 492.

As to what specific code you need to change to make them behave the way you want, that isn't quite so easy to answer. I'm not sure if there are line breaks, or if the table cell needs widened, or what. Could be any one of half a dozen or more things.

You could activate the SNMP service and have cacti poll the data, but otherwise there isn't a way to push them as-is.

You could have some kind of automated process that connected every so often and dumped the data, and then restore it into an rrd file on the cacti server, but that isn't ideal either.

Running a web server on a firewall is not a value-add, its a massive security hole.  What you propose is the definition of a "very bad idea"

Edit /etc/inc/auth.inc and change this line:

Though of course that won't survive a firmware update. On 2.0 the auth system is completely different so this isn't relevant there.

Probably not, since even the 80 column view spills over the page I doubt it would be added as a standard option.

You could always edit the source of that page and add -w 120 to the command it runs…

So I figured it out.  On the NAT rule I had to enable NAT reflection (the default setting is off).

Easy fix…

1)  Get access to the webGUI (after removing conflicting computer)
2)  Go back to the mac address box in the webGUI and blank it out.
3)  Click Save at bottom of page
4)  I had to reboot and the original mac address came back.

JH

/usr/local/www/themes/<theme name="">/</theme>

The suggested fix has been tested by me and applied in the latest 2.0 code.

awesome, thanks!

Thank you for your work !!!

Yes, this is very easy to do with pfSense.  You will want a firewall rule on the WAN interface which allows access to the port you're running your webGUI from the source IP in question.  Then you'll want to create a firewall rule on the LAN side (above the default allow rule) which blocks access to that same port from any source IP.

BUMP?

I'm having the same issue.

Did you manage to fix it?

For me, deactivating traffic shaper did the job. But this is not a solution :-(

Still searching for help.

then i suggest you do one of two things:

1. contact the person who was managing it before you
2. run nmap from a local machine using the command: nmap -p- -A 192.168.10.254
this may take some time, it will scan all tcp ports and try to connect to them to see what is running, look for a port that responds with:
"PortNumber/tcp open  ssl/http lighttpd"