Hi folks,
I'm stuck to get dnsmasq running. I checked all entries against my backup and copied them manually, but there is no dhcp-Server. By starting the service I get these error-messages:
root@omv:/etc# systemctl status -l dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: failed (Result: signal) since Fr 2017-10-06 12:39:37 CEST; 3min 43s ago
Process: 57992 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=exited, status=0/SUCCESS)
Process: 57927 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS)
Process: 57923 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
Process: 57920 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 57926 (code=killed, signal=SEGV)
Okt 06 12:39:36 omv dnsmasq[57920]: dnsmasq: Syntaxprüfung OK.
Okt 06 12:39:36 omv dnsmasq[57926]: gestartet, Version 2.72, Cachegröße 150
Okt 06 12:39:36 omv dnsmasq[57926]: Übersetzungsoptionen: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
Okt 06 12:39:36 omv dnsmasq-dhcp[57926]: DHCP, IP-Bereich 192.168.22.20 -- 192.168.22.245, Lease Zeit7d
Okt 06 12:39:36 omv dnsmasq[57926]: Benutze lokale Adressen nur für Domain aceh.vdr
Okt 06 12:39:36 omv dnsmasq[57926]: keine Server in /var/run/dnsmasq/resolv.conf gefunden, werde es später neu versuchen
Okt 06 12:39:36 omv systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Okt 06 12:39:36 omv systemd[1]: dnsmasq.service: main process exited, code=killed, status=11/SEGV
Okt 06 12:39:37 omv systemd[1]: Unit dnsmasq.service entered failed state.
journalctl -xn
-- Logs begin at Do 2017-10-05 21:58:03 CEST, end at Fr 2017-10-06 12:45:03 CEST
Okt 06 12:39:36 omv kernel: dnsmasq[57926]: segfault at 7ffdc6560fe0 ip 00007f3a
Okt 06 12:39:36 omv systemd[1]: dnsmasq.service: main process exited, code=kille
Okt 06 12:39:36 omv systemd[1]: Starting Host and Network Name Lookups.
-- Subject: Unit nss-lookup.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nss-lookup.target has begun starting up.
Okt 06 12:39:36 omv systemd[1]: Reached target Host and Network Name Lookups.
-- Subject: Unit nss-lookup.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nss-lookup.target has finished starting up.
--
-- The start-up result is done.
Okt 06 12:39:37 omv postfix/master[2435]: reload -- version 2.11.3, configuratio
Okt 06 12:39:37 omv systemd[1]: Unit dnsmasq.service entered failed state.
Okt 06 12:45:01 omv CRON[58186]: pam_unix(cron:session): session opened for user
Okt 06 12:45:01 omv CRON[58187]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>
Okt 06 12:45:01 omv rrdcached[1477]: Received FLUSHALL
Okt 06 12:45:03 omv CRON[58186]: pam_unix(cron:session): session closed for user
What about my settings:
eth0:
192.168.2.11/255.255.255.0; GW: 192.168.2.254; DNS: 192.168.2.254
eth1:
192.168.22.11/255.255.255.0;
IP-forwarding is enabled and works vice versa.
I need dnsmasq-dhcp for eth1 only and new hardware should be able to get outside. This worked already with OMV-2.
root@omv:/etc/dnsmasq.d# more omv.conf
# Configuration file for dnsmasq.
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
strict-order
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
local=/heca.vdr/
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
domain=aceh.vdr
log-queries
dhcp-range=192.168.22.20,192.168.22.245,255.255.255.0,168h
log-dhcp
dhcp-option=option:router,192.168.22.11
dhcp-hostsfile=/etc/dnsmasq-dhcphosts
dhcp-option=option:domain-search,aceh.vdr
dhcp-option=15,"heca.vdr"
dhcp-option=44,192.168.22.11
dhcp-option=option:ntp-server,192.53.103.108
dhcp-option=6,192.168.22.11,8.8.8.8,8.8.8.4
cname=mldserver,mldserver
cname=mldserver.heca.vdr,mldserver.heca.vdr
cname=mldrpi3b,mldrpi3b
cname=mldrpi3b.heca.vdr,mldrpi3b.heca.vdr
cname=octonet,octonet
cname=octonet.heca.vdr,octonet.heca.vdr
root@omv:/etc/dnsmasq.d# more dnsmasq.eh.conf
# dhcp-interface
interface=eth1
root@omv:/etc# more dnsmasq-dhcphosts
08:00:27:da.d3:0e,192.168.22.240
b8:27:eb:eb:24:05,192.168.22.23
54:84:7b:00:33:2a,192.168.22.20
root@omv:/etc# more resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.2.254
search heca.intern heca.vdr
Whats missing? Thnx for patience.
Regards