Problems with dnsmasq and interfaces

tim11 · June 1, 2019, 10:49am

Please follow the below template, it will help us to help you!

Expected Behaviour:

[Replace this text with what you think should be happening]

Actual Behaviour:

hi everyone, i got several problems on my proxy server, on which i installed pi hole 2 days ago. i got 3 NIC with 3 IP ranges (178.1, 1.1 and 2.1), interfaces are enp1s0, enp2s0 and enp3s0.

pi hole worked fine when installed, but listened to main interface only, which is enp2s0. i found the solution with the 99-inferfaces.conf in here, but it didnt work. Interface listening behavior at web interface is on

Listen on all interfaces

99-interfaces.conf:

interface=enp1s0
interface=enp2s0
interface=enp3s0

after that my dnsmasq had problems with line 44 (dhcp-name-match=set:wpad-ignore,wpad). i found some topics with the same problems but no help. my ftl is v4.3.1
when going with

pihole checkout ftl master

i receive a

Error: Unable to get latest release location from GitHub.

i put the ISP DNS server back on but no connection.

so, how do i get dnsmasq back on track with line 44 and support for the other interfaces?
thanks for your help

Debug Token:

[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]

DL6ER · June 1, 2019, 10:52am

You should not use dnsmasq. The error you see is caused by the system-wide dnsmasq on your system being to old.
With Pi-hole you should only use pihole-FTL which includes its own fork of dnsmasq.

tim11 · June 1, 2019, 10:59am

thanks for your fast help. i checked on an old backup the original dnsmasq.conf, pihole replaced it and killed all my settings with interfaces.
So i have to purge dnsmasq on my proxy and reinstall pihole?
if so, where do i place my ip ranges for all 3 NIC, my permanent ip for several clients and so on?

DL6ER · June 1, 2019, 11:00am

Just create a new file inside /etc/dnsmasq.d, name it maybe 99-interfaces.conf

tim11 · June 1, 2019, 11:02am

great. fork got same syntax as the original conf on permanent ip and other settings?

DL6ER · June 1, 2019, 11:05am

Yes, you will not see any differences. It is also guaranteed that our fork inside pihole-FTL is always the latest version whereas some distributions still ship versions that are years old.

tim11 · June 1, 2019, 11:13am

thanks, i will test it tomorrow. thanks for your help, have a nice day

tim11 · June 2, 2019, 11:06am

i ran a clear installation on a backup. Now i got problem with ftl. service tells me

● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sun 2019-06-02 12:54:28 CEST; 1s ago
Docs: man:systemd-sysv-generator(8)
Process: 1915 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 1920 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Jun 02 12:54:28 proxyserver systemd[1]: Starting LSB: pihole-FTL daemon...
Jun 02 12:54:28 proxyserver pihole-FTL[1920]: Not running
Jun 02 12:54:28 proxyserver su[1949]: Successful su for pihole by root
Jun 02 12:54:28 proxyserver su[1949]: + ??? root:pihole
Jun 02 12:54:28 proxyserver su[1949]: pam_unix(su:session): session opened for user pihole by (uid=0)

web interface:

DNS service not running FTL offline
Load: 0.3 0.23 0.1
Memory usage: 6.2 %

FTL Information

The FTL service is offline!

sudo service pihole-FTL restart wont solve the problem

directory @var:

***@proxyserver:/var/run/pihole$ ls -lha
insgesamt 0
drwxr-xr-x 2 pihole pihole 40 Jun 2 12:49 .

so where did i scew up?

DL6ER · June 2, 2019, 5:51pm

Check these two for error lines:

tail /var/log/pihole.log
tail /var/log/pihole-FTL.log

tim11 · June 4, 2019, 2:40pm

[2019-06-04 16:17:22.754 951] Using log file /var/log/pihole-FTL.log
[2019-06-04 16:17:23.193 951] ########## FTL started! ##########
[2019-06-04 16:17:23.193 951] FTL branch: master
[2019-06-04 16:17:23.193 951] FTL version: v4.3.1
[2019-06-04 16:17:23.193 951] FTL commit: b60d63f
[2019-06-04 16:17:23.193 951] FTL date: 2019-05-25 21:37:26 +0200
[2019-06-04 16:17:23.193 951] FTL user: pihole
[2019-06-04 16:17:23.193 951] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2019-06-04 16:17:23.193 951] SOCKET_LISTENING: only local
[2019-06-04 16:17:23.193 951] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2019-06-04 16:17:23.193 951] MAXDBDAYS: max age for stored queries is 365 days
[2019-06-04 16:17:23.193 951] RESOLVE_IPV6: Resolve IPv6 addresses
[2019-06-04 16:17:23.193 951] RESOLVE_IPV4: Resolve IPv4 addresses
[2019-06-04 16:17:23.193 951] DBINTERVAL: saving to DB file every minute
[2019-06-04 16:17:23.193 951] DBFILE: Using /etc/pihole/pihole-FTL.db
[2019-06-04 16:17:23.193 951] MAXLOGAGE: Importing up to 24.0 hours of log data
[2019-06-04 16:17:23.193 951] PRIVACYLEVEL: Set to 0
[2019-06-04 16:17:23.194 951] IGNORE_LOCALHOST: Show queries from localhost
[2019-06-04 16:17:23.194 951] BLOCKINGMODE: Null IPs for blocked domains
[2019-06-04 16:17:23.194 951] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2019-06-04 16:17:23.194 951] DBIMPORT: Importing history from database
[2019-06-04 16:17:23.194 951] PIDFILE: Using /var/run/pihole-FTL.pid
[2019-06-04 16:17:23.194 951] PORTFILE: Using /var/run/pihole-FTL.port
[2019-06-04 16:17:23.194 951] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2019-06-04 16:17:23.194 951] WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2019-06-04 16:17:23.194 951] BLACKLISTFILE: Using /etc/pihole/black.list
[2019-06-04 16:17:23.194 951] GRAVITYFILE: Using /etc/pihole/gravity.list
[2019-06-04 16:17:23.194 951] REGEXLISTFILE: Using /etc/pihole/regex.list
[2019-06-04 16:17:23.194 951] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2019-06-04 16:17:23.194 951] AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2019-06-04 16:17:23.194 951] MACVENDORDB: Using /etc/pihole/macvendor.db
[2019-06-04 16:17:23.194 951] PARSE_ARP_CACHE: Active
[2019-06-04 16:17:23.195 951] Finished config file parsing
[2019-06-04 16:17:23.404 951] Database version is 3
[2019-06-04 16:17:23.405 951] Database successfully initialized
[2019-06-04 16:17:23.405 951] Imported 0 queries from the long-term database
[2019-06-04 16:17:23.406 951] -> Total DNS queries: 0
[2019-06-04 16:17:23.406 951] -> Cached DNS queries: 0
[2019-06-04 16:17:23.406 951] -> Forwarded DNS queries: 0
[2019-06-04 16:17:23.406 951] -> Exactly blocked DNS queries: 0
[2019-06-04 16:17:23.406 951] -> Unknown DNS queries: 0
[2019-06-04 16:17:23.406 951] -> Unique domains: 0
[2019-06-04 16:17:23.406 951] -> Unique clients: 0
[2019-06-04 16:17:23.406 951] -> Known forward destinations: 0
[2019-06-04 16:17:23.406 951] Successfully accessed setupVars.conf

Error on pihole.log.1, but this shouldnt concern DNS:

Jun 2 16:32:58 dnsmasq[8845]: failed to load names from /etc/pihole/black.list: No such file or directory

Jun 2 16:31:56 dnsmasq[8845]: started, version pi-hole-2.80 cachesize 10000
Jun 2 16:31:56 dnsmasq[8845]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
Jun 2 16:31:56 dnsmasq-dhcp[8845]: DHCP, IP range 192.168.2.150 -- 192.168.2.175, lease time 3d
Jun 2 16:31:56 dnsmasq-dhcp[8845]: DHCP, IP range 192.168.1.150 -- 192.168.1.175, lease time 3d
Jun 2 16:31:56 dnsmasq-dhcp[8845]: DHCP, IP range 192.168.2.150 -- 192.168.2.175, lease time 3d
Jun 2 16:31:56 dnsmasq-dhcp[8845]: DHCP, IP range 192.168.1.150 -- 192.168.1.175, lease time 3d
Jun 2 16:31:56 dnsmasq[8845]: using nameserver 1.0.0.1#53
Jun 2 16:31:56 dnsmasq[8845]: using nameserver 1.1.1.1#53
Jun 2 16:31:56 dnsmasq[8845]: read /etc/hosts - 11 addresses
Jun 2 16:31:56 dnsmasq[8845]: read /etc/pihole/local.list - 2 addresses
Jun 2 16:31:56 dnsmasq[8845]: failed to load names from /etc/pihole/black.list: No such file or directory
Jun 2 16:31:57 dnsmasq[8845]: read /etc/pihole/gravity.list - 113443 addresses
Jun 2 16:32:58 dnsmasq[8845]: read /etc/hosts - 11 addresses
Jun 2 16:32:58 dnsmasq[8845]: read /etc/pihole/local.list - 2 addresses
Jun 2 16:32:58 dnsmasq[8845]: failed to load names from /etc/pihole/black.list: No such file or directory
Jun 2 16:32:58 dnsmasq[8845]: read /etc/pihole/gravity.list - 113443 addresses
Jun 2 16:32:58 dnsmasq[8845]: read /etc/hosts - 11 addresses
Jun 2 16:32:58 dnsmasq[8845]: read /etc/pihole/local.list - 2 addresses
Jun 2 16:32:58 dnsmasq[8845]: failed to load names from /etc/pihole/black.list: No such file or directory
Jun 2 16:32:59 dnsmasq[8845]: read /etc/pihole/gravity.list - 113443 addresses
Jun 2 16:33:05 dnsmasq[8845]: query[MX] smtp.XXX.de from 127.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: forwarded smtp.XXX.de to 1.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: forwarded smtp.XXX.de to 1.1.1.1
Jun 2 16:33:05 dnsmasq[8845]: query[A] smtp.XXX.de from 127.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: forwarded smtp.XXX.de to 1.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: reply smtp.XXX.de is XXX
Jun 2 16:33:05 dnsmasq[8845]: query[AAAA] smtp.XXX.de from 127.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: forwarded smtp.XXX to 1.0.0.1
Jun 2 16:33:05 dnsmasq[8845]: reply smtp.XXX.de is XXX
Jun 2 16:34:02 dnsmasq[8845]: exiting on receipt of SIGTERM

pihole.log is clear

tim11 · June 4, 2019, 4:02pm

got it, google is your friend:

Seems to be solved by sudo touch /var/lib/misc/dnsmasq.leases sudo chown pihole:pihole /var/lib/misc/dnsmasq.leases sudo reboot

system · June 25, 2019, 4:02pm

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.