[43890] in North American Network Operators' Group
Re: Pinging Yahoo! (WAS: Getting hacked by Digital Isle?)
daemon@ATHENA.MIT.EDU (mike harrison)
Fri Oct 26 22:09:54 2001
Date: Fri, 26 Oct 2001 22:09:02 -0400 (EDT)
From: mike harrison <meuon@highertech.net>
To: "Patrick W. Gilmore" <patrick@ianai.net>
Cc: "nanog@merit.edu" <nanog@merit.edu>
In-Reply-To: <5.1.0.14.2.20011026162950.04508c88@127.0.0.1>
Message-ID: <Pine.LNX.4.10.10110262204090.32617-100000@home.highertech.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> It is interesting to note that Yahoo! presented @ NANOG a couple days ago
> they were getting XX Mbps (15? I forget) of ICMP traffic. They mentioned
> they could use this data in a decision whether to considering limiting ICMP
> (without actually saying they were considering limiting ICMP).
Ok.. I'm guilty of this as well, in fact my 'network watcher' sent
a single ping to www.yahoo.com every 15 minutes until your post.
I just turned it off.
Now, here's a real issue, many of us probably have similiar systems
that ping upstream connections and page/alert/log when there are
problems. My 'watcher' could also grab a web page (checking port 80)
or do other tests, but I have always assumed that the ping was the least
amount of traffic easily and reliably sent to check connectivity.
Whats the best way to monitor upstream connectivity for this purpose?
