| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
a dependency of p5-GD
|
| |
|
|
| |
tree now
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
obsolete ones
|
| |
|
|
| |
version is preferable. Should fix Ticket #4160.
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
future
Put the {} back around the rate-limit values without any whitespace.
{} around PHP variables in <<< text output to named.conf might get confused with {} text in namd.conf.
Added this comment in those areas to help prevent future problems.
// curly braces in the following <<<EOD are PHP {$variable}, not named.conf text { value; }
bump package version
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
The rate-limit option should not have values with {} and look like this:
rate-limit {
responses-per-second 15;
log-only yes;
};
|
| |\ |
|
| | | |
|
| | |
| |
| | |
addded code to fetch entries from virus log and push to "realtime" table
|
| | |
| |
| |
| | |
- adds a table to the tab "realtime" for virus log displaying
- corrected link to tab "antivirus"
|
| | |
| |
| | |
this writes a logfile when a virus was found
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \ |
|
| |/ / |
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| | |
Shared secrets longer than 31 characters will display garbage passwords.
Another cause of garbage passwords being logged is the secret being too long. Certain NAS boxes have limitations on the length of the secret and don't complain about it. FreeRADIUS is limited to 31 characters for the shared secret.
http://wiki.freeradius.org/guide/faq#Common-problems-and-their-solutions
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Make the zone type cases more consistent and add default cases.
|
| | |
| |
| |
| | |
This improves the readability of the generated named.conf file.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Often a zone configuration can be identical for LAN/local and WAN/pulic views, especially when using NAT reflection.
This change allows those zones to only be entered once in the configuration and then applied to both the local and public views.
The change converts the zone's 'view' field from a single selection to an array multiple selection. Since an old value of 'local' is the same as an array value with only one element for 'local', this change is backwards compatible with existing configurations. For that reason, I'm leaving the field name as 'view' rather than changing it to 'views'
When the zones are being added to the view clause, it will now check to see if the view is in the zone's view list rather than checking to see if it is a simple match before including the zone in the view. By setting the old varible $zoneview to the matching view from the list, the existing code needs very little change.
|
| | |
| |
| |
| |
| |
| | |
The update-policy statement allows the zone to specify, among other things, a key to be used for authorization of master zone updates
Add a checkbox and text field to add an update-policy statement to the zone configuration. When the update-policy statement is used, it replaces the allow-update statement.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Trim trailing ; from forwarders since ; is added when it is written to the config. Since it's a list of semi-colon separated values, users can accidently add a trailing ;
Only ensure the view folder exists if the zone is not a 'forward' zone since forward zones are only in named.conf and don't have a .DB file
Add allow-query statements to slave and redirect zones
Add allowquery and allowupdate fields to on_type_zone_changed()
Use isempty() on customoptions and forwarders to skip adding empty statements
Use isempty() instead of == '' on some statements
|
| | |
| |
| |
| |
| |
| |
| |
| | |
-4 and -6 restrict the resolver to use the IPv4 and IPv6 transports respectively. The option is needed for the cases such as when you have IPv6 enabled on the LAN, but the WAN does not support IPv6.
Add a list of choices with IPv4+IPv6 (default), IPv4 (only) and IPv6 (only)
If IPv4 is selected, -4 will be added to the command line
If IPv6 is selected, -6 will be added to the command line
|
| | |
| |
| |
| |
| |
| |
| | |
Add a supplemental checkbox to "Reverse Zone" which further qualifies the reverse zone as an IPv6 reverse zone.
The resulting zone name will be *.ipv6.arpa rather than *.ip-addr.arpa
This change was originally submitted by https://github.com/cuteredstorm/pfsense-packages/commit/2b4e8084a92c8e9936f1b2fdca8272d29217c20a for Bug #4553
|
| |/
|
|
|
|
| |
Add field similar to custom options, but for global settings. Rather than being added to the options{} clause, these settings are added directly to named.conf.
This allows the addition of items such as key{} and server{} clauses.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
notification flag tests
Bump package number to 0.3.5
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
