Skip to main content

Uverse hell

Day one - Thursday

I got my uverse installed, install went okay, took about 5 hours to get it running. Once the tech left I switched from my Clear Wimax connection to the uverse. Looked good, then I got on the PTPP connection at work, and it started dropping me every 5-9 minutes. I called them and worked with support for 2 hours and tried lots of settings on the router. These included lowering the MTU and upping the timeout. Nothing fixed it at all, they were keeping my case open in case I wanted to call back. Then I was playing with it later on and lowered the timeout and it seemed to fix the issue. The router has a very small connection table which is a known issue, I think with the 1 day timeout there were lots of open connections which weren't being cleaned up.

Day two - Saturday

Turned on the TV to start setting up some of the DVR recordings, and the DVR wasn't working. I called ATT and the box was dead, we tried to do a factory reset and OS reload several times and the box was toast. They promptly sent out a tech a few hours later. He tried with 4 different boxes and was unable to get it working. He was there for about 3 hours, and he was out of ideas. It was 8:30PM on Saturday. He also reset my router since the TV connects to the router and uses the line that is shared.

Day Three – Sunday

I reset up the router with the same settings I had before, but I started once again to get PTPP issues and drops. I messed with it for a while and gave up again.

Day Four – Monday

I turned on the DVR, and what do you know, it started working perfectly, makes no sense to me. I called support once again on my VPN issues, I gave them my case number and they told me they don't work on VPN issues and regardless of my case and the tech I worked with I should go away. I spoke to the shift supervisor and she told me the same thing, but was nicer about it. I told them I would disconnect service if I wasn't able to use a simple VPN. They were happy to lose me as a customer, and transferred me to the disconnection line. When I got someone there, I asked them if I could have TV only, and they said I need to have internet as well. I told them I would work on it some more, and let them know if I wanted to disconnect.

We happen to have firewalls which give us SSL VPN as a free option, so one of my co-workers set it up, and it worked perfectly. No drops, and no issues. At least I have a fix for now, so I can work at home if needed.

I called customer service and got a credit for my outage time and a discounted rate for the next 6 months. All in all I've wasted about 20 hours on this mess, but glad its working now. The customer support has been good, aside from the lady who refused to help me.

Service impressions

The base 6down/512up is decent, but no better than the clear wimax service. The TV seems very good, and the DVR is better than others I have seen, but I still miss my Tivo HD XL. Nothing beats Tivo!

I wish I had my FIOS like I had back in Boston L


Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p