| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
setup, this solves the issues with Windows7/Vista client machines where elevated permissions are required by running OpenVPN as a service.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Check exists 'squid_resync' function.
|
| |
|
| |
Also check 'resync_squid' function.
|
| |
|
| |
Fix squid.inc include
|
| |
|
|
| |
The split function is deprecated in PHP 5.3. For this simple use, the explode function does the same thing.
http://forum.pfsense.org/index.php/topic,55187.0.html
|
| |
|
| |
Check squid.inc by system path's ( for 2.1 also )
|
| |
|
| |
Fix error 'Warning: require_once(squid.inc): failed to open stream: No such file or director'
|
| |
|
|
|
| |
The SQUIDGUARD_GUILOG_MAXCOUNT limit to 500 lines does not seem to work. The /var/squidGuard/log/squidGuard.log is increasing over this limit.
This patch rotates this file daily when logrotation is enabled and cuts this file after the last 1000 lines - the same as with /var/squidGuard/log/block.log
|
| |
|
|
|
|
|
|
| |
In squidguard_configurator.inc there is a daily rotation of the logile which cuts the last 1000 lines.
LOGSHOW_BUFSIZE limits this file again by the last 64KB. A file with ~1000 lines has size between 100KB and 300KB so I increased this buffer to 256KB to match these ~1000 lines.
I think this buffer size will work well even on low end systems, too.
Log rotation every day will do the rest.
|
| |
|
| |
In 2.1 a CPU time limit of 900 seconds is set for PHP scripts. Normal scripts used by the GUI should do their thing and finish. But lcdproc needs to run "forever" in the background.
|
| |
|
|
|
|
|
| |
squidguard: "url_rewrite_children" replaces "redirect_children" in squid 2.6 and newer versions. Increased default value up to 5.
http://www.squid-cache.org/Versions/v2/2.7/cfgman/url_rewrite_children.html
"redirector_bypass" is by default off which disallows to bypass ACLs.
http://www.squid-cache.org/Versions/v2/2.7/cfgman/redirector_bypass.html
|
| |\
| |
| | |
Fixed two issues with IP Ranges
|
| | |
| |
| | |
Small cleanup for readability
|
| | |
| |
| | |
Net masking math was off by 1
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Because all three cases (CIDR, IP Range, and Single IP Address) are always
tested, it is possible that more than one will have a positive match.
Examples:
172.16.0.0/12 matches both for CIDR and Individual IP Address
169.254.0.0-169.254.255.255 matches for both Address Range and Individual IP
By doing if, elseif, elseif instead of if, if, if testing, the later tests
will only be performed if the former tests fail. Because the Individual IP
Address test will return a result, even for CIDRs and IP Ranges, that test
has been moved to the end of the elseif list.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Several IP address ranges were being calculated improperly.
Examples:
10.0.0.0-10.255.255.255 became 160.0.0.0/8
65.113.241.0-65.113.241.255 became 130.227.226.0/24
72.165.61.0-72.165.61.255 became 145.74.122.0/24
The use of complicated string and regular expressions to calculate netmasks
has been replaced with basic and proper bit masking.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Dansguardian blacklist download fix for shallalist
|
| | | |
|
| | |
| |
| | |
The code did not work on nanobsd, due to $workdir templates being on a read-only mount point. The appropriate $client_install_exe needs to be written straight to $tempdir rather than first done in $workdir templates. And also we don't want to be writing to $workdir templates every time we make a client install package for someone.
|
| | | |
|
| | | |
|
| | |
| |
| | |
and default values, and some field description text.
|
| | | |
|
| | |
| |
| | |
Sorry guys - I missed out an equals sign here, the logic ended up only applying rules to the first interface, and not for others.
|
| | |
| |
| | |
typo
|
| | |
| |
| | |
added field description
|
| |\ \
| | |
| | | |
Update config/freeradius2/freeradiussync.xml
|
| | | |
| | |
| | |
| | | |
Added the option to edit the default XMLRPC timeout from the GUI
also added the option to activate or deactivate the servers that it is going to replicate to by adding a check mark to each server
|
| |\ \ \
| | | |
| | | | |
Update config/freeradius2/freeradius.inc
|
| | |/ /
| | |
| | |
| | | |
Added the option to edit the default XMLRPC timeout from the GUI
also added the option to activate or deactivate the servers that it is going to replicate to by adding a check mark to each server
|
| | | |
| | |
| | |
| | | |
If users move rules around in the GUI, the the rules for 1 interface can end up in separate blocks in config.xml. This causes pfBlocker code to put a set of pfBlocker rules before each separate block of rules for an interface, as they are processed out of config.xml.
The code here fixes that, ensuring that pfBlocker rules are only added once to an interface, the first time the interface is found in a rule.
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
http://forum.pfsense.org/index.php/topic,53809.msg287761.html#msg287761
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
than it fixes; Add a third Yealink variant.
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| | |
need pbi to be rebuild to get apache worker options working
|
