2 ms·
> 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 conce
by 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 agoYou'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 agoi 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