- Joined
- Nov 16, 2004
I have a situation that is on going with an ISP. Right now I have Wireshark set up and configure to show me "tcp.analysis.lost_segment". Which to my understanding is essentially lost packets. My reasoning for doing so is I have an issue on going with this ISP... we had slow speeds for the last month since we moved into a new location and just yesterday we were able to rectify having inconsistent, slow speeds. Before we were bottoming out as low as 560kbps. YES, KBPS! However after resolving that issue, I still notice there is a lot of "packet jitter" when the system is under load. Typically when I run speed tests I see this consistently.
The Internet is -usable- for the time being, but there are still moments when files take a long time to download, web pages refuse to load, and overall general connectivity is not what it should be. They do a straight fiber test between our location and theirs (about 3.5 miles) and they claim the connection is 100% solid, stable, and that we are receiving 95/95 mpbs for download and up. This isn't the case though when trying to access the actual outside Internet. They won't escalate me to engineers and simply aren't giving me the time and day anymore since I've called them everyday for two weeks now.
I have been fighting with this ISP and there is zero accountability on their end. I need a way to prove that we are losing these packets and that it is their fault. I'm not quite sure what showing them a long list of packet loss in WireShark will accomplish, but it is all I could think of try to at least verify that reports from speedof.me and DSLReports.com were indeed correct when reflecting how unstable the connection was testing. DSLReports is by far my favorite test as it shows "bufferbloat" which is essentially the same thing as packet loss.
I have a port accessible on the switch for pure speed tests, but that port tests incredibly poor. Right now I get somewhat OK results testing from behind the firewall we have configured (90mbps down, 30 mbps up).
Just not sure where to go from here and I'm not in the mood to battle with them again until I have something 100% definitive to throw in their face. The tech that was out here yesterday saw ONE test run at 90/90 and he ran out the door.
The Internet is -usable- for the time being, but there are still moments when files take a long time to download, web pages refuse to load, and overall general connectivity is not what it should be. They do a straight fiber test between our location and theirs (about 3.5 miles) and they claim the connection is 100% solid, stable, and that we are receiving 95/95 mpbs for download and up. This isn't the case though when trying to access the actual outside Internet. They won't escalate me to engineers and simply aren't giving me the time and day anymore since I've called them everyday for two weeks now.
I have been fighting with this ISP and there is zero accountability on their end. I need a way to prove that we are losing these packets and that it is their fault. I'm not quite sure what showing them a long list of packet loss in WireShark will accomplish, but it is all I could think of try to at least verify that reports from speedof.me and DSLReports.com were indeed correct when reflecting how unstable the connection was testing. DSLReports is by far my favorite test as it shows "bufferbloat" which is essentially the same thing as packet loss.
I have a port accessible on the switch for pure speed tests, but that port tests incredibly poor. Right now I get somewhat OK results testing from behind the firewall we have configured (90mbps down, 30 mbps up).
Just not sure where to go from here and I'm not in the mood to battle with them again until I have something 100% definitive to throw in their face. The tech that was out here yesterday saw ONE test run at 90/90 and he ran out the door.