Some chip makers have hidden latency and jitter issues from common tests
badmodems.com
badmodems.com
Puma 5 shipped with just enough resources for 8 downstream channels. Puma 6 has same resources, but 16 downstream channels. Bottleneck is in hardware accelerating packet decoding/assembly, queue/buffer is too shallow and more packets in flight result in stalls. You can disable this hardware block and magically modem stops being susceptible to DOS, but max throughput goes down to ~60Mbit (opposed to theoretical ~800Mbit with ~2Mbit DOS potential)
There are people with Puma 6 with ISP using only 6 downstream channels and their modems work just great. 8 is barely acceptable (even puma 5 has problems on the test and can be DOSed by ~10Mbit), 16 is just plan broken.
The DOCSIS standard requires filtering by IP address and port [1] built in to the modem, instead of at the CMTS. This is back-asswards, as a hacked modem can ignore the filtering, but it's part of the spec.
There are multiple sources of jitter in the puma 6/5: more channels = more jitter, more flows = more jitter/complete failure at ~2000 separate active flows in a 1 second period.
[1]: http://www.cable-europe.eu/wp-content/uploads/bsk-pdf-manage... - Annex F Protocol Filtering (Normative)
IP is the network layer. Can't route packets without it.
Yup, I've had this happen WAY to frequently with the DG1670 CableOne forced me to switch to (and I literally have no option for other equipment, they require this specific modem for anyone with a static IP). The modem will literally lose connection and reset itself when under load (which takes upwards of 10 minutes to boot), if I could put my old SBG6850 back in place I would do so in a heartbeat.
Until Intel released its Puma 6 chip Broadcom dominated the modem chip market. The Broadcom chip does not have latency or jitter issues.
As much as I hate them, Broadcom dominates the market because (as long as you don't ask for source code or Linux or datasheets...) their modems and other networking devices generally work. I'm guessing the cause of this jitter is because Intel is trying to do more in software vs. the dedicated hardware Broadcom uses.
The DoS on the "Security Issues" page is even more unusual, unless these modems are actually more than just modems and include a router/NAT too?
Even the graphics vendors have got their shit together. That's how hopeless Broadcom is.
in my experience, many bluetooth hiccups are caused by manufacturers having alternate readings of the bluetooth spec, which is a massive, hard to swallow behemoth.
if you have two 1st party BTLE devices, you can expect to see bluetooth at its best. for example, apple airpods + iphone are probably as good as youll ever see a bluetooth pairing.
I personally only use my AirPods with Apple products so I can't speak to whether they perform less well on regular devices, but, I somehow doubt it. Beyond pairing, it seems the only remaining secret sauce is in the relay between the two earbuds and coordination between the to for which one actually connects to the source device. None of that matters for the BT spec.
Outdoors, particularly walking down streets, may be a different matter.
Tricky bit about BT is that it is actually designed to bounce of surfaces to some degree. This because in its most basic form, that of a wireless earbud connection, it may not be able to penetrate the human body.
So to work around issues with devices being on different sides of a walking, talking, bag of water, it tried to make use of echos from nearby walls and other suitable surfaces.
End result is that in a environment that is constantly shifting, like out on an open street, performance will be hit or miss from moment to moment.
But when indoors and stationary i have been able to get a phone to talk to a tablet and earbuds, while the tablet also talks to a keyboard.
And this was all kit from before BTLE...
Broadcom dominated telecommunications/ISP modem sector thanks to Sophie Wilson of ARM fame, and her massively parallel Firepath LIW/SIMD chip
https://www.eetimes.com/document.asp?doc_id=1180959
https://www.hotchips.org/wp-content/uploads/hc_archives/hc14...
I'm more than a little furious that after being sold a product that explicitly fails under load, the best we have in terms of consumer protections is a class action that, if my history of class actions holds true, will accomplish little to nothing to either punish intel or compensate the consumers.
For the last year I've been putting up with network issues that I thought were a result of the house I moved into, when now I find out that the sb6190 I spent a silly amount of money on has been degrading an equally not-cheap internet plan for the entire time. And now my best approach is "deal with it, spend 200$ more."
Here's hoping consumers in the EU are more protected, for us in the US I don't have my fingers crossed.
That being said, thanks for the clarity on 3.0 vs 3.1, I had pulled up the recommended SB8200 since I had broadly heard positive things about Arris in the past and saw it to be ~190; didn't realize the cutoff was as high as 300mbps, so I should be fine with my 250mb down to get a cheaper one.
[0]https://camelcamelcamel.com/ARRIS-SURFboard-SB6190-DOCSIS-Ca...
"Apparently, it runs on some form of electricity."
Australia's internet is in such a confusing state. At the moment a house could potentially get internet via one of ADSL1/2/2+, VDSL2+, HFC, Fiber, Wireless or satellite and on top of that most telcos are shipping woefully bad modems/router hardware with equally bad, gimped, and undersupported firmware to consumers.
Before then it was all about ADSL2+ (or some such) over a aging copper pair.
From a practical perspective, if your modem is on the list, your apps and browsers will load pages slowly, with weird delays all over the place (due to DNS being Most Impacted by the Puma problems). Replace ASAP.
100% across the board with an SB6190 (HW ver 3, SW ver 9.1.93V, service from RCN). So… either the test missed an issue, or my SB6190 has been fixed. (Latest posts in the forum [1] seem to indicate that at least Cox is working with Intel on a fix.)
[1] http://www.dslreports.com/forum/r31122204-SB6190-Puma6-TCP-U...
I know at least one box i have here are listed by 3 different variants on the OEM site, and the only distinguishing factor is a single letter on a single model code pinted on the sticker underneath it.
Checking the box or anything similar and you would be non the wiser.