Cajun72 Posted April 13, 2016 Share Posted April 13, 2016 I've just moved house (within same area, only 200 yards away!) and contined with Plusnet with their fibre package. I first tested speedtest.net through the Plusnet hub one router and got 74.5mbps download and 18.5mbps upload with 11ms ping so I thought all was ok with the line. Later on when I returned from work I turned off the plusnet and connected the netduma as per the setup guides. I then re-ran the same speed test and was getting only around 29mbps download! I then run the netduma diagnostics test and was only getting 'good' for jitter and spikes where before I was getting 'exceptional'. Also on the bufferbloat I was getting constant red spikes. I then did a reboot of the netduma and plusnet router and the download speeds increased slightly to 39mbps. The test improved slightly with now getting spikes as exceptional. (see below) Ping Jitter Spikes Packet Loss Good Good Exceptional No Loss Show Details Ping PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=57 time=19.251 ms 64 bytes from 8.8.8.8: seq=1 ttl=57 time=18.563 ms 64 bytes from 8.8.8.8: seq=2 ttl=57 time=15.258 ms 64 bytes from 8.8.8.8: seq=3 ttl=57 time=16.469 ms 64 bytes from 8.8.8.8: seq=4 ttl=57 time=17.652 ms 64 bytes from 8.8.8.8: seq=5 ttl=57 time=16.343 ms 64 bytes from 8.8.8.8: seq=6 ttl=57 time=13.971 ms 64 bytes from 8.8.8.8: seq=7 ttl=57 time=16.449 ms 64 bytes from 8.8.8.8: seq=8 ttl=57 time=13.770 ms 64 bytes from 8.8.8.8: seq=9 ttl=57 time=13.824 ms 64 bytes from 8.8.8.8: seq=10 ttl=57 time=18.892 ms 64 bytes from 8.8.8.8: seq=11 ttl=57 time=13.955 ms 64 bytes from 8.8.8.8: seq=12 ttl=57 time=20.814 ms 64 bytes from 8.8.8.8: seq=13 ttl=57 time=13.826 ms 64 bytes from 8.8.8.8: seq=14 ttl=57 time=13.635 ms 64 bytes from 8.8.8.8: seq=15 ttl=57 time=19.124 ms 64 bytes from 8.8.8.8: seq=16 ttl=57 time=16.181 ms 64 bytes from 8.8.8.8: seq=17 ttl=57 time=20.143 ms 64 bytes from 8.8.8.8: seq=18 ttl=57 time=19.061 ms 64 bytes from 8.8.8.8: seq=19 ttl=57 time=13.259 ms --- 8.8.8.8 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 13.259/16.522/20.814 ms Trace traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets 1 192.168.1.254 0.883 ms 0.848 ms 0.795 ms 2 195.166.130.204 14.456 ms 19.395 ms 19.998 ms 3 84.93.249.18 11.692 ms 84.93.249.17 13.790 ms 84.93.249.18 12.405 ms 4 72.14.222.97 11.416 ms 72.14.223.32 12.760 ms 18.197 ms 5 216.239.48.77 12.247 ms 64.233.174.83 11.994 ms 216.239.48.89 17.200 ms 6 216.239.57.171 13.476 ms 216.239.57.107 21.407 ms 216.239.57.131 12.468 ms 7 8.8.8.8 17.452 ms 21.666 ms 12.229 ms Extra Information: I am still with plusnet and am actually closer to the exchange/green cabinet than before. I have had an electrician in to test wiring in the house and all is ok. I run the tests with an ethernet cable to the pc I tried both preemptive and reactive algo with sliders set at 100% for the speed tests. I am on latest FW 1.03.6g Is this an ISP issue or do I need to keep rebooting until I get good diagnostic tests? What is confusing is the difference in download speeds without the netduma although I am more bothered about not getting an Exceptional rating for jitter as I did before in the other house? Just to note I'm not criticising the netduma at all as it's been great for over 1 year now but I want to get to the bottom of the issue (whatever it is) as soon as possible. Link to comment Share on other sites More sharing options...
Zennon Posted April 13, 2016 Share Posted April 13, 2016 Did you set up your speeds in the congestion control? Deep packet & ipv6 in lan and wan unticked ? You have 6ms of jitter in the test , all lines are different with the same ISP, on FTTC the copper wire from the cab to your home may have a fault or your BT mk3 faceplate may be defective in the new property' Or PN were having a bad day and its fine. If it is still the same tomorrow plot some tests with ping plotter to get some proof. Then keep testing and rule things out one by one do what you can at your home first then contact PN for them to pass it to open retch (pun intended). Link to comment Share on other sites More sharing options...
sharpz44 Posted April 13, 2016 Share Posted April 13, 2016 As Zennon says ,also try not to keep rebooting as this can affect the lines performance DLM,also as this is new connection it will take a little while for the line stability hence why no resets,not sure what plusnet supply's in hardware,did you get an openreach modem or a router modem combi as I know that bt are trying to go the combi route nowadays, sorry forgot to add keep the modem connected ,rebooting Netduma should be ok Link to comment Share on other sites More sharing options...
Zennon Posted April 13, 2016 Share Posted April 13, 2016 Its different for fibre there is no fluctuating at first DLM is off for the first 48h and you have full throughput then DLM is introduced. If you are lucky enough to have a G.inp cab and compatible FW on your modem then you do nto have to worry about DLM unless you are rebooting to much or have a flapping line. BT's thresholds quote "A connection should drop no more than 20 times in a 24 hour period, and should error no more than 2 times per minute." Link to comment Share on other sites More sharing options...
Cajun72 Posted April 13, 2016 Author Share Posted April 13, 2016 Did you set up your speeds in the congestion control? Deep packet & ipv6 in lan and wan unticked ? You have 6ms of jitter in the test , all lines are different with the same ISP, on FTTC the copper wire from the cab to your home may have a fault or your BT mk3 faceplate may be defective in the new property' Or PN were having a bad day and its fine. If it is still the same tomorrow plot some tests with ping plotter to get some proof. Then keep testing and rule things out one by one do what you can at your home first then contact PN for them to pass it to open retch (pun intended). Hi Z. I left the speeds in CC as before as the initial test of 74mbps dl and 18.5 ul through the plusnet hub router (essentially a BT home hub router) where even better than at the old house. Yes all unticked as above. Be surprised it the faceplate is faulty as electrician fitted the newer one to the master socket? I'll keep checking via pingplotter over the next day or so and report back if that's ok. Am I ok to reboot netduma only (not modem) or could that destabilise? Many Thanks Link to comment Share on other sites More sharing options...
Zennon Posted April 13, 2016 Share Posted April 13, 2016 You can reboot the Netduma that is fine it is only routing the traffic not holding the sync. Try a new RJ11 cable sometimes they can go also new Ethernet cables. Did he fit a VDSL faceplate? or a standard NTE? If its a NTE you will need a VDSL dongle filter. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 13, 2016 Administrators Share Posted April 13, 2016 Do the following to rule out the Duma: Input into bandwidth settings 100% anti-flood Reactive algo Share excess enabled Reset device prioritisation & apply Remove anything from hyper traffic Disable IPv6 in WAN, LAN & Misc Disable Deep packet in misc Do a wired speed test from your PC If that doesn't work enable turbo mode in misc settings Link to comment Share on other sites More sharing options...
Cajun72 Posted April 13, 2016 Author Share Posted April 13, 2016 You can reboot the Netduma that is fine it is only routing the traffic not holding the sync. Try a new RJ11 cable sometimes they can go also new Ethernet cables. Did he fit a VDSL faceplate? or a standard NTE? If its a NTE you will need a VDSL dongle filter. I'm pretty sure the RJ11 cable is ok as I bought it (as recommended by your good self ) a few months back. I'll try changing the ethernet cable as the one I used on the pc for the diagnostic test I haven't used for ages but I used that as it was the shortest as there is much less distance now to the router. It is definitely a VDSL faceplate - MK3 2014 version which I bought from amazon fairly recently. The top slot is used to connect straight to plusnet hub router/modem then cat6 from there into Netduma. Link to comment Share on other sites More sharing options...
Zennon Posted April 13, 2016 Share Posted April 13, 2016 I'm pretty sure the RJ11 cable is ok as I bought it (as recommended by your good self ) a few months back. I'll try changing the ethernet cable as the one I used on the pc for the diagnostic test I haven't used for ages but I used that as it was the shortest as there is much less distance now to the router. It is definitely a VDSL faceplate - MK3 2014 version which I bought from amazon fairly recently. The top slot is used to connect straight to plusnet hub router/modem then cat6 from there into Netduma. Ah right sorry that slipped my mind. The guide Fraser has posted above help with the speed? we have got side tracked with the jitter problem. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 13, 2016 Author Share Posted April 13, 2016 Do the following to rule out the Duma: Input into bandwidth settings 100% anti-flood Reactive algo Share excess enabled Reset device prioritisation & apply Remove anything from hyper traffic Disable IPv6 in WAN, LAN & Misc Disable Deep packet in misc Do a wired speed test from your PC If that doesn't work enable turbo mode in misc settings Ok I'll try that Fraser - I've done all above apart from removing ps4 from hyper traffic and enabling turbo mode. Thanks Link to comment Share on other sites More sharing options...
Cajun72 Posted April 13, 2016 Author Share Posted April 13, 2016 Ah right sorry that slipped my mind. The guide Fraser has posted above help with the speed? we have got side tracked with the jitter problem. That's fine no worries Z. to be honest I can live with a bit lower download speed but the jitter problems are more problematic especially when playing COD. Link to comment Share on other sites More sharing options...
Zennon Posted April 13, 2016 Share Posted April 13, 2016 Fingers crossed its just a blip and it evens it's self out. Test with ping plotter direct from your modem/router as well as with the duma in-line to see if there is any discrepancy's. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 13, 2016 Author Share Posted April 13, 2016 Ok I'll try that also Thanks Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 Hi Zennon/Fraser, So last night I did exactly as suggested by you Fraser in the netduma settings and ran speed test but still only getting 30 dl. I then tried with different ethernet cables and run speedtest.net but was still getting around the same dl speed. Then I tried testing from just the hub modem/router (no netduma connected) but still it was only around 30 dl. I then did a reboot of the netduma but still the same speed and on the diagnostics test the results where worse than before (only getting good, good etc). After a 3rd reboot of the netduma and also the plusnet router/modem I ran a diagnostic test and was getting this which surprised me! Ping Jitter Spikes Packet Loss Exceptional Exceptional Exceptional No Loss Show Details Ping PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=57 time=15.071 ms 64 bytes from 8.8.8.8: seq=1 ttl=57 time=14.296 ms 64 bytes from 8.8.8.8: seq=2 ttl=57 time=13.779 ms 64 bytes from 8.8.8.8: seq=3 ttl=57 time=14.571 ms 64 bytes from 8.8.8.8: seq=4 ttl=57 time=13.096 ms 64 bytes from 8.8.8.8: seq=5 ttl=57 time=13.741 ms 64 bytes from 8.8.8.8: seq=6 ttl=57 time=13.572 ms 64 bytes from 8.8.8.8: seq=7 ttl=57 time=14.370 ms 64 bytes from 8.8.8.8: seq=8 ttl=57 time=13.815 ms 64 bytes from 8.8.8.8: seq=9 ttl=57 time=15.910 ms 64 bytes from 8.8.8.8: seq=10 ttl=57 time=13.361 ms 64 bytes from 8.8.8.8: seq=11 ttl=57 time=14.652 ms 64 bytes from 8.8.8.8: seq=12 ttl=57 time=14.535 ms 64 bytes from 8.8.8.8: seq=13 ttl=57 time=15.333 ms 64 bytes from 8.8.8.8: seq=14 ttl=57 time=16.587 ms 64 bytes from 8.8.8.8: seq=15 ttl=57 time=15.634 ms 64 bytes from 8.8.8.8: seq=16 ttl=57 time=14.288 ms 64 bytes from 8.8.8.8: seq=17 ttl=57 time=14.181 ms 64 bytes from 8.8.8.8: seq=18 ttl=57 time=13.877 ms 64 bytes from 8.8.8.8: seq=19 ttl=57 time=13.506 ms --- 8.8.8.8 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 13.096/14.408/16.587 ms Trace traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets 1 192.168.1.254 0.926 ms 0.801 ms 0.745 ms 2 195.166.128.233 11.398 ms 11.188 ms 15.071 ms 3 84.93.249.65 47.455 ms 12.569 ms 11.296 ms 4 72.14.222.97 11.659 ms 12.189 ms 72.14.223.32 11.209 ms 5 216.239.56.203 11.965 ms 216.239.48.89 12.279 ms 216.239.56.203 12.451 ms 6 216.239.57.95 12.276 ms 216.239.57.53 12.203 ms 216.239.57.91 12.594 ms 7 8.8.8.8 12.163 ms 13.134 ms 13.940 ms Because of these good results I didn't want to fiddle about any more so I left things as they arre, even with the dl speed being so low. I'm a bit confused as to why before the diagnostics where only 'good' but after rebooting all went to 'exceptional', so not sure which is the most accurate? I am conscious that if I reboot or run again this may change again. Not sure what to do next really, I could install ping plotter and try running that, but that won't affect the dl speeds. What do you think? Link to comment Share on other sites More sharing options...
Zennon Posted April 14, 2016 Share Posted April 14, 2016 Be cause you are getting the 30mb direct from your ISP router you need to access the PN routers GUI and look at your stats to see what you are syncing at. Jitter is never constant it changes over time, ping plotter is best for judging over time not just a short 20 times ping. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 Sorry what do you mean but what it is syncing at? is this a log somewhere on the plusnet router? Link to comment Share on other sites More sharing options...
Zennon Posted April 14, 2016 Share Posted April 14, 2016 The line syncs with the exchange and your router will have a page that tells you the information. To me it sound like your syncing at 32mb with over heads you are getting around 30mb. It could be that the housing estate where you are now send the copper on a wild goose chase back to the cab, unlike your last property that when directly to the cab, this is not uncommon. I have two friends that live on the same housing estate over the road from each other, one gets 30mb the other 22mb because his copper line goes round the housing estate back to the cab and the others is a more direct route. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 So can it be fixed? I think I'm going to contact plusnet as it doesn't sound right. If I run ping plotter and the post results will you help me as I find it hard to understand what it is telling me! Link to comment Share on other sites More sharing options...
fuzzy clam Posted April 14, 2016 Share Posted April 14, 2016 So can it be fixed? I think I'm going to contact plusnet as it doesn't sound right. If I run ping plotter and the post results will you help me as I find it hard to understand what it is telling me! Yoda Z is the man when it comes to this stuff,if anyone can get it sorted for you it will be him. Pingplotter was great for me when he suggested it to find the jitter issues on my line and now I have a new ISP with basically no jitter. Link to comment Share on other sites More sharing options...
Zennon Posted April 14, 2016 Share Posted April 14, 2016 So can it be fixed? I think I'm going to contact plusnet as it doesn't sound right. If I run ping plotter and the post results will you help me as I find it hard to understand what it is telling me! You can not fix the route the copper makes to the cab. It may not be this though, you have to show us the sync of the line. And yes i will look at the plots mate. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 Ok. I'll have a look at what the plusnet sync is showing and post the results along with the pingplotter results. With pingplotter, do you just keep it running for an hour or so, or do you run once to an ip address one night then do the same over the next few days at peak times? Link to comment Share on other sites More sharing options...
Zennon Posted April 14, 2016 Share Posted April 14, 2016 Ping 8.8.8.8 for a few tests and bbc.co.uk for some more at peak times 10 mins each will do. Do not use the internet while you test. Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 Hi Z Firstly it wouldn't let me dl pingplotter pro as I must have previously downloaded it and the trial expired so I tried the free version, which I realised half way through doesn't show the jitter is this still ok? anyway I've attached 2 files - v1 is at 8:21pm to 8.8.8.8 and v2 is 8:34pm to bbc.co.uk I've been in the plusnet hub page and saw this: and also attached the event log. DSL Line Status Connection Information Line state: Connected Connection time: 0 days, 23:22:10 Downstream: 78.12 Mbps Upstream: 19.53 Mbps plusnset hub event log 140416.txt Link to comment Share on other sites More sharing options...
Cajun72 Posted April 14, 2016 Author Share Posted April 14, 2016 Ok an update, I've managed to uninstall and re-install pingplotter pro and tested for 10 mins each again to 8.8.8.8. and bbc.co.uk with jitter details. 1st test shows jitter in red, the 2nd was red for almost the 10 minutes then the jitter went to 1.78 near the end. What do you think guys do I need to report to plusnet or keep running for a few days? Link to comment Share on other sites More sharing options...
Zennon Posted April 14, 2016 Share Posted April 14, 2016 The packet loss on the bbc plot is normal it is because the two routers in the hops do not respond to ping so it shows 100% loss when infact there is non. There is around 10ms of jitter from time to time it is not crazy bad but it is jitter non the less. Was this testing with nothing using the net but the plotter? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.