From nweaver at ICSI.Berkeley.EDU Wed Jan 13 07:32:38 2010 From: nweaver at ICSI.Berkeley.EDU (Nicholas Weaver) Date: Wed, 13 Jan 2010 07:32:38 -0800 Subject: [Netalyzr] We are now out of beta! Message-ID: We are out of beta! We have been toiling hard to implement new tests, make the existing ones more robust, and improve the user interface. Among the changes we are rolling out today are: * New tests. We now provide a path MTU test, IP fragmentation support, improved DNS examination, and look up additional names. Besides the client-side transcript you can now inspect the server-side one, which is useful for debugging highly troubled sessions. In addition, we have improved the overall robustness of the existing tests. * Interface improvements. A frequent complaint we received was that the results summary is overwhelming. As a first step to improve the situation, you can now selectively show or hide result summary detail. On the summary page, you find clickable plus/minus symbols that will expand/collapse test results on the entire page, in a particular test class, or on a particular test. When you first arrive at the summary page, any issues we have noticed remain expanded by default. * Updated info pages. Each of our tests comes with an info page, available by clicking on the test's name (such as "Path MTU" in the above). We have given those info pages a makeover, which will hopefully make them easier to understand and more useful to less technical users. We are also using this opportunity to try to get people to run or rerun Netalyzr, at http://netalyzr.icsi.berkeley.edu , in order to see how much the network has changed since our beta release during the summer. Thanks again for running Netalyzr -The Netalyzr Crew: Christian, Nick, and Vern. From zehn.cao at gmail.com Fri Jan 15 21:55:06 2010 From: zehn.cao at gmail.com (Zhen Cao) Date: Sat, 16 Jan 2010 13:55:06 +0800 Subject: [Netalyzr] DNS latency threshold Message-ID: Hi Netalyzr Contributors and All, I'd like to know what's DNS latency threshold in Netalyzr. In one test, I got a DNS lookup latency of 770ms and it reported "Your ISP's DNS server is slow to lookup names". In another test, I got 740ms and did not see that warning. Did you set a threshold between 740ms and 770ms and why? Thanks, Zhen From nweaver at ICSI.Berkeley.EDU Fri Jan 15 21:59:28 2010 From: nweaver at ICSI.Berkeley.EDU (Nicholas Weaver) Date: Fri, 15 Jan 2010 21:59:28 -0800 Subject: [Netalyzr] DNS latency threshold In-Reply-To: References: Message-ID: <93CC1BD8-76FA-46BC-B0F8-8E2E1EAF5747@icsi.berkeley.edu> 750. And we set a threshold simply because we don't have gradiants: either it raises an alert or not, so we have to pick a number that is somewhat sensible. On Jan 15, 2010, at 9:55 PM, Zhen Cao wrote: > Hi Netalyzr Contributors and All, > > I'd like to know what's DNS latency threshold in Netalyzr. In one > test, I got a DNS lookup latency of 770ms and it reported "Your ISP's > DNS server is slow to lookup names". In another test, I got 740ms and > did not see that warning. Did you set a threshold between 740ms and > 770ms and why? > > Thanks, > Zhen > _______________________________________________ > Netalyzr mailing list > Netalyzr at mailman.ICSI.Berkeley.EDU > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/netalyzr From zehn.cao at gmail.com Fri Jan 15 22:16:59 2010 From: zehn.cao at gmail.com (Zhen Cao) Date: Sat, 16 Jan 2010 14:16:59 +0800 Subject: [Netalyzr] DNS latency threshold In-Reply-To: <93CC1BD8-76FA-46BC-B0F8-8E2E1EAF5747@icsi.berkeley.edu> References: <93CC1BD8-76FA-46BC-B0F8-8E2E1EAF5747@icsi.berkeley.edu> Message-ID: Thanks for the reply. Another question followed: which DNS is under test? I am configuring my DNS at 8.8.8.8 (google public dns), but the analysis result indicates that "Your NAT has a built in DNS proxy. The DNS request was received from 211.99.129.210". So the DNS performance in done between my NAT box and the outside internet? And when i am accessing the web, i checked that the DNS response is actually received from the 8.8.8.8. Thanks for the help. On Sat, Jan 16, 2010 at 1:59 PM, Nicholas Weaver wrote: > 750. ?And we set a threshold simply because we don't have gradiants: either it raises an alert or not, so we have to pick a number that is somewhat sensible. > > > > On Jan 15, 2010, at 9:55 PM, Zhen Cao wrote: > >> Hi Netalyzr Contributors and All, >> >> I'd like to know what's DNS latency threshold in Netalyzr. In one >> test, I got a DNS lookup latency of 770ms and it reported "Your ISP's >> DNS server is slow to lookup names". In another test, I got 740ms and >> did not see that warning. Did you set a threshold between 740ms and >> 770ms and why? >> >> Thanks, >> Zhen >> _______________________________________________ >> Netalyzr mailing list >> Netalyzr at mailman.ICSI.Berkeley.EDU >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/netalyzr > > From nweaver at ICSI.Berkeley.EDU Sat Jan 16 07:16:54 2010 From: nweaver at ICSI.Berkeley.EDU (Nicholas Weaver) Date: Sat, 16 Jan 2010 07:16:54 -0800 Subject: [Netalyzr] DNS latency threshold In-Reply-To: References: <93CC1BD8-76FA-46BC-B0F8-8E2E1EAF5747@icsi.berkeley.edu> Message-ID: <8F560444-8CE1-4D17-B1FB-0F274A129DEB@ICSI.Berkeley.EDU> On Jan 15, 2010, at 10:16 PM, Zhen Cao wrote: > Thanks for the reply. > > Another question followed: which DNS is under test? > > I am configuring my DNS at 8.8.8.8 (google public dns), but the > analysis result indicates that "Your NAT has a built in DNS proxy. The > DNS request was received from 211.99.129.210". So the DNS performance > in done between my NAT box and the outside internet? > > And when i am accessing the web, i checked that the DNS response is > actually received from the 8.8.8.8. > > Thanks for the help. Actualyl, we test Multiple DNS 'things': Most tests are through the recursive resolver you set (so in this case, google public DNS), however, the IP we report for it in the server identification test is not the IP you use, as many of these DNS setups are clusters, so your request goes to one IP, it gets bounced around internally, and comes out to our server using a different IP. But we also do low level tests that check other things. EG, the applet sends a message to what it guesses is your NAT, to see if your NAT also acts as either a DNS server or forwarder (most do, and we'd like to know the percentage, because some of these are broken and causing havoc with various issues.). And we also send a series of messages directly to our server to make sure that direct DNS access is blocked by the network. > > On Sat, Jan 16, 2010 at 1:59 PM, Nicholas Weaver > wrote: >> 750. And we set a threshold simply because we don't have gradiants: either it raises an alert or not, so we have to pick a number that is somewhat sensible. >> >> >> >> On Jan 15, 2010, at 9:55 PM, Zhen Cao wrote: >> >>> Hi Netalyzr Contributors and All, >>> >>> I'd like to know what's DNS latency threshold in Netalyzr. In one >>> test, I got a DNS lookup latency of 770ms and it reported "Your ISP's >>> DNS server is slow to lookup names". In another test, I got 740ms and >>> did not see that warning. Did you set a threshold between 740ms and >>> 770ms and why? >>> >>> Thanks, >>> Zhen >>> _______________________________________________ >>> Netalyzr mailing list >>> Netalyzr at mailman.ICSI.Berkeley.EDU >>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/netalyzr >> >> >