IMHO.this is where you need to reduce it. Use PiHole to block Tiktok and edmw, so you can save 3 hours.
Block internet.... haha.
IMHO.this is where you need to reduce it. Use PiHole to block Tiktok and edmw, so you can save 3 hours.
IMHO.
I am trying to figure how to have a corner at my place to house all the hardware to maximize the time. Now, if i need to use tinker with mini PC or routers, I have to take out and setup. Maybe have something movable.![]()
IMHO.Maybe can consider a movable rack fitted with castor wheels and locate it in your CD shelter or aka store room.
Do take note of the heat build up though. But could be easily resolved with proper exhaust system with ducting.
Cannot la. Still need whatsapp and internet surfing access,IMHO.
Block internet.... haha.
IMHO.
CD shelter cannot because got a "kerb".
I think movable rack is the way to go. I should be using small devices, so heat should be minimal - important is that i can run many devices all at once.
Next time, if i have my own home, own BTO, I will need to set up a corner dedicated to electronics, Pi Hole, Router, NAS, switch and IOT zigbee or BT hub products. I also attempted setting up own Android TV Box using orangepi 5.
Now that cloudflare is down, not sure if its cloudflare DNS issue or also affect website hosting?
Im using own PiHole unbound own DNS. Don't see any issues with surfing websites.
Looks like IPv6 only issue. No issues with IPv4. Hopefully the issue will be resolved soon.
![]()
Singtel Fibre Broadband 5Gbps plan here.
Bash:PS C:\work\networking\ookla-speedtest-1.2.0-win64> ping challenges.cloudflare.com Pinging challenges.cloudflare.com [2606:4700::6812:5f29] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 2606:4700::6812:5f29: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PS C:\work\networking\ookla-speedtest-1.2.0-win64> ping -4 challenges.cloudflare.com Pinging challenges.cloudflare.com [104.18.94.41] with 32 bytes of data: Reply from 104.18.94.41: bytes=32 time=5ms TTL=54 Reply from 104.18.94.41: bytes=32 time=7ms TTL=54 Reply from 104.18.94.41: bytes=32 time=6ms TTL=54 Reply from 104.18.94.41: bytes=32 time=5ms TTL=54 Ping statistics for 104.18.94.41: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 7ms, Average = 5ms PS C:\work\networking\ookla-speedtest-1.2.0-win64> ping dns.cloudflare.com Pinging dns.cloudflare.com [2a06:98c1:52::8] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 2a06:98c1:52::8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PS C:\work\networking\ookla-speedtest-1.2.0-win64> ping -4 dns.cloudflare.com Pinging dns.cloudflare.com [172.64.41.8] with 32 bytes of data: Reply from 172.64.41.8: bytes=32 time=5ms TTL=54 Reply from 172.64.41.8: bytes=32 time=8ms TTL=54 Reply from 172.64.41.8: bytes=32 time=5ms TTL=54 Reply from 172.64.41.8: bytes=32 time=6ms TTL=54 Ping statistics for 172.64.41.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 8ms, Average = 6ms
i can't visit the website tooOn my side, only IPv6 is down. IPv4 is okay.
I was having brief issues accessing Downdetector.com due to IPv6 connection issues with "challenger.cloudflare.com".
Yeah, Downdetector was inaccessible in the Speedtest app earlier when I wanted to check if the Singtel disruption still persist or has it recovered.On my side, only IPv6 is down. IPv4 is okay.
I was having brief issues accessing Downdetector.com due to IPv6 connection issues with "challenger.cloudflare.com".
I would register it as a client and set the option to temporary disable the blocklist for this specific client.i need to fix, is my Sony TV is unable to connect to server and update software
This seems like a very agressive list that you are using. Are you also using browser based adblock?HWZ cannot see FB embedded posts
Oh thanks. Didn't think of this way, will try it next time.I would register it as a client and set the option to temporary disable the blocklist for this specific client.
i vaguely remember pihole got such option. Once updated, then resume the block and go search for the domain
Yup. I am also using Brave Browser which also blocks ads, trackers and more.This seems like a very agressive list that you are using. Are you also using browser based adblock?
You might want to keep things simpler and only use only 1 list from this 2 providers
- oisd big from https://oisd.nl/
- HaGeZi multi pro from https://github.com/hagezi/dns-blocklists
Then maybe add on security list
- Malicious URL Blocklist (URLHaus)
- HaGeZi's Threat Intelligence Feeds - This one is huge! If pi hole system is on SD card, i won't reccomend it
If so, i would check if it's the built in blocker list that causing issue bah. Ttry using edge or chrome without any adblock and see if the same post can access or not since sometimes, the list used by the browser itself can be too agressive and out of your control.I am also using Brave Browser which also blocks ads, trackers and more.
Likely, but i won't just dismiss using SD Card since any storage can fail also randomlyYes, my pi-hole system is on a SD-card, so having lots of list will also risk having more failures right? Cos they have to write and re-write many times?
thanks for the help. I'll try.If so, i would check if it's the built in blocker list that causing issue bah. Ttry using edge or chrome without any adblock and see if the same post can access or not since sometimes, the list used by the browser itself can be too agressive and out of your control.
Sometimes can also be just a cache problem. Too much data / history on the browser and things get messed up
Likely, but i won't just dismiss using SD Card since any storage can fail also randomly
Quries are really only read operations, is the writes that may kill it like these jobs.
- Updating of the list (PI defaults to once a week on sat or sun which should be decent enough if you don't need constant chasing of the latest blockings)
- Logging (See if can switch to ram logging or similar eitherwise log only block queries)
- Increase your caching for the quries that has already been done (reduce search and then cache operation)
Having more list will result in slower operations, but even so, quries should be done in miliseconds with decent caching size.
![]()
![]()
I don't use pihole already but those are my list that i used on my rpi4 and another mini pc at ~800k entries. Both are on SSD, sata and nvme.
Previously only 1 rpi4 on SD card, also was avg 30-40ms without the threat feeds for 4 years. Then the SD card died when i was at work and family no internet![]()