I personally use these colors

$colortrafficup = array("0000ff", "000000");  /* mod */ $colortrafficdown = array("de0202", "00c000");  /* mod */ $colortraffic95 = array("ece904", "808080" );  /* mod */ $colorpacketsup = array("0000ff", "000000");  /* mod */ $colorpacketsdown = array("de0202", "00c000");  /* mod */ $colorstates = array('ece904','757575','0000ff','00c000','de0202');  /* mod */ $colorprocessor = array('ece904','00c000','0000ff','ff0000','808080','000000'); /* mod */ $colormemory = array('c00000','00c000','0000ff','ffff00','808080','000000'); /* mod */ $colorqueuesup = array('666666','00ff00','ff0000','0000ff','ff8000','9f00ff','ff00ff','00dfff','ffdf00'); /* mod */ $colorqueuesdown = array('666666','000080','008000','800000','804000','500080','800080','007080','807000'); /* mod */ $colorqueuesdropup = array('666666','00ff00','ff0000','0000ff','ff8000','9f00ff','ff00ff','00dfff','ffdf00'); /* mod */ $colorqueuesdropdown = array('666666','000080','008000','800000','804000','500080','800080','007080','807000'); /* mod */ $colorqualityrtt = array('ff0000','ece904','808080','0000ff','00c000','000000'); /* mod */ $colorqualityloss = "de0202"; /* mod */ $colorwireless = array('990000','a83c3c','b36666'); $colorspamdtime = array('DDDDFF', 'AAAAFF', 'DDDDFF', '000066'); $colorspamdconn = array('00AA00BB', 'FFFFFFFF', '00660088', 'FFFFFF88', '006600'); $colorvpnusers = array('de0202'); /* mod */ $colorcaptiveportalusers = array("000000"); /* mod */

Thank you! I changed the file manually, and it is working flawlessly!

There is no config indicator saying you're working on a "backup" or "master" since it's also possible to chain multiple things together… a single unit doesn't have a way to show that it's going to be receiving config updates from another.

The easiest fix for this is to:
1. Set different hostnames on each so you can identify them that way
2. Set each box to a different theme, so it's obvious they are different at a glance.

I've thought about that, and I just opened the XML file after I stored it. But that basically means the same reassignment of gateway rules as I see it, since the OPTx changes. LAN1 is now opt5, LAN2 is opt1.

Any idea how to change that gracefully? Or is it as simple as moving the definition to where I want it in the XML file?

I'm experiencing this issue as well.  Embedded amd64 VGA install, 2.1 snapshots.  Hardware's a dual core atom (d2500), 4gig ram, dual onboard intel gigabit nics.  Would be nice if someone could point in the direction of a solution

Bump..

Nobody knows a way to get data? :/

Thanks!… :D

@jeffpfse:

Also, for the restricted user, will they still be able to see all the menu options even though they cannot access them, or will only the ones that they have access to be displayed?

On 2.1 it shows only menus user has access to.

So I woke up a bit more and connected a keyboard and monitor to it, I selected to enable ssh but it's still not responding on either ssh or webGUI.

On a 32 bit OS that comes from a 32 bit counter, that's what happens when the counter wraps.

That is probably a little bug in there.

To remove it, make a backup of your config (Diag > Backup/Restore) edit it out and then restore it.

You can open a bug report for that at http://redmine.pfsense.org

Hi, thanks for looking at that

…probably be best to do it through something other than the Edit File page...

;D ;D ;D

Added 3 lines using vi in console session. Confirmed working this end on x64 and x86 2.0.1-RELEASE.

Thank you for pfsense!

Rob

Hi Again…

Just updated to newest today Chrome Version 21.0.1180.89 Kubuntu 12.4 still have the bug...

/Michael

Some sort of reverse proxy could do that, based off of hostname/url in some way. I know Varnish and HAproxy can do it, just setup your own internal/fake domain (or a real one, if you want) and then access the various things via hostnames you create, and let the proxy sort out how best to route the request.

@McFuzz:

Hi all,

I recently started experiencing a weird issue pertaining to logging in to the UI from a WAN connection (i.e. hitting the external address of the firewall). When I try to, browsers indicate that a secure connection could not be made - specifically, this is what Chrome (amongst others) spits out:

Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.

A reboot of pfSense appears to fix the issue, but only temporarily. Restarting the webUI does not resolve it. For what its worth - I can access it just fine from within the LAN.

Any ideas?

I'm running 2.0.1 if it matters…

Thanks!

I too am encountering this issue and it's making me crazy.  Reading forums trying to find a clue.  I can access all of my pfsense functionality but ONLY from my LAN behind the PF box.  In fact, it is even allowing me to RDP from the internet into one of my PCs behind the box to access PF webGUI.  How strange is that?

If it works, feel free to fork, edit, and submit a pull request in github.

https://github.com/bsdperimeter/pfsense/

EasyRule automatically does a filter reload when called.