Jump to content

Recommended Posts

Called ISP he reckoned the line is all over the place with dropped packets etc. but believes it's a network issue rather than a line issue. Engineer is coming first thing Friday morning (hopefully). Last time a BT engineer came he said it was an openreach problem so I don't have much hope for this one to do anything but book another engineer. I'll let you know. 

Share this post


Link to post
Share on other sites

Engineer came, everything in the house is fine. He reckons is degradation on the copper line. He’s sent it back to BT who should call in the next couple of hours with a Special Fault Investigator appointment (don’t know if that’s just a technical name for a normal open reach engineer or if that’s a more specialised open reach engineer). He actually asked if I tried any third party routers with QOS where I showed him my massive hidden collection 😁 and said they were struggling due to the line connection. 

Share this post


Link to post
Share on other sites

Unfortunately he couldn’t ‘see’ a fault as he was only allowed to work inside the house. However the tests ran by BT on the line and his report suggests there must be something wrong. He also said only gamers would notice the ping spikes and packets loss as other applications like streaming and web browsing would be unaffected so while the whole line is likely to be faulty we’re probably the only gamers on the street who bothered to report the issue so far and so I’m not super hopeful of a solution.

Share this post


Link to post
Share on other sites

Gonna hijack this thread a little to report an issue I'm experiencing with QoS on a PPPoE/VDSL connection as well

Basically, by default after doing the initial setup of putting my speeds in to anti-bufferbloat, putting a 70% limit on dl/ul and turning the policy to always, the net effect is absolutely nothing, devices are free to dl/ul at the maximum speeds of the connection, it just doesn't work. This is regardless of whether there was any active game traffic or not and there was no difference between the "always" and "when high priority traffic detected" settings. However, after much annoyance and messing around, I found out that if I manually added a device on my network to the "Traffic Prioritization" list and selected some random service (I chose skype, none of the devices actually ever use skype) the QoS would work as intended and limit the bandwidth of the device. This is by no means a new problem, it has been this way ever since I upgraded from the old firmware to DumaOS and persisted through many factory resets.

Hopefully this info is useful to others and the bugs with DumaOS and PPPoE can be rectified.

Share this post


Link to post
Share on other sites

Quick update, Openreach engineer due tomorrow morning. However I’m not that hopeful as they missed 3 appointments last time so fingers crossed!

Share this post


Link to post
Share on other sites

Openreach have said no issues on the line with their tests so they didn’t bother sending an engineer. BT have now said no faults as well and refuse to rebook. To be fair to them the speeds are always consistent. I’m going to leave ping plotter running on my pc for an hour or two. If it’s stable then I think the issue may be with the XR500.

To further this as well, the fact that it’s rock solid when I’m home alone implies that’s there’s not an issue with the line causing packet loss or anything like that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...