Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Ful country code and encoding was necessary for pt_BR.ISO8859-1, (Brazilian Portuguese), and since it was the first translation, I followed the same format.
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>

fix menu collapses when select DHCP Server interfaces tab 

Services -> DHCP Server

(legacy) it feels kind of duplicate, but to avoid too much changes on how it works now let's keep the behavior approx. the same. (part 2)

missing prototype.js in protochart directory

This reverts commit 92a5f77a.
This reverts commit 681f654c.

Submitted by: Jakob Strebel
Edited by: franco@

(proxy) add transparant proxy option to squid including a template for the firewall_nat rules to forward traffic to it

(legacy/ldap) allow local users to be created with random password, solves errors in log when linking groups and leaves the possibility open to allow shell login using ldap in a later stage (currently not supported)

for example, if squid needs some directories to exists before initial run after boot, it could set this in /etc/rc.d.conf/squid

squid_opnsense_bootup_run="/usr/local/opnsense/scripts/proxy/setup.sh"

which effectively results in setup.sh being started followed by the normal service squid start

disadvantage of this, both the service template and the rc system needed to be aware of the setup.
advantage, all services which don't need special preperation are configured as they would be on normal FreeBSD

`block quick' creates a chain-reaction that requires `pass quick' for
loopback traffic, even though we have non-quick loopback pass rules
below.  If `quick' ought to be used, non-quick should be removed
completely, but that is beyond the scope of this fix.

For now, rather pass all IPv6 traffic on the looback device as opposed
to passing all IPv6 traffic with an IPv6 loopback address.

While blocking IPv6 in this case is a good start, loopback traffic
from internal to internal should never be blocked as some deamons
like squid use it to probe and/or communicate.