Please follow the below template, it will help us to help you! Expected Behaviour: The previous web interface displayed the IPv4 and IPv6 addresses for use for manual device DNS setups. Actual Behaviour: The web interface no longer provides the IPv4 and IPv6 addresses I need for manual device DNS s…

This was removed, since the information is not always accurate. https://github.com/pi-hole/AdminLTE/commit/cf917a6391a6a309be9dfdf87f0bde7c66d698b4 You can run ip addr to show this information, or generate a debug log with pihole -d and the information will be near the top.

[image] bcutter: By the way: those two lines are meanwhile in /etc/pihole/setupVars.conf again 2 times, don´t know what action added them. Just FYI, I personally don´t really care -.- Thanks for letting us know. That's a bug. I'll fix that.

[image] bcutter: Sent by PM. Thanks, we had a bit of conversation over there and I've also checked the configuration which is plain standard. This means FTL is unable to obtain any kind of information about the interfaces connected to your system. On none of the test systems we used during de…

In addition, I'd like to ask you to run pihole checkout ftl tweak/iface_detection and repeat the nslookup and send me again what you see in pihole-FTL.log (pihole.log not needed). I added more debugging output and this should hopefully reveal why your interface is not correctly being detected her…

[image] DL6ER: On which hardware is this system running? Do you use any kind of virtualization? Raspberry Pi 4 on Raspbian. No virtualization. Only „special“ config as mentioned is a virtual interface on top of eth0 which runs a separate IP address Pi-Hole is bind to.

[image] bcutter: Set the right IP address with REPLY_ADDR4 in /etc/pihole/pihole-FTL.conf and now everything`s fine again. Is this really resolved with the current version? I'm currently running: Docker Tag 2021.10 Pi-hole v5.5 FTL v5.10.2 Web Interface v5.7 When I'm configuring the virt…

That post you quoted was 20 days and many test and debug steps ago. But yes, currently with FTL 5.10.2 and parameter set in FTL config the virtual interface IP of pihole is correctly resolved. Anyway, this should work automatically without the parameter set manually, that’s why DL6ER is still inve…

[image] bcutter: But yes, currently with FTL 5.10.2 and parameter set in FTL config the virtual interface IP of pihole is correctly resolved. That's strange. I actually found the reason why REPLY_ADDR4 in my pihole-FTL.conf always got overwritten with the wrong IP on every container restart. …

[image] derandiunddasbo: But: At least in my case, this settings still seems to be ignored, as pihole-FTL still pushes the wrong IP to clients. Just to make sure: you did a ’pihole restartdns‘ after changing the FTL config right? And maybe cleared clients DNS cache. That worked for me, always…

[image] derandiunddasbo: At least in my case, this settings still seems to be ignored, as pihole-FTL still pushes the wrong IP to clients. Could you check what your /var/log/pihole-FTL.log says about REPLY_ADDR4 ? It should say REPLY_ADDR4: Using IPv4 address 192.168.4.250 in IP blocking …

Pi-hole Userspace

Finding Pi-hole IP addresses after v5.4 update

Help

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled