Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pi-hole does not make it clear that Whitelist is associated to group(s) #4581

Open
ronald-mendoza opened this issue Jan 27, 2022 · 7 comments

Comments

@ronald-mendoza
Copy link

ronald-mendoza commented Jan 27, 2022

Versions

  • Pi-hole: v5.8.1
  • AdminLTE: v5.10.1
  • FTL: v5.13

Platform

  • OS and version: Ubuntu 21.10
  • Platform: bare metal

Expected behavior

Both at the console, as well as in the web GUI, it is not clear that the Whitelist entries are actually associated with a group. (The Default group that is created after install.) Because of this, it is very easy to assume that the Whitelist entries are global.
The documentation should be clear that the Whitelist function adds an entry to Group Management > Domains, assigned to the Default group, and that it needs to be adjusted if that is not the intended behavior.
In addition, I would suggest that any viewing of the Whitelist should also include the group assignment.
e.g. at the console, using pihole -w -l should also include the group(s) that each domain is assigned to
in the web GUI, the section of the Whitelist page that shows a table for the List of whitelisted entries should include a column for the group(s) each Domain/RegEx is assigned to -OR- instead of showing a List of whitelisted entries, it should point the user to Group Management > Domains.

Actual behavior / bug

Because the Whitelist entries are assigned to the Default group, if you have any additional groups created, and have adlist(s) associated with those groups, adding entries to the Whitelist will not apply to the non-Default group(s). This gives the impression that the Whitelist is not functioning.

Steps to reproduce

Add a non-default group. Assign an adlist to that non-default group. Add a Whitelist entry at the console or in the web GUI. Test using a client that belongs to the non-default group and confirm that the whitelisted entry is not effective.
Next, in the web GUI, go to Group Management > Domains. Find the domain related to the whitelist entry, and notice that it actually has a group assignment to the Default group.
Assign that domain to the non-default group and re-test, to confirm that the whitelisted entry is now effective.

@ronald-mendoza
Copy link
Author

ronald-mendoza commented Jan 29, 2022

@PromoFaux Can you elaborate on what documentation is needed? Are you referring to screenshots of the console and web GUI? Or something else?

@PromoFaux
Copy link
Member

The documentation should be clear that the Whitelist function adds an entry to Group Management > Domains, assigned to the Default group, and that it needs to be adjusted if that is not the intended behavior.

This, no? The label is more of a reminder that we need to look at the documentation (and/or anyone else that wants to document it and submit a PR)

@ronald-mendoza
Copy link
Author

Gotcha. I thought the label meant that the team needed more documentation from me to understand what I was reporting.

Besides updating the documentation, I had also made a suggestion on product changes at the console and the GUI, to more clearly reflect the group(s) assigned with any domain on the whitelist.

@martinbrose
Copy link
Sponsor

@PromoFaux I have given this a go and filed two related PRs in pi-hole/docs and pi-hole/AdminLTE.

At least that should address the documentation request from @ronald-mendoza.

Adding the associated groups to the output of pihole -w -l would require changes in pi-hole/FTL?
I guess the terminal output could get quite messy quickly, so not sure if this is agreed to be looked at?

@rdwebdesign
Copy link
Member

I think this issue was addressed months ago, but never closed.

Currently, there is a note explicitly saying the domain/regex will be added to the Default Group:
image

Also, the documentation was updated.

Can we close this?

@ronald-mendoza
Copy link
Author

I think the note in the WebUI is sufficient. But what about at the console?

pihole -w -l still does not show any group association with entries, and I'm not even sure it is possible to assign a non-default group to an entry at the command-line.

@yubiuser
Copy link
Member

pihole -w -l still does not show any group association with entries

This is true. We could, however, change the current pihole -w -l code to the output we have in pihole -d "Domainlist" and just filter for white/blacklist entries.

I'm not even sure it is possible to assign a non-default group to an entry at the command-line.

Not with a pihole command. The web interface executes sqlite commands directly to modify the group assignment. You could do the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants