4 ms·

1. You’re totally right about that, but I couldn’t find one as easily 2. I was initally hesitant about using WiFi for DNS, but after reading comments it seemed

1. You’re totally right about that, but I couldn’t find one as easily 2. I was initally hesitant about using WiFi for DNS, but after reading comments it seemed that no one really had any issues. Mine has been kicking for 6 months sitting right next to my router without any noticeable delays, so I think it’s okay.

sgbeal 1y ago
> I was initally hesitant about using WiFi for DNS, but after reading comments it seemed that no one really had any issues FWIW, that was also an initial concern of mine. Almost three years later, i've never once had an issue with running my pi-hole over wifi.
- tonymet 1y ago
  You're right it's usable, though DNS is the most critical service to have low latency. on good wifi with no interference you can get good 2ms avg and 0.2-0.4 ms SD ping distribution. ethernet will have 0.2 ms avg and 0.01 SD it's the outliers that will cause headaches, when there is radio interference. wifi is a dynamic system with every base station migrating bands for interference.
  - sgbeal 1y ago
    > on good wifi with no interference you can get good 2ms avg and 0.2-0.4 ms SD ping distribution. i opine that there's no _functional_ difference between those speeds for purposes of a home LAN. Both values are far below humans' ability to perceive the difference.
    - tonymet 1y ago
      i agree, but you won't know until you test. ethernet results are extremely consistent across applications, assuming there isn't a bad cable. wifi can vary wildly by 10000 factor even in the same location on different days
tonymet 1y ago
it's mostly fine, only edge cases. with original zero W and 2.4ghz radio, microwaves were real interference. I mostly used USB as an experiment and I didn't know what else to do with the regular-zero Very cool how a $5 board could work so well! I was glad to see your post.

4 ms·

1. You’re totally right about that, but I couldn’t find one as easily 2. I was initally hesitant about using WiFi for DNS, but after reading comments it seemed

by perdomon 1y ago

sgbeal 1y ago
> I was initally hesitant about using WiFi for DNS, but after reading comments it seemed that no one really had any issues FWIW, that was also an initial concern of mine. Almost three years later, i've never once had an issue with running my pi-hole over wifi.
- tonymet 1y ago
  You're right it's usable, though DNS is the most critical service to have low latency. on good wifi with no interference you can get good 2ms avg and 0.2-0.4 ms SD ping distribution. ethernet will have 0.2 ms avg and 0.01 SD it's the outliers that will cause headaches, when there is radio interference. wifi is a dynamic system with every base station migrating bands for interference.
  - sgbeal 1y ago
    > on good wifi with no interference you can get good 2ms avg and 0.2-0.4 ms SD ping distribution. i opine that there's no _functional_ difference between those speeds for purposes of a home LAN. Both values are far below humans' ability to perceive the difference.
    - tonymet 1y ago
      i agree, but you won't know until you test. ethernet results are extremely consistent across applications, assuming there isn't a bad cable. wifi can vary wildly by 10000 factor even in the same location on different days
tonymet 1y ago
it's mostly fine, only edge cases. with original zero W and 2.4ghz radio, microwaves were real interference. I mostly used USB as an experiment and I didn't know what else to do with the regular-zero Very cool how a $5 board could work so well! I was glad to see your post.