Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

17
  • 6
    OT for this stackexchange, but, there's actually no practical difference between "getting errors above 10mbps" and "downgrading to 10mbps". In both cases, the excess/erroneous packets will be dropped, and the protocol will automatically scale back the send rate. That's one of the major reasons TCP/IP have been flexible enough to last 40+ years. Commented Dec 15, 2020 at 13:44
  • 10
    "May not work well for 4K video," There is no 'may' about it; 10mbps isn't even enough to handle 1080p streaming well, let alone twice that resolution. Commented Dec 15, 2020 at 16:35
  • 7
    @BlueRaja-DannyPflughoeft, well, if the cable works okay as a 10 Mb/s link, but gives errors at 100 Mb/s, negotiating the link as 100 Mb/s but sending only 10 Mb/s worth of data would still be likely to get errors, since the packets would be sent on the wire using the faster encoding, even if there's less of them. (Also, as far as I remember, TCP isn't really made to deal with random errors, just congestion, but I might just remember wrong.) Commented Dec 15, 2020 at 18:09
  • 19
    Downgrading to 10Mbps seems insane. OP has a 200Mbps service and it's 2020. 10Mbps is painfully slow, and it's not like bandwidth requirements are going down. OP is going to want to pull that cable out sooner rather than later and do this properly. Commented Dec 15, 2020 at 19:07
  • 4
    "6x the speed of standard DSL of just a few years ago" how long since you had ADSL1 service? My country has notoriously shitty internet and ADSL2+ has been standard since 2006. Commented Dec 16, 2020 at 3:47