Your Raspberry Pi Projects

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.
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?)
 
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?)
It was a DIY solution.

This is the inverter: https://www.brights.co.za/product/inverter-pure-sine-wave-ups-type/
Select 600w and 12v to see it. Its made by ACDC. Bought a battery trolley and mounted the inverter on top. Works a treat still years later. Even though I have installed solar now, I still have this for wifi/internet in case the main house inverter goes offline.
 
What happens when the wifi is down, and what button do you use in the vehicle?
House has inverter backup, but you could run the ESP8266 in AP mode so you connect to it direct.

Don't use a button, I use my phone. But if you want a button, you could use a 433mhz button and a RF receiver.
 
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?
 
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?
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
 
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 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.
 
How do they "seem" to not be going through the Pi-hole

What's come on your IPConfig on the devices getting DHCP?
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?
 
How do they "seem" to not be going through the Pi-hole

What's come on your IPConfig on the devices getting DHCP?
Devices are showing the router as DNS (192.168.0.1), but pi-hole isn't registering any queries.

Router is 192.168.0.1, Pi-hole is 192.168.0.3. Router is now set to use 192.168.0.3 as DNS (using the link provided by @Anthro above) but still no joy. I'm pretty convinced the issue is on the router side.
 
I have my Billion router set as the DHCP server, with all devices - including my Pi-Hole server - acquiring their IP addresses from the router.

They also all use the router's primary DNS server: there is no secondary DNS server.

All devices are also set to target the Pi-Hole server as a primary DNS server: once again there is no secondary DNS server.

The Pi-Hole server also runs CloudFlared, so I use a custom #1 DNS setting of 127.0.0.1#5053
 
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.
 
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.
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.
 
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.
 
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.
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 hurry
 
Have you flushed the DNS caches ?
Not on all the devices, but it looks like it's mostly working now

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
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.
 
I'm a bit late to the PI party, just bought myself a Raspberry Pi Model 4 - 4GB. Currently running Nxfilter as a DNS sinkhole, and running the 3CX PABX system for all my VOIP phones in the house. Works like a charm.
 
Top
Sign up to the MyBroadband newsletter
X