V5 to v6 2024.07 to 2025.02.1

pihole.toml is your one-stop shop for configuring all aspects of your (bare metal) Pi-hole. It can be updated by many different means (see Introducing Pi-hole v6), and it combines various settings previously strewn over different config files in v5 (like setupVars.conf, pihole-FTL.conf and /etc/dnsmasq.d/*).

You've already quoted me pointing out that pihole-FTL is a tailored fork of dnsmasq.
As such, it's inheriting everything from its upstream parent, apart from some DNS portions, which our developers customised to allow for speedy blocking and extra features like regex blocking and deep CNAME inspection.

The paragraph you're quoting specifically mentions a dnsmasq default.
As far as the DHCP server feature is concerned, pihole-FTL is identical to dnsmasq.
Thus, all of dnsmasq's default's apply. As changing them would require to change dnsmasq code rather than Pi-hole's, it seems fair to keep that reference to dnsmasq.

As with v5, pihole-FTL internally still will read dnsmasq options from a configuration file in pure dnsmasq syntax, but to better avoid conflicts, v6 moved this /etc/pihole/dnsmasq.conf, using pihole.toml to populate it.

1 Like

everyone seems to be ignoring the fact the docker tag is no longer a hyperlink
is this a bug?
this is the last time I will mention it, as I already have like 5 times, the system is running fine just need to change the variable still but its currently not effecting anything

found another bug

padd does not work

$ sudo docker exec -it pi-hole padd
[รขล“โ€”] Error!
    PADD only works in conjunction with Pi-hole!

along with everything else I have said like:

so you did secretly listen to me
or did you already know about these bugs

the docker tag is a hyperlink after updating
padd still does not work
and the DHCP server metrics and DNS cache metrics lose data on FTL restart

I swear your reading these but ignoring me for some reason
Please tell me what I did, so I can be better in the future

Make PADD compatible with Pi-hole v6 (pi-hole/PADD#247) + a lot of smaller associated PRs

that would have been nice to know it was not compatible, I didn't see it say that anywhere

I did write more but felt like it was cause me to be banned
I am really trying, the things I want to say but I am stopping myself

solution: wait for bugs to be solved, read documentation, stay calm and be patient

1 Like