On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
We use CDMA clocks and last leap second it took weeks for all of the
cell sites to adjust the last one. As a result, I have set all of our
clocks for manual leap second and set them to adjust tonight at
midnight
(UTC).I'll take a look in about
On Mon, 16 Mar 2009, Leo Bicknell wrote:
What appears to happen is vendors don't auto-size queues. Something
In my mind, the problem is that they tend to use FIFO, not that the queues
are too large.
This is most likely due to the enormous price competition in the market,
where you might
* Marian Ďurkovič:
TCP window autotuning is part of several OSs today. However, the actual
implementations behind this buzzword differ significantly and might impose
negative side-effects to our networks - which I'd like to discuss here.
There seem to be two basic approaches which differ
On Tue, Mar 17, 2009 at 1:07 AM, Ask Bjørn Hansen a...@develooper.comwrote:
On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
We use CDMA clocks and last leap second it took weeks for all of the
cell sites to adjust the last one. As a result, I have set all of our
clocks for manual leap
On Mon, Mar 16, 2009 at 09:09:35AM -0500, Leo Bicknell wrote:
Many edge devices have queues that are way too large.
What appears to happen is vendors don't auto-size queues. Something
like a cable or DSL modem may be designed for a maximum speed of
10Mbps, and the vendor sizes the queue
On Mon, Mar 16, 2009 at 10:48:42PM -0500, Frank Bulk - iName.com wrote:
It was my understanding that (most) cable modems are L2 devices -- how it is
that they have a buffer, other than what the network processor needs to
switch it?
The Ethernet is typically faster than the upstream cable
From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= a...@develooper.com
Date: Mon, 16 Mar 2009 23:07:42 -0700
On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
We use CDMA clocks and last leap second it took weeks for all of the
cell sites to adjust the last one. As a result, I have set all of
In a message written on Tue, Mar 17, 2009 at 08:46:50AM +0100, Mikael
Abrahamsson wrote:
In my mind, the problem is that they tend to use FIFO, not that the queues
are too large.
We could quickly get lost in queuing science, but at a high level you
are most correct that both are a problem.
Out of interest, is there a report that details the number of unused older
AS's in the Internet and what is being done to recover them to recycle, as
we approach the 53k mark and the 32 bit numbering scheme, it strikes me that
we probably have a lot of stagnant AS's out there due to takeovers
On Mar 17, 2009, at 11:47 AM, Simon Brilus wrote:
Out of interest, is there a report that details the number of unused
older AS's in the Internet and what is being done to recover them to
recycle, as we approach the 53k mark and the 32 bit numbering
scheme, it strikes me that we probably
Or use a transmission-layer protocol that optimizes delay end-to-end.
http://tools.ietf.org/html/draft-shalunov-ledbat-congestion-00
On 2009Mar17, at 12:47 PM, Joe Maimon wrote:
Leo Bicknell wrote:
TCP needs drops to manage to the right speed.
This is whats bad. TCP should be slightly more
On Tue, 17 Mar 2009 08:06:51 PDT, Kevin Oberman said:
Routers as ntp servers. Yuck! Routers route well, but they treat time as
a low priority job and jitter on Cisco routers is simply terrible.
Junipers do better, but are still a poor time server.
They may suck for being a Stratum-1/2 server,
On Tue, 17 Mar 2009, valdis.kletni...@vt.edu wrote:
They may suck for being a Stratum-1/2 server, but even the most jittery
Cisco is still far and away good enough to serve up a ntpdate so that an
end-user PC-class machine is in the right minute.
As long as the end-user is made aware that
On Tue, 17 Mar 2009, Joe Maimon wrote:
TCP needs drops to manage to the right speed.
This is whats bad. TCP should be slightly more intelligent and start
considering rtt jitter as its primary source of congestion information.
TCP Vegas did this but sadly it never became popular.
(It doesn't
As long as the end-user is made aware that the accuracy of said NTP
clock
is +/- 30.000 seconds (or whatever jitter might exist). Seems kind
of
ridiculous to use an NTP source that is, for many purposes, wildly
inaccurate. For my purposes, wildly is more than +/- 0.1 seconds.
This 100-line document contains 62% of what you need to know to avoid
annoying 10,000 people in your email to the NANOG list. It also contains
pointers to another 23%. Please take 5 minutes to read it before
you post [again].
General Information
===
About NANOG:
I have already tried calling +1-310-215-1001 which is not in service as
well as emailing peer...@myspace.com and n...@myspace.com and checking
peeringdb.com for any other contact info.
Thanks
Leslie Carr
Craigslist
also at 415/566-6394 x140
On 2009-3-17, at 12:10, Tony Finch wrote:
On Tue, 17 Mar 2009, Joe Maimon wrote:
TCP needs drops to manage to the right speed.
This is whats bad. TCP should be slightly more intelligent and start
considering rtt jitter as its primary source of congestion
information.
TCP Vegas did this
EBD Date: Wed, 18 Mar 2009 00:13:48 + (GMT)
EBD From: Edward B. DREGER
Many thanks to all who have responded. I think/hope I have enough
information now!
Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman Dreger, Inc. - http://www.brotsman.com/
Bandwidth,
https://mgmt.hep.caltech.edu/routeproxy
Jason Lewis wrote:
This brings up something I've been thinking about. Are there any free
services that let you submit an IP and get traces back from multiple
geographic locations?
There are plenty of internet measurement projects, but none of them
Anyone having issues with speakeasy dsl connectivity?
On Mar 17, 2009, at 9:38 PM, John Martinez wrote:
Anyone having issues with speakeasy dsl connectivity?
Supposedly they're having a national outage.
--
TTFN,
patrick
I currently have partial connectivity to the Internet through speakeasy.
Sent from my iPhone
On Mar 17, 2009, at 9:38 PM, John Martinez jmarti...@zero11.com wrote:
Anyone having issues with speakeasy dsl connectivity?
Our speakeasy t1 in palo alto was out for approx. 40 minutes. Service
is back as of now.
Andrew MacLeod
Network Operations Manager
Etheric Networks
877.541.3905
Sent from my iPhone
On Mar 17, 2009, at 18:43, Dan Snyder sliple...@gmail.com wrote:
I currently have partial connectivity to the
24 matches
Mail list logo
