Pi hole works on all devices but on a wired connection

Help
1

Actual Behaviour:

[ Internet drops connection when I try to connect my laptop to a wired connection]

DHCP server is active on the pihole. I have done a few clean install a few days ago but same thing happens. I guess it's a mistake on my part.
I would appreciate if someone could help me with this...

Debug Token:

[cpitw1e8cd]

EDIT: The problem was my router with DD-WRT firmware!!
Some DD-WRT and Openwrt firmware have this problem on some TP-Link and Netgear routers. Especially the older routers that aren't officially maintained.

Here's what I didi (from dd-wrt forum):

OK, problem solved!

  1. log in to your router IP. "192.168.1.---"
  2. on DD-WRT GUI, select ADMINISTRATION
  3. enter password
  4. select COMMANDS
  5. in commands box enter the following on each line

code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 set apply

  1. below the box click RUN COMMAND
  2. If this runs without error, then lastly click SAVE TO STARTUP.

YOUR LAN PORT WILL NOW WORK EVERYTIME

I hope this thread will be helpful for someone with similar problem as I was having.

2

Please try to help us help you.

3

I guess it's good now? Thanks!

4

Can you ping the Pi-hole's IP address when on the wired connection?

5

nope. It doesn't "see" the pihole somehow.

6

Check your router to see if it is separating wired and wireless devices. This is more of a networking problem than a Pi-hole issue.

7

But it only happens when I have pihole connected. So I think it has something to do with it.

8

I looks like you have the DHCP server set to hand out the Pi-hole device as the router, is this the intended configuration?

9

Hum... Pihole has DHCP enabled, and it seems to be doing its job. All wireless devices are working properly blocking ads.

10

Do you know if your router has Wireless Client Isolation?

11

I'm not sure... I am using ddwrt tho.
Edit: It does have it (ap isolation) but is unchecked.

12

Try setting the gateway address to that of the DD-WRT router, your wireless clients may be getting the correct information, but wired clients are getting the wrong router/gateway address.

What Operating Systems are on your clients? (We can check and see what addresses your clients are getting for all of their configurations.)

13

Do you mean check the client isolation box? I only have the option to check the box, no place to point to an ip/gateway. The gateway of the WAN or LAN connection (192.168.1.1)?

In my network I have Windows 10 and android devices.

Thanks for being patient.

14

What's the output from the following on the Pi-hole device:

ip addr
ip link
ip route
15 
pi@raspberrypi:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:f0:52:62 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.144/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::987a:631a:e86f:ed0/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:a5:07:37 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::76f5:febd:b5de:c6e7/64 scope link tentative
       valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none
    inet 10.8.0.1/24 brd 10.8.0.255 scope global tun0
       valid_lft forever preferred_lft forever

pi@raspberrypi:~ $ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether b8:27:eb:f0:52:62 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT group default qlen 1000
    link/ether b8:27:eb:a5:07:37 brd ff:ff:ff:ff:ff:ff
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
    link/none

pi@raspberrypi:~ $ ip route
default via 192.168.1.1 dev eth0  metric 202
10.8.0.0/24 dev tun0  proto kernel  scope link  src 10.8.0.1
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.144  metric 202
16

Okay, and what does your /etc/pihole/setupVars.conf currently look like?

cat /etc/pihole/setupVars.conf
17

pi@raspberrypi:~ $ cat /etc/pihole/setupVars.conf
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.144/24
IPV6_ADDRESS=
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
QUERY_LOGGING=true
INSTALL_WEB=true
WEBPASSWORD=c806b5a682bfe0dfd0d45087f5cec0175175e56fa9d95433b9d81d96c77750fd
DHCP_ACTIVE=true
DHCP_START=192.168.1.101
DHCP_END=192.168.1.141
DHCP_ROUTER=192.168.1.144
DHCP_LEASETIME=48
PIHOLE_DOMAIN=local
DHCP_IPv6=true

18

On the settings page of the Admin panel, change the DHCP Router (gateway) to be the IP address of your DD-WRT router, not of the Pi-hole.

19

added 192.168.1.1

I'll try to connect to the wired connection again.

Edit: I ran the network diagnostic and got 'Ethernet doesn't have a valid ip configuration' message.
Edit2: I Manually changed the IP for the ethernet and I can access websites but pihole's admin page.

20

Have you rebooted the clients so that they get the new DHCP lease with the new IP information?