title: Bad Checksum on TCP packets/ UDP traffic is just fine
body: <p>I know only enough about packet traffic to make a lot of very bad assumptions.  I am turning to the collective wisdom of Stackoverflow to help me out a little bit.</p>
  
  <p>Unsurprisingly, I feel that my Internet provider (lets just call them  'big cable') is blowing a bunch of smoke up my butt when it comes to solving a technical issue.</p>
  
  <p>I can only open simple web pages.  Pages loaded down with a lot of includes, large javascript libraries, big Styles Sheets, google analytics etc simply stall out.   I can see that the index.html file loads just fine using curl. </p>
  
  <p>My cable prover hooks up speedtest.net and say "See it goes just as fast as it should".</p>
  
  <p>When I open a packet sniffer however I can see that between 50% and 95% of the incoming TCP packets at any given time have a bad Checksum.   ANd when i get too high a percentage of bad checksum, my browser will timeout loading the page.  Streaming video and Voip are just fine however.</p>
  
  <p>I am making a few assumptions here that I would like to have verified.</p>
  
  <ol>
  <li>Voip, streaming video and speedtest are usually UDP packets not TCP?</li>
  <li>The reason the video loads but the web page does not is that the Checksum is not applied to UDP packets.</li>
  </ol>
  
  <p>I have come up with an analogy that I would like someone to confirm its accuracy:   It is as if FedEx was delivering my packages on time, but smashed beyond usefulness.</p>
  
  <p>Finally.  As they are using the speediest.com result to keep me stuck to my contract.  What can I do to either help them fix the mess or prove to them they in fact have a mess?</p>