After updating to latest versions (Pi-hole v5.3 Web Interface v5.5 FTL v5.8) and removing IP addresses from setupVars.conf as described in the announcement, 'pihole -g' command does not work anymore.
Automated IP blocking mode
Until now, FTL’s IP
and IP-NODATA-AAAA
blocking modes sourced the IP to deliver on a blocked domain from the setupVars.conf
values IPV4_ADDRESS
and IPV6_ADDRESS
. This is, however, quite a limitation, especially if the device running Pi-hole has more than one interface or of the address is changing. To address this, FTL v5.8 implements an automated IP blocking mode. Instead of reading the addresses from setupVars.conf
, we dynamically determine the address of the interface a query arrived on. We then use this IP address in the blocked reply. This does not only reduce maintenance ( IPV4_ADDRESS
and IPV6_ADDRESS
can now be removed from setupVars.conf
) but also localizes blocked queries. The automated detection can be overwritten using REPLY_ADDR4
and REPLY_ADDR6
in pihole-FTL.conf
.
issue:
pi@raspberrypi:~ $ pihole -g
No IP addresses found! Please run 'pihole -r' to reconfigure
setupVars.conf:
WEBPASSWORD=c4ed4b14fd7a9306efb67c3e6f1c
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=true
REV_SERVER=true
REV_SERVER_CIDR=192.168.0.0/24
REV_SERVER_TARGET=192.168.0.1
REV_SERVER_DOMAIN=fritz.box
BLOCKING_ENABLED=true
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=127.0.0.1#5335
PIHOLE_DNS_2=::1#5335
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
ADMIN_EMAIL=
WEBUIBOXEDLAYOUT=boxed
WEBTHEME=default-darker
ifconfig:
pi@raspberrypi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2003:XYZ:86c prefixlen 64 scopeid 0x0<global>
inet6 fd00::70fc:7114:a1f6:9b24 prefixlen 64 scopeid 0x0<global>
inet6 fe80::c1c1:5321:25f8:e87 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:bd:5c:aa txqueuelen 1000 (Ethernet)
RX packets 3197414 bytes 658461879 (627.9 MiB)
RX errors 0 dropped 408977 overruns 0 frame 0
TX packets 2362117 bytes 618913772 (590.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
dhcpcd.conf:
pi@raspberrypi:~ $ sudo nano /etc/dhcpcd.conf
interface eth0
static ip_address=192.168.0.2/24
static ip6_address=fd00::70fc:7114:a1f6:9b24/64
static routers=192.168.0.1
static domain_name_servers=::1
static domain_search=
Debug token
https://tricorder.pi-hole.net/ow5jaqcb1a
DL6ER
April 16, 2021, 6:44am
2
Thanks for the report. The comment about the possibility to remove the variables from setupVars.conf
was (initially) meant to be an internal one and it seems we forgot a few spots.
Proposed fix:
pi-hole:master
← pi-hole:fix/gravity_noIP
opened 06:42AM - 16 Apr 21 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have r… ead and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template.
- [X] I have made only one major change in my proposed changes.
- [X] I have commented my proposed changes within the code.
- [X] I have tested my proposed changes, and have included unit tests where possible.
- [X] I am willing to help maintain this change if there are issues with it later.
- [X] I give this submission freely and claim no ownership.
- [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
- [X] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
---
**What does this PR aim to accomplish?:**
Fix a bug reported on Discourse (see below).
**How does this PR accomplish the above?:**
Instead of relying on the correct IP address being in `setupVars.conf`, we should add all available addresses to `local.list`. FTL uses the option `localise-queries` that will pick the most appropriate one (arriving interface dependent) for the requesting client.
**What documentation changes (if any) are needed to support this PR?:**
None
1 Like
system
Closed
May 7, 2021, 6:45am
3
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.