Pi-Hole: No Internet on Wifi, but wired works
I set up a pi-hole on a Raspberry Pi 4 and am running my home network with an ER605 router, OC200 controller, 3 Omada access points (EAP225), and a few Omada switches (PoE T1500G-10MPS, 2x TL-SG3428).
Everything works well for my wired clients, but none of the APs deliver an internet connection. All of my phones and tablets can connect to the SSID, but all get the "Connected, but no internet" error. I'm obviously missing 'something' basic, but no idea what it is.
In the controller, I set the IP of the Pi-hole under LAN DNS, rebooted the system, and thats working since my wired clients all work and block ads. Its just the wifi that is failing. I'm not running any VLANs, and my ER605 is the DHCP server.
On the Pi, I have "permit all origins" selected in Settings, but otherwise running default.
What am I missing?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Do you have som EAP ACL enabled or have you enabled Guest network on SSID.
there is no other reason that WiFi don't work against Pi-Hole as I see.
- Copy Link
- Report Inappropriate Content
Thanks for the reply. Sorry for the delayed response, but I didn't get a notification. Anyhoo....
I had a guest network, but its a different, and uniquely named SSID.
And I have no gateway, switch, or EAP ACL rules.
- Copy Link
- Report Inappropriate Content
if pi-hole works with wired devices I don't see any reason why wifi doesn't work if it's on the same vlan, can you ping the pi-hole server when you is connected to wifi?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
ok, no ACL no guest network activated on SSID, same vlan as wired network, you can ping pi-hole, then it should work. so from what I know, there is not much more I can help with unfortunately. I've used pi-hole myself and it's quite simple things.
have you tried the pi-hole forum on reddit?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
yes, it seems quite strange, I've used pi-hole here without problems, but I don't have EAP225, but there could be something with these access points that causes problems,
you can hope that someone from tp-link are responding to this thread and that they know something about this problem.
- Copy Link
- Report Inappropriate Content
So strangely, things just started to work for a few days. Until they didn't. Both with no changes to my setup.
This afternoon, my mobile devices suddenly lost internet connections on their SSID again. I checked the Pi and thought it was frozen, so I rebooted.
When it restarted, it didn't take the IP address reserved for it in the DHCP reservation table. Very odd. It just picked up an open IP in the range (192.168.0.49).
I couldn't get the pi to release its lease, and didn't feel like starting to troubleshoot, so I went to change the DNS in my ER605 back to 1.1.1.1.
While I was there, I deleted the entry in the DHCP reservation table for the Pi and recreated it with its original reservation (192.168.0.111)
When I rebooted the ER605, the Pi re-accepted its reserved IP address (0.111)
I guess I need to check the Pi and its network settings. I don't have wifi enabled on it, so its not like the wifi network interface should be causing an IP conflict.
I'm totally stumped.
- Copy Link
- Report Inappropriate Content
There are a lot of errors and problems with DHCP on TP-Link routers, look at this post.
https://community.tp-link.com/en/business/forum/topic/581548
- Copy Link
- Report Inappropriate Content
I found that thread last night. I wish there was some way of confirming that was the issue rather than just assuming, but for the time being, I'm willing to accept it. I'll keep monitoring the firmware fixes until it gets ironed out.
I presume I had lots of devices getting their wrong reserved IP addresses, but the network didn't crash because of it. C'est la vie.
Thanks for your help. Much appreciated.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1743
Replies: 10
Voters 0
No one has voted for it yet.