Dns seems high
Quote from: npr it's not the network latency which is the governing factor
Well, the present variability is definitely visible in ping for me, anyway. More than that, I do not know!
[tt]Pinging 212.159.6.10 with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=30ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=25ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=4ms TTL=250
Reply from 212.159.6.10: bytes=32 time=20ms TTL=250
Ping statistics for 212.159.6.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 30ms, Average = 10ms[/tt]
Quote from: 30FTTC06 i do feel there isn't a lot to gain from maraDNS over Unbound as you say
Yes, I absolutely agree with you, 30FTTC06. Your Unbound setup seems to work extremely well, and extremely well with the Raspberry Pi. There would be no sense in using Mara instead. The comparison is interesting, though, and definitely worth doing just to see - thank you for going to all the trouble.
I had to look twice........
Nameserver Response Time (ms)
min/avg/max/stdev/retries
192.168.0.15 0.81/0.87/0.95/0.06/0
212.159.6.9 17.35/46.52/98.64/35.86/0
212.159.6.10 17.14/26.08/44.47/9.91/0
212.159.13.49 17.21/17.65/18.49/0.44/0
212.159.13.50 17.17/17.82/19.19/0.72/0
208.67.222.222 17.23/17.51/17.83/0.20/0
208.67.222.220 17.22/17.51/18.03/0.27/0
208.67.222.123 17.44/17.67/17.86/0.14/0
208.67.220.123 17.24/17.50/17.83/0.21/0
8.8.8.8 22.87/23.25/23.75/0.34/0
8.8.4.4 22.72/23.63/26.37/1.38/0
4.2.2.1 17.22/17.56/17.94/0.26/0
4.2.2.6 17.15/17.42/18.09/0.34/0
Nameserver Response Time (ms)
min/avg/max/stdev/retries
192.168.0.15 0.83/0.90/1.00/0.07/0
212.159.6.9 17.24/40.86/81.35/28.83/0
212.159.6.10 17.38/31.43/57.68/17.36/0
212.159.13.49 17.31/17.61/17.86/0.21/0
212.159.13.50 16.94/17.66/18.29/0.43/0
208.67.222.222 16.97/17.31/17.57/0.22/0
208.67.222.220 17.33/17.51/17.76/0.16/0
208.67.222.123 17.21/17.69/18.10/0.35/0
208.67.220.123 17.48/17.80/18.39/0.33/0
8.8.8.8 23.32/25.42/28.32/1.98/0
8.8.4.4 23.17/25.09/30.90/2.97/0
4.2.2.1 17.32/17.55/17.81/0.16/0
4.2.2.6 16.90/17.19/17.44/0.20/0
Quote from: 30FTTC06 [
I like the idea of it not expiring, but i'm not a big user a windows so maybe not for me, but it's another one for the pot for sure.
I'd prefer something which runs on the raspberry pi rather than on the local machine.
I'm not too good with linux so I'm struggling but "pdnsd" looks promising.
http://ubuntuforums.org/showthread.php?t=331850
Don't know if I can make it run on the pi.
Also I'm not sure if it refreshes out of date cached items in slack periods like Acrylic.
@SuperZoom
4ms pings !!!!!!!
I'm closer to 20ms.
I don't see why not npr.
pi@raspberrypi ~ $ sudo apt-get install pdnsd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
resolvconf
The following NEW packages will be installed:
pdnsd resolvconf
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 366 kB of archives.
After this operation, 776 kB of additional disk space will be used.
Do you want to continue [Y/n]?
Thanks.
It's all the other bits like config and testing that discourages me from getting on with this - All those strange linux commands.
Please let me know if you give this a try.
Before that, my next pi project is to turn it in to a wireless access point. The objective is to configure the BT fiber modem as a router and let the pi do the wireless.
It's all the other bits like config and testing that discourages me from getting on with this - All those strange linux commands.
Please let me know if you give this a try.
Before that, my next pi project is to turn it in to a wireless access point. The objective is to configure the BT fiber modem as a router and let the pi do the wireless.
I'll add it to the list npr that tutorial seems pretty good as well.
@SuperZoom I can't confirm what i'm seeing though, my sam graphs are not up to date yet.
that tutorial seems pretty good as well.@SuperZoom I can't confirm what i'm seeing though, my sam graphs are not up to date yet.
Nameserver Response Time (ms)
min/avg/max/stdev/retries
192.168.0.15 0.57/0.60/0.68/0.04/0
212.159.6.9 17.46/17.79/18.37/0.32/0
212.159.6.10 17.50/17.93/18.52/0.35/0
212.159.13.49 17.79/18.26/19.34/0.55/0
212.159.13.50 17.59/18.30/19.54/0.66/0
208.67.222.222 17.63/18.04/18.24/0.22/0
208.67.222.220 17.62/17.97/18.36/0.25/0
208.67.222.123 17.52/18.05/18.42/0.34/0
208.67.220.123 17.69/18.09/18.62/0.37/0
8.8.8.8 23.62/23.88/24.33/0.27/0
8.8.4.4 23.26/23.69/24.00/0.27/0
4.2.2.1 17.43/17.88/18.35/0.31/0
4.2.2.6 17.49/17.86/18.40/0.39/0
Nameserver Response Time (ms)
min/avg/max/stdev/retries
192.168.0.15 0.58/0.63/0.70/0.06/0
212.159.6.9 23.20/62.38/205.80/71.73/0
212.159.6.10 18.48/143.27/204.47/70.17/1
212.159.13.49 18.08/18.30/18.76/0.26/0
212.159.13.50 17.52/18.39/20.40/1.02/0
208.67.222.222 17.68/17.93/18.35/0.23/0
208.67.222.220 17.71/17.85/18.04/0.15/0
208.67.222.123 17.98/18.26/18.77/0.29/0
208.67.220.123 17.76/18.39/19.81/0.74/0
8.8.8.8 22.66/24.66/28.17/1.86/0
8.8.4.4 22.97/23.58/23.85/0.31/0
4.2.2.1 17.81/18.25/18.56/0.28/0
4.2.2.6 17.06/17.80/18.37/0.43/0
Quote from: npr my next pi project is to turn it in to a wireless access point.
Raspberry pi is the new TV for me
-_J2po3i0U
The DNS seems to be a bit more stable this morning, if significantly elevated. Pings still most jittery, though.
@npr
It was 3ms
But be not consumed by thine envy, for there are some at PlusNet Towers who wouldst have thee believe that 16ms maketh no difference to anything, and verily mine web browsing experience is in any case no better than 6Mbps ADSL at best - which is a bit carp, I think you'll agree.
It's amazing how, with the noise of xDSL removed, you can actually see what's going on from single millisecond changes, even if practically speaking the millisecond doesn't make a difference in itself - often they are an indicator of something bigger which does make a difference. My connection is incredibly stable usually, so if the ping moves from 3 -> 4 -> 5 ms, something has definitely changed. And if it jitters around all over the place there is definitely a problem.
The fact that all the other FTTP metrics are so good (or were) makes the comparatively poor browsing responsiveness the more surprising (and irksome!) How can I boast to my friends when their ADSL connections are certainly no worse? I have to focus on the fact that we can stream YouTube, Netflix, LoveFilm, iPlayer, ITV Player, 4oD, whatever Channel 5's is called etc. etc. all at the same time, no problem at all. But it's really hard to concentrate on so many video streams at once
Quote from: npr @SuperZoom
4ms pings !!!!!!!
I'm closer to 20ms.
@npr
It was 3ms
But be not consumed by thine envy, for there are some at PlusNet Towers who wouldst have thee believe that 16ms maketh no difference to anything, and verily mine web browsing experience is in any case no better than 6Mbps ADSL at best - which is a bit carp, I think you'll agree.It's amazing how, with the noise of xDSL removed, you can actually see what's going on from single millisecond changes, even if practically speaking the millisecond doesn't make a difference in itself - often they are an indicator of something bigger which does make a difference. My connection is incredibly stable usually, so if the ping moves from 3 -> 4 -> 5 ms, something has definitely changed. And if it jitters around all over the place there is definitely a problem.
The fact that all the other FTTP metrics are so good (or were) makes the comparatively poor browsing responsiveness the more surprising (and irksome!) How can I boast to my friends when their ADSL connections are certainly no worse? I have to focus on the fact that we can stream YouTube, Netflix, LoveFilm, iPlayer, ITV Player, 4oD, whatever Channel 5's is called etc. etc. all at the same time, no problem at all. But it's really hard to concentrate on so many video streams at once
Quote from: SuperZoom
@npr
It was 3ms
Envy! why should I be envious?
I've got plusnet superfast fiber which connects at 20 mbps down and 0.6mbps up -- on a good day.
Yesterday the BT speed test was showing around 6mbps down and 0.01mbps up.
