No Internet Connection on Wifi but wired works and blocks ads

Help Community Help
1

The issue I am facing:
I installed pi-hole my my r-pi 4. Seemed to go well. Ads are being blocked on my wired computers. However none of my wireless clients can get an internet connection. They all see the wifi SSID and can connect, but all report "no internet connection" on the SSID.

Details about my system:
All TP-Link Omada network. ER605 router, OC200 controller, 3x EAP225 access points, T1500G-10MPS v2.0 PoE switch, 2x TL-SG3428 managed switches.

What I have changed since installing Pi-hole:

I have "Settings/DNS/Interface Settings" to "Permit all origins" but didn't help. Not sure what to try next.

token: https://tricorder.pi-hole.net/IInniohl/

2

I think this is a router issue. Check the router settings carefully.

On one of the wireless clients, do the following to see what DNS server it is trying to use:

From the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 172.17.0.3

3

C:\Users\CK>nslookup pi.hole
Server: UnKnown
Address: 192.168.0.111

Name: pi.hole
Address: 0.0.0.0

C:\Users\CK>nslookup flurry.com
Server: UnKnown
Address: 192.168.0.111

Name: flurry.com
Addresses: ::
0.0.0.0

C:\Users\CK>nslookup flurry.com 172.17.0.3
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 172.17.0.3

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

4

Just an update...things started working fine for the last two or three days. I didn't make any changes, but my wireless devices decided to work. Until they didn't.

No changes, not even logged into the admin, and my phone dropped the wifi. Same error. "SSID has no internet access." Found my Rpi frozen.

Just rebooted the pi and it has a new IP address. Still has its old one in the DHCP reservation table. So I'm going with "sounds like a router problem" and going to try and figure this one out. But I'd appreciate any input.

Edit: Definitely a router issue. Rebooted the router and the Pi picked up its assigned IP address. I didn't see any alerts that my router had crashed, but I guess I should go looking.

In case there's anything to be found, my Pihole token is: https://tricorder.pi-hole.net/SaCR41zX/

5

Did you have any wifi problems or other problems with this setup before introducing the Pi-hole to the network?

I would be inclined to temporarily remove the Pi-hole and establish a baseline with all this kit working together correctly. There's a TP-Link guide for troubleshooting and optimising the EAP wireless. This may help reveal any underlying problems with wireless interference, range, power supplies, config errors and so on.

Once that baseline is establshed, reintroduce the Pi-hole, locate it on the network, ssh in and run the command pihole reconfigure and select Reconfigure to start over with the networking, Make sure it has a static IP, which can most simply be done by allocating one to it in whatever device is providing DHCP. As far as I know, a reconfigure won't destroy your adlists or rules that you've spent time crafting.

Now you can compare operation with the known working baseline. If you found and fixed any issues in the earlier steps, hopefully it's all behaving now. But if new issues appear, then something's not right with the way the Pi-hole is interacting with the network. In that case another debug log will help the devs to dig into the Pi-hole config and see if anything stands out.

6

I think I may have found a (the?) culprit.

"ER605 ER7206 v1 - DHCP Server May Fail With 1.2.0 and 1.2.1 Firmware [Updated on Nov 11th 2022]"

Before introducing the pihole, my network had been (seemed) rock solid for months. The occasional hiccup with finicky Google Home devices, but has been stress and maintenance free for a long time.

I'm guessing I never noticed any DHCP or IP assignment issues because they happened to other devices that weren't critical to my network functioning. (Who cares if the Roku or my kid's laptop gets the wrong IP address?), but things got funky when the Pi got introduced.

Will post a new debug log when I get a chance to mess with it, but it wont be for a few days.

7

if your wired and wireless are in a diff. subnet or LAN, then you need to create a FW rule allowing DNS port 53 between them.

8

Thanks for the suggestion, @smurf . Unfortunately (or I guess not), they are all in the same subnet.

Over the past week, I've installed, reinstalled, removed, restarted, reconfigured, etc., just about everything. Sometimes I get an internet connection, sometimes I don't. Sometimes it stays for a day, sometimes it doesn't connect at all.

I'm just going to wait for the updated ER6605 firmware before i spend anymore time trying to troubleshoot.

9

I'm using the same router ER605 FW 1.2.1. I have two separate LAN1 and LAN2
(LAN1) 192.168.0.0/24 - for wired devices
(LAN2) 172.16.0.0/24 - for wireless devices
My Pihole is on the 192.168 network. I had similar issue as you until I created a FW rule allowing LAN2 (wireless) to access LAN1 (wired) via DNS. Now they both are working.

10

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