Pi-Hole won't connect to internet with 2 nics installed on Hyper-v

Piehole works but no connection to Internet

Expected Behaviour:

It should work, even with 2 nics on Hyper-v

Actual Behaviour:

Can connect to internal and get DHCP working but I can not reach out to Internet.

Debug Token:

Don't have one yet as I am sure it has to do with the Configuration in Debian.

So I need some help as I am not a Linux guy, I have Debian stretch as minimal server and 2 nics on Hyper-v.

The first nic (External) configured DHCP so that if I connect to any network it gets a connection. Hyper-v Management disabled so every traffic goes over internal.
The second nic (Internal) configured as static ip to connect my Laptop and all other Virtual machines.

Pihole is installed on the second nic, I can update it and I have it configures with DHCP and I get my Internal computers connected. I also can reach the Pihole webconfiguration.

What I don't get is connection to the internet.
The Same configuration worked with pfsense but it consumes to much resources.
I don't know if I miss some configuration in Debian or else.
Any help would be appreciated.

--- wow, not one single attempt to help. Seems to me I have to look for another solution. :frowning:

pfsense is a Router/Gateway, with your Setup pihole wont give you Internet Access, the Gateway Function has to be up and running and pihole will only do the Name resolution

Thanks for responding, I only mentioned pfsense because I was using it before with the same network configuration. Also, I had pihole running with 1 nic and it works just fine. My question was related how to make that happen in Debian minimal install with 2 Nics. The first Nic should be dhcp and the second, static, for Debian, aka pihole.

I installed it, updated it, all ok. I can connect from local to hyperv and log in to pihole but I can not get to internet. I can ping to the dhcp given ip address on eth0 but I can not reach out from there. On the other hand from the Debian installation I can ping everything, outside and inside.

I am not a Linux guy who can setup the correct network so I asked for help because there is nothing to find in internet what is useful and I did not try already in a period of a few month.

So anything what helps that would be fine to get this running,

Given that your Pi-Hole works with 1 NIC and not with 2, I think this is a difficulty with your network that we will not be able to help you resolve. I recommend additional searching for a web resource that can help you with your specific network configuration.

Given that would be great but as Hyper-v with Pihole is on a Laptop there are Hyper-v WiFi for Extern with management access disabled (no connection internal), aka Debian eth0 and Hyper-v Lan or Internal, aka eth1.

Pihole is therefore installed eth1 with static ip and eth0 is access to the internet. As I mentioned before, i can login to pihole, updated it, download lists everything. I can ping from Hyper-v pihole to the outside and to inside without problems. From the inside i can only reach up to eth0 given ip from dhcp but not in the internet.
I am looking or researching now for month and there is nothing to find, every configuration listed for Debian networks are either out of date or simple all with static ip what does not help.
As far as i found today, there are 2 errors in ip route show table all. I can not figure out how this works. :frowning: not a Linux guy nor a scripting guy.

i think you didnt really get the fact that pihole wont route anything to the internet. inside of the hyper-v you have internet-access through eth0, but other internal clients will only see eth1. pihole is not a router

edit: only way this could work is to set the IP from the Hyper-V eth1 only as DNS-Server for your internal Clients, the Default Gateway needs to be an other Machine

I am sorry but I guess I explain this all wrong or I get misunderstood.
Even without pihole installed on Hyper-v Debian I don't get connection to the internet if
Hyper v has 2 networks, external and internal. External is the shared access to either ISP or Router.
If I disable the Management in Hyper-v i can use with the Host Machine the Internal Network.

Host --> Internal -> Client with 2nics act as router (one nic to internal, one nic to exteral) --> ISP (example with pfsense and 2 nics)

That would be the same as

Host--> pihole --> Firewall Router --> ISP because the Firewall has in and out, equals 2 nics.

Now, without talking about pihole, if I try this with a Debian server and 2 nics to act as a firewall router I can not reach the internet. THAT is what I was asking for. So I am getting the fact but apparently everybody misunderstands.
If it is still unclear I have to create a flow chart or I give up on pihole because this would be the only configuration to utilize the Dhcp fuction in pihole in such environment.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.