This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
"Warning
Below table contains the options to manually set listening and outbound interfaces, the recommended setting for both is "All" for good reasons. Unless you absolutely know what you are doing, best keep these settings default as misuse often causes startup issues.
Interfaces -> Other Type -> Loopback -> + > Name LO1
Interfaces -> Assigment Name "LO1",
Interfaces -> LO1 - Enable Interface
IPv4 Configuration Type: Static IPv4
IPv4 address: 127.0.0.1/8
server:
local-data: "local.lan. 10800 IN SOA opn.local.lan. root.local.lan. 1 3600 1200 604800 10800"
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core # ls
+TARGETS blocklists.conf dot.conf unbound_dhcpd.conf
access_lists.conf dnsbl_module.py private_domains.conf
advanced.conf domainoverrides.conf safesearch.conf
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core #
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core #
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core # cat +TARGETS
access_lists.conf:/usr/local/etc/unbound.opnsense.d/access_lists.conf
advanced.conf:/var/unbound/advanced.conf
blocklists.conf:/usr/local/etc/unbound/unbound-blocklists.conf
safesearch.conf:/usr/local/etc/unbound.opnsense.d/safesearch.conf
dot.conf:/usr/local/etc/unbound.opnsense.d/dot.conf
private_domains.conf:/var/unbound/private_domains.conf
domainoverrides.conf:/usr/local/etc/unbound.opnsense.d/domainoverrides.conf
unbound_dhcpd.conf:/usr/local/etc/unbound_dhcpd.conf
dnsbl_module.py:/var/unbound/dnsbl_module.py
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core #
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core #
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core # cat private_domains.conf
{% if not helpers.empty('OPNsense.unboundplus.domains.domain') or not helpers.empty('OPNsense.unboundplus.dots.dot') %}
server:
# Set private domains in case authoritative name server returns a Private IP address
{% set domains = [] %}
{% for domain in helpers.toList('OPNsense.unboundplus.domains.domain') %}
{% if domain.enabled == '1' %}
{% do domains.append(domain.domain) %}
{% endif %}
{% endfor %}
{% for forward in helpers.toList('OPNsense.unboundplus.dots.dot') %}
{% if forward.enabled == '1' and forward.domain and forward.type == 'forward' %}
{% do domains.append(forward.domain) %}
{% endif %}
{% endfor %}
{% for domain in domains|unique %}
domain-insecure: "{{ domain }}"
{% if domain is regex_match('.+\.(in-addr|ip6)\.arpa\.?$') %}
local-zone: {{ domain }} typetransparent
{% elif not helpers.exists('system.webgui.nodnsrebindcheck') %}
private-domain: "{{ domain }}"
{% endif %}
{% endfor %}
{% endif %}
root@opn:/usr/local/opnsense/service/templates/OPNsense/Unbound/core #
server:
local-data: "local.lan. 10800 IN SOA opn.local.lan. root.local.lan. 1 3600 1200 604800 10800"
do-not-query-localhost: no
forward-zone:
name: "."
forward-addr: 127.0.0.1@5353
Quote from: cs1 on February 08, 2024, 03:41:17 PM
Yes, that seems to be the case. You can't select an interface but only add an IP. As a workaround you can leave this empty and have it bind to all interfaces and set up firewall rules that only allow access via WAN. I'm not sure what the design decision is behind not being able to select an interface but I suspect it has something to do with dynamic IPs on interfaces (e. g. if there's no fixed WAN IP).
>>> Check for missing or altered package files
Checking all packages: .....
os-sensei-1.16.2: missing file /usr/local/zenarmor/output/archive/.placeholder
Quote from: franco on August 15, 2023, 02:31:34 PM
Reinstall with config import.
Cheers,
Franco
