| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Use system_hosts_entries to generate unbound host_entries.conf
|
|
|
|
| |
Read local items from system_hosts_local_entries()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) util.inc - add parameter to get_staticroutes() so the caller can
choose to see all static routes or only the ones that are currently
enabled.
2) filter.inc - just process enabled static routes when making direct
networks list, tonathosts etc.
3) services.inc - only include enabled static routes when making confogs
for DHCP(6) Relay.
4) unbound.inc - only include enable static routes in
unbound_acls_config
5) rc.newroutedns - only trigger if there is an enabled static route.
Note: GUI validation has been left as-is. e.g. in system_gateways we don
not allow to delete a gateway if there is a disabled static route using
it... If people want to delete "higher level" stuff, then they need to
first delete the disabled static route(s). Otherwise it will get rather
"risky" having disabled static routes in the config that refer to
gateways that no longer exist, or have a subnet range that now matches a
local interafce or...
(cherry picked from commit cf08b49e20810a0aa953561892b1d5bee353957e)
|
|
|
|
|
|
| |
(Feature #6914)
(cherry picked from commit 6a827f6959fc34972e532516a6a414e1cdf87714)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
unbound's local-data. Ticket #6064"
This reverts commit cde0ef17a60cffa4a54f3ab4922b77bc0447d068.
|
| |
|
| |
|
|
|
|
| |
In the Unbound documentation, it is noted that setting "outgoing-num-tcp" to "0" disables TCP queries. In testing I noticed that although I could select & save a value of "0" in the Unbound Advanced Config, the actual value written to /var/unbound/unbound.conf was still the default "10". Apparently in PHP, a value of "0" still tests "false" for !empty(). Changing the test to isset() seems to fix the issue.
|
| |
|
|
|
|
| |
Wrap var in string with braces.
|
|
|
|
| |
Protect against breaking the system; check for valid unbound local zone type rather than just the setting existence.
|
| |
|
|
|
|
|
|
| |
Generate a complete set of test conf files in /var/unbound/test subdir when doing the validation of the tentative config that is being saved.
This avoids any dependency on any of the "real" files already existing in /var/unbound and also avoids the chance of overwriting a live file that is currently in use by the running unbound.
/var/unbound/test is removed once the validation has been done.
The real unbound conf files are created in /var/unbound like they always were after the user presses apply.
|
|
|
|
| |
was the reason they were added, it was never finished and it's not being used
|
|
|
|
| |
Expose system domain unbound local-zone type to be configurable.
|
| |
|
|
|
|
| |
#4021
|
| |
|
|
|
|
|
|
| |
The stuff generated by unbound_statistics() goes into unbound.conf
It had got separated out and was going nowhere. This puts the behavior back the way it was yesterday.
Note: There is a separate issue about this because the UI has no place to actually select the statistics settings. There is some upgrade code that looks like it was converting statistics settings from the old Unbound package into custom commands in the integrated Unbound. So it looks like the unbound_statistics() function can/should be removed???
|
|
|
| |
to the correct place based on $g setting.
|
|
|
|
| |
writing the actual file and a syntax check can be run. Rearrange services_unbound.php to wait until input checking is complete before saving things to global config and run syntax check as part of input checking. Implements #4411.
|
|
|
|
| |
unbound-anchor runs otherwise it will fail and unbound will fail to start. fsync the file after writing to prevent the problem. Ticket #5334
|
|
|