Hi,
Anyone on here using Charter Telephone VOIP service? I've currently
got Verizon, but the wife hates it because our phone lines get flaky
all the time, esp when it rains.
So I'm thinking to save money and combine all my stuff onto Charter.
I've already got High Speed internet and regular old cable. Not wild
about Digital Cable since I'm happy with Tivo and I don't want yet
another set top box to have to deal with...
So, any horror stories about Charter Phone VOIP quality and service?
Thanks,
John
On recomendation from someone on this list,
I signed up for Speakeasy DSL. The helped
me set up a primary name server (DNS) and
they ran a secondary name server for a few
extra dollars per month. This has been
working well for about a decade.
Speakeasy was sold to MegaPath, who yesterday
sent me a message that included this:
> Dear MegaPath Customer,
>
> This email is to advise you that MegaPath is
> migrating its legacy Speakeasy ISP, web hosting,
> webmail and DNS services to a more advanced platform.
>
> <Braindead "customer-experience"
> happy market-talk deleted>
>
> Going forward, we will no longer support secondary
> DNS services. If your domain is set up in this
> manner, please be sure to make the proper changes to
> avoid a post-migration service disruption.
This all happens next Tuesday.
I read this is "We are breaking what has worked
for a decade, there is nothing you can do,
have fun finding a new ISP in two days."
I was wall-punching cursing mad.
When I calmed down a bit I began to think, if they
don't break anything else, maybe it's not so bad. The
system was designed to tolerate failure. _I_ was not
designed to tolerate _intentional_ failure, but
everything should still work if the secondary name
server is broken.
Since I have only one IP address on one DSL line,
I never really saw the need for a secondary server
in the first place. I run a primary server because
(A) I like to think of myself as a programmer,
and it is self education to figure out how to
do it.
(B) Sometimes I create subdomains and run test
program servers in them.
The RFC's require a second name server, and
the registrar asks for it, but who's going to
care really? If the primary name server goes
out, so do all other servers in the domain,
since it's all really just one computer.
What would you recommend?
If anyone else has the same problem, I could
be your secondary, and you could be mine.
-- Keith
This is a paper about High Frequency Trading, it's an interesting if not
entirely terrifying read about what a crazy place the markets have become.
http://queue.acm.org/detail.cfm?id=2536492
Tim.
--
I am leery of the allegiances of any politician who refers to their
constituents as "consumers".
Just so people know... this is how to change the scheduler on Ubuntu 13.04.
tc qdisc replace dev eth0 root fq_codel limit 100 target 5ms interval 30ms
ecn
Obviously replace "eth0" with your appropriate network device...
Enjoy,
Tim.
--
I am leery of the allegiances of any politician who refers to their
constituents as "consumers".
Hi folks,
The next Worcester Linux Users' Group (WLUG) meeting will be held this
Wednesday. This month we will have Jim Gettys from Bell Labs talk
about Internet buffer bloat. This is the talk that has been
rescheduled from April.
Note that there has been a room change to a larger room right down the
hall from our regular location.
Wednesday, October 9, 7:00 - 9:00 PM
WPI Campus Center, Hagglund Room 301
The Campus Center is building #7 on the campus map [1], and the
Hagglund Room is room 301 on the Campus Center building floorplan [2].
[1] http://www.wpi.edu/about/visitors/campusmap.html
[2] http://www.wpi.edu/Admin/CC/Floorplans/37678.htm
"Internet buffer bloat, by Jim Gettys (Bell Labs)
VOIP and teleconferencing often perform much more poorly on today's
Internet than the Internet of a decade ago, despite great gains in
bandwidth. Lots of fiber, cheap memory, smart hardware, variability of
wireless goodput, changes in web browser behaviour, changes in TCP
implementations, and a focus on benchmarking Internet performance
solely by bandwidth, and engineer's natural reluctance to drop packets
have conspired to encourage papering over problems by adding buffers;
each of which may introduce latency when filled.
The mistaken quest to never drop packets has destroyed interactivity
under load, and often results in actual higher packet loss, as TCP's
congestion avoidance algorithms have been defeated by these
buffers. The lessons of the "RED manifesto" of 1997 have been
forgotten or never learned by a new generation of engineers."
Wednesday, October 9, 7:00 - 9:00 PM
WPI Campus Center, Hagglund Room 301
Afterwards, we will go out for pizza.
See you there,
Chuck
President, Worcester Linux Users' Group
http://www.wlug.org/
Hi folks,
The next Worcester Linux Users' Group (WLUG) meeting will be held at
its regularly scheduled time: the 2nd Wednesday of the month, which is
Wednesday, October 9, at 7PM. The location will be the WPI Campus
Center, Mid-Centry Room 331.
This month we will have Jim Gettys from Bell Labs talk about Internet
buffer bloat. This is the talk that has been rescheduled from April.
"Internet buffer bloat, by Jim Gettys (Bell Labs)
VOIP and teleconferencing often perform much more poorly on today's
Internet than the Internet of a decade ago, despite great gains in
bandwidth. Lots of fiber, cheap memory, smart hardware, variability of
wireless goodput, changes in web browser behaviour, changes in TCP
implementations, and a focus on benchmarking Internet performance
solely by bandwidth, and engineer's natural reluctance to drop packets
have conspired to encourage papering over problems by adding buffers;
each of which may introduce latency when filled.
The mistaken quest to never drop packets has destroyed interactivity
under load, and often results in actual higher packet loss, as TCP's
congestion avoidance algorithms have been defeated by these
buffers. The lessons of the "RED manifesto" of 1997 have been
forgotten or never learned by a new generation of engineers."
Wednesday, October 9, 7:00 - 9:00 PM
WPI Campus Center, Mid-Centry Room 331
Afterwards, we will go out for pizza.
See you there,
Chuck
President, Worcester Linux Users' Group
http://www.wlug.org/