OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of Olodin »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

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.

  • Messages
  • Topics
  • Attachments

Topics - Olodin

Pages: [1]
1
17.7 Legacy Series / DHCP leases not resolvable in unbound
« on: September 26, 2017, 02:37:17 pm »
I have set unbound to "Register DHCP leases in the DNS Resolver" and "Register DHCP static mappings in the DNS Resolver" but are unable to resolve new dhcp leases.

What I found so far is, that /var/unbound/dhcpleases.conf is written and data is ok. Simply restarting unbound will help to resolve new hosts from dhcpleases.conf.
It seems that unbound is not triggered to read the changed file.

The box is currently running 17.7.3.

This is unbound config:
Code: [Select]
  <unbound>
    <custom_options>include:/var/unbound/conf.d/ad-blacklist.conf</custom_options>
    <forwarding>1</forwarding>
    <regdhcp>1</regdhcp>
    <regdhcpstatic>1</regdhcpstatic>
    <active_interface/>
    <outgoing_interface/>

### snip
host entries
### snip

    <hideidentity>1</hideidentity>
    <hideversion>1</hideversion>
    <cache_max_ttl/>
    <cache_min_ttl/>
    <incoming_num_tcp>10</incoming_num_tcp>
    <infra_cache_numhosts>10000</infra_cache_numhosts>
    <infra_host_ttl>900</infra_host_ttl>
    <jostle_timeout>200</jostle_timeout>
    <log_verbosity>1</log_verbosity>
    <msgcachesize>4</msgcachesize>
    <num_queries_per_thread>512</num_queries_per_thread>
    <outgoing_num_tcp>10</outgoing_num_tcp>
    <unwanted_reply_threshold/>
    <enable>1</enable>
    <acls>
      <aclname>nt0010 openvpn adress</aclname>
      <aclaction>allow</aclaction>
      <description>nt0010 openvpn adress</description>
      <row>
        <acl_network>172.16.1.2</acl_network>
        <mask>32</mask>
        <description>nt0010 openvpn adress</description>
      </row>
    </acls>
    <acls>
      <aclname>Openvpn Clients</aclname>
      <aclaction>allow</aclaction>
      <description/>
      <row>
        <acl_network>172.16.7.0</acl_network>
        <mask>24</mask>
        <description/>
      </row>
    </acls>
  </unbound>

2
17.7 Legacy Series / [SOLVED] dyndns with multiwan: only IP from default gateway?
« on: August 09, 2017, 09:37:42 pm »
Hi,

I have a multi-wan setup with 3 next hop router and want to update 3 freedns records based on those routers wan IPs.

This is what I have configured 3 times (see screenshot), each with its unique hostname and with the "interface to monitor" set to the corresponding interface.

But all records are updated with the IP adresse from the default route and not the different wan ips.

The logs say this:
Code: [Select]
Aug 9 21:17:30 opnsense: /services_dyndns_edit.php: Dynamic DNS (myfreedns.hostname): (Success) IP Address Changed Successfully!
Aug 9 21:17:30 opnsense: /services_dyndns_edit.php: Dynamic DNS: updating cache file /var/cache/dyndns_opt2_myfreedns.hostname_0.cache: 80.62.134.xxx

The box is running
OPNsense 17.7-amd64
FreeBSD 11.0-RELEASE-p11


Any ideas?
LibreSSL 2.4.5

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2