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

Wiki for using VPN and PiHole is unclear #1553

Closed
DerfOh opened this Issue Jun 22, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@DerfOh
Copy link

DerfOh commented Jun 22, 2017

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

How familiar are you with the codebase?:

{replace this text with a number from 1 to 10, with 1 being not familiar, and 10 being very familiar}


[BUG REPORT | OTHER]:

Please submit your feature request here, so it is votable by the community. It's also easier for us to track.

[BUG | ISSUE] Expected Behaviour:

Afterwards, we change the interface of Pi-hole to eth0 (your local network adapter instead of the VPN adapter tun0). This can conveniently be done by using pihole -r + Reconfigure.

After a restart of the OpenVPN server, all clients should be able to see all devices within your (at home) local network. This is an example running on a distant server, which is connected through the VPN and can successfully communicate with all internal devices:

[BUG | ISSUE] Actual Behaviour:

Blocking works using eth0 but stops working for tun0 thus ending expected behavior for VPN.

[BUG | ISSUE] Steps to reproduce:

  • Follow the guide with a fresh install.

(Optional) Debug token generated by pihole -d:

<token>

This template was created based on the work of udemy-dl.

Suggested Fix:
What finally worked for me after pulling out my hair for the last couple days was the following command via the cli:

pihole -a -i all

Nowhere in the wiki does it suggest that this command even exists... Please add this to the guide for future users 👍

@nobody1407

This comment has been minimized.

Copy link

nobody1407 commented Jul 6, 2017

moved
#1588

@DL6ER

This comment has been minimized.

Copy link
Member

DL6ER commented Jul 7, 2017

Yes, your use case was never intended by the Wiki which was tailored for VPNs running on virtual servers where you won't/shouldn'b be sending DNS queries to eth0. I will nevertheless add your suggestion with some remarks.

You are right, this switch is undocumented as it is triggered internally from the Settings page which offers you this choice on the Settings page:
screenshot at 2017-07-08 01-20-28

@WaLLy3K

This comment has been minimized.

Copy link
Contributor

WaLLy3K commented Oct 9, 2017

@DL6ER, has this suggestion been added? I've taken a brief look over the article, but I can't find it. (Then again, I was never a good skim reader!)

@jacobsalmela

This comment has been minimized.

Copy link
Member

jacobsalmela commented Nov 25, 2017

It wasn't, but I added it in as I was recently editing several other pages in the wiki.

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