Pihole Does not work in Wifi Mode

Help Community Help
1

I have Raspberry Pi 1 installed and running only Pihole, i have configured the pi to work perfectly in wifi and ethernet mode without issues. Pi hole works fine with ethernet cable connected as it should.
I am able to connect to the portal and see the settings, but does not do the blocking. I have IPV6 Disabled in the PI Settings and the router.

Although this works in Ethernet mode and does the blocking for all devices acting as a DHCP, it does not block when the Pi is connected via Wifi. Do note i am able to ping google and the internet is up.
Kindly help me here.
Debug Token:
https://tricorder.pi-hole.net/d92m1n0u19

2

From your debug log, you still have connectivity problems on the Pi-hole host.

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the enxb827ebe77832 interface.

[✗] No IPv6 address(es) found on the enxb827ebe77832 interface.

[i] Default IPv4 gateway: 192.168.1.1
   * Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.mgsmedia.ru is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve www.mgsmedia.ru via Pi-hole (192.168.1.30)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=enxb827ebe77832
    IPV4_ADDRESS=192.168.1.30/24
3

How do i resolve it ? i did the below and tried, still does not work

sudo ifconfig enxb827ebe77832 down
sudo ifconfig wlx801f02bf0b5b up

Pinging google.com works fine
ping google.com
PING google.com (74.125.24.101) 56(84) bytes of data.
64 bytes from 74.125.24.101 (74.125.24.101): icmp_seq=1 ttl=59 time=36.8 ms
64 bytes from 74.125.24.101 (74.125.24.101): icmp_seq=2 ttl=59 time=36.3 ms

also i am able to ping the gateway which is my wifi modem from Pi1
ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.96 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.48 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.67 ms

4

In this configuration, please generate a new debug log, upload it and post the new token.

5

Even after executing the steps i am able to see the same error, it does not seem to use wlan config instead still uses ethernet and somehow able to ping google.
https://tricorder.pi-hole.net/rxk6heoxur

This is the profile in dhcpcd.conf
#fallback to static profile on eth0
#interface eth0
#fallback static_eth0
interface wlx801f02bf0b5b
static ip_address=192.168.1.30/24
static routers=192.168.1.1
static domain_name_servers=127.0.0.1
interface enxb827ebe77832
static ip_address=192.168.1.30/24
static routers=192.168.1.1
static domain_name_servers=127.0.0.1

6

You have two different interface names assigned to the same IP. Look at the output of the following command: it will tell you which interfaces are active.

ip addr

7

Yes that is because i want pi to have same ip if i connect to either wifi or lan. And we will be able to connect to either one any one point of time.

8

How are you telling linux how to properly route packets then?

9

Create a bridge interface to aggregate those two interfaces into one IP:

10

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