- Aug 25, 2001
- 56,570
- 10,202
- 126
Had an interesting happening, with a friend, that had recent signed up with Comcast, for 200Mbit/sec Blast, with a Win7 64-bit PC, connected via gigabit ethernet, either direct to modem (SB6141), or through a gigabit router (Trendnet AC1200, newest firmware).
With the old modem (SB6121), he was getting 140Mbit/s down, maxed. Then like a week later, 1Mbit/s down, suddenly. Not sure why.
Called Comcast, spoke to an L2 tech, who re-provisioned SB6121 modem.
Then he was getting a steady 35Mbit/s down. But not higher.
I hooked him up with a SB6141, which was capable of the full 200Mbit/s down. Still stuck on 35Mbit/s down.
Maybe it took 2-3 days to provision?
He got home tonight, and was having some better luck on the Comcast speedtest, but still not great.
One of the confusing things, was that it was reporting 100ms+ of latency, and IPv6 protocol, sometimes. other times, it was reporting 11ms, and IPv4.
Long and short of it was, IPv6 was UNCHECKED, under the adapter properties.
So, I figured out that the 100ms latency, was caused by a Teredo IPv6 tunnel in the background.
CHECKING IPv6 in properties, allowed the native IPv6 to work instead, and that brought the latency down on the speedtests to 15ms and IPv6.
Now he was able to actually hit 260Mbit/s down on a speedtest!
With the old modem (SB6121), he was getting 140Mbit/s down, maxed. Then like a week later, 1Mbit/s down, suddenly. Not sure why.
Called Comcast, spoke to an L2 tech, who re-provisioned SB6121 modem.
Then he was getting a steady 35Mbit/s down. But not higher.
I hooked him up with a SB6141, which was capable of the full 200Mbit/s down. Still stuck on 35Mbit/s down.
Maybe it took 2-3 days to provision?
He got home tonight, and was having some better luck on the Comcast speedtest, but still not great.
One of the confusing things, was that it was reporting 100ms+ of latency, and IPv6 protocol, sometimes. other times, it was reporting 11ms, and IPv4.
Long and short of it was, IPv6 was UNCHECKED, under the adapter properties.
So, I figured out that the 100ms latency, was caused by a Teredo IPv6 tunnel in the background.
CHECKING IPv6 in properties, allowed the native IPv6 to work instead, and that brought the latency down on the speedtests to 15ms and IPv6.
Now he was able to actually hit 260Mbit/s down on a speedtest!
Facebook
Twitter