Tinuva
The Magician
Ive always had a 600w pure sine inverter with 102ah battery for my internet+wifi. So wifi is never down. WFH has made this a necessity.What happens when the wifi is down, and what button do you use in the vehicle?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Ive always had a 600w pure sine inverter with 102ah battery for my internet+wifi. So wifi is never down. WFH has made this a necessity.What happens when the wifi is down, and what button do you use in the vehicle?
For this you probably don't need a pure-sine inverter since those devices' power bricks will just be converting back to DC anyway.Ive always had a 600w pure sine inverter with 102ah battery for my internet+wifi. So wifi is never down. WFH has made this a necessity.
It was a DIY solution.For this you probably don't need a pure-sine inverter since those devices' power bricks will just be converting back to DC anyway.
But out of interest which model do you have? I haven't seen a 600W one before, usually they are bigger (1.2kW is the common Mecer one on the forum, isn't it?)
House has inverter backup, but you could run the ESP8266 in AP mode so you connect to it direct.What happens when the wifi is down, and what button do you use in the vehicle?
Your default route as propagated by DNS should the IP of the pihole. Disclaimer never used pihole but from I remember it’s a gatewayI'm needing some help with pi-hole, pretty pleae. I've set it up and everything seems to be working just fine. The issue is I've got the router (Huawei B618) taking care of DHCP and have set DNS on the router to the pi-hole IP. Devices connecting to the router don't seem to be going via pi-hole though?
I believe that's what I've done. Pi-hole IP is 192.168.0.3, which is what I've set DNS to on the router. For some reason this doesn't work though. When I set DNS to 192.168.0.3 on the device (eg laptop) it works perfectly, it's just getting the router to play ball now.Your default route as propagated by DNS should the IP of the pihole. Disclaimer never used pihole but from I remember it’s a gateway
I'm needing some help with pi-hole, pretty pleae. I've set it up and everything seems to be working just fine. The issue is I've got the router (Huawei B618) taking care of DHCP and have set DNS on the router to the pi-hole IP. Devices connecting to the router don't seem to be going via pi-hole though?
Give this man a Bell's!
I'm needing some help with pi-hole, pretty pleae. I've set it up and everything seems to be working just fine. The issue is I've got the router (Huawei B618) taking care of DHCP and have set DNS on the router to the pi-hole IP. Devices connecting to the router don't seem to be going via pi-hole though?
Devices are showing the router as DNS (192.168.0.1), but pi-hole isn't registering any queries.How do they "seem" to not be going through the Pi-hole
What's come on your IPConfig on the devices getting DHCP?
Crazy thinking! Problem is it's a SOHO and the LTE router travels from time to time, so I need to keep DHCP on the router otherwise there'd be no DHCP when using the router at a secondary location.I'm not surprised really, Huawei is adamant on not supporting setting the DNS on the router itself and the hidden javascript snippet that exposed that setting was removed from future firmware versions.
Have you flushed the DNS caches ?Some devices are now working through the pi-hole, others aren't. I guess I'll leave the settings for a day or two - maybe some caches need to be refreshed or something.
Easiest route is to reboot all devices and then reboot the router for good measure to release any cached settings. But it should sort itself out in a few days if you aren't in a hurrySome devices are now working through the pi-hole, others aren't. I guess I'll leave the settings for a day or two - maybe some caches need to be refreshed or something.
Not on all the devices, but it looks like it's mostly working nowHave you flushed the DNS caches ?
Yeah, I'll give it a day or so. It's not super crucial, just handy to have. I've added a secondary DNS (cleanbrowsing's adult filter) for went the router travels.Easiest route is to reboot all devices and then reboot the router for good measure to release any cached settings. But it should sort itself out in a few days if you aren't in a hurry