I keep getting the message LAN cable disconnected on my wired ps4 connection, then a moment later it connects.
I connected my laptop with a short ethernet cable direct to my modem/router and tested with sourceforge speedtest and pingplotter. This is BT Infinity with a Netgear D7000 modem/router, tested with different cables
You have a small amount of packet loss (1.3%). Usually anything under 5% would not be very noticable in general browsing as TCP is designed to deal with such issues, however gaming (e.g. your PS4) and streaming will be likely be affected here. This could indeed be an issue with your line.
That being said, I don't have a PS4 but "LAN cable disconnected" implies there is a problem with the ethernet connection rather than the internet. I wouldn't expect to see a message like that just because of packet loss. Have you got another router you can try, e.g. your original HH, to rule out the internal switch on the Netgear?
Also, do you have any noise on your line if you perform a quiet test? (Dial 17070)
Thanks, I just dug out my BT Homehub 5 from the loft and plugged that in. Same situation, only the homehub and a short cat 6 to my laptop. This time there were no red bars on pingplotter but the sourceforge speed test results were slightly worse (I'd use pingtest.com but it doesnt like my java for some reason) and latency to the router of about 1.5ms. Just out of interest I also tried it with my laptop where my PS4 is (router > 25m cat 6 cable > switch > 1m cat 6 > ps4) and the latency to the router is up at 3.8ms with 60% packet loss.
I tried the quiet line and I do hear the odd rustling sound every few seconds, very faint to the point I was unsure if it was just my ear rubbing against the headset but it is there.
Hi, not entirely sure what my TCP/MTU/TTL settings should be but here is my results:
« SpeedGuide.net TCP Analyzer Results »
Tested on: 2017.03.26 09:34
IP address: 86.174.xxx.xxx
Client OS/browser: Windows 10 (Chrome 56.0.2924.87)
TCP options string: 020405a80103030801010402
TCP Window: 66560 (NOT multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 260
Recommended RWINs: 63712, 127424, 254848, 509696, 1019392
BDP limit (200ms): 2662kbps (333KBytes/s)
BDP limit (500ms): 1065kbps (133KBytes/s)
MTU Discovery: ON
IP ToS: 01001000 (72)
Precedence: 010 (immediate)
Delay: 0 (normal delay)
Throughput: 1 (high throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DSCP (DiffServ): AF21 010010 (18) - Assured Forwarding class 2, low drop precedence (RFC 2597).
I repeated my earlier tests with wifi only 1 metre from the hub. The hub is connected directly to the mains. It seemed to give better ping on the first test but pingplotter results are way worse.
Not sure if you meant wired or wireless so I did both 🙂 First pic wired 2nd wireless, both right next to the home hub.
The wireless result is a little odd as it looks like you're going via another router or access point (with a 192.168.88 address). Is that the case?
Either way, from that last ethernet result it's clear that the homehub has some rate limiting of ICMP traffic (where the TTL is 0, which is why we don't see it when tracing to the router directly) - that explains why it previously appeared you were getting packet loss at hop 1. The 1.9ms average latency to the router over a single ethernet cable isn't great, but I don't think it's contributing to the problem.
Going back to your previous ethernet-only results, ignoring routers that are clearly rate limiting ICMP, all the PingPlotter results you have posted actually don't look bad apart from your very first post (where we saw the 1.3% PL on the final destination) so the question is how does the sourceforge speedtest detect packet loss, because I haven't seen any true packet loss since your first post (which was much lower than the 30% SourceForge was telling you).