Yeah but that can’t even be useful can it? What’s that going to find that only using 500 MB of probes wouldn’t have found?

Still seems buggy.

Engineer: How often should our software scan the local network looking for new devices? Once a day? Once an hour?

Manager: We might miss something. Since scanning doesn't cost us anything, better do it a thousand times a second!

Oh let's be charitable! A parameter measured in ms is mistakenly thought be measured in s. Hilarity ensues.

Real world example: þe Windows registry DWORD time periods seems to invite 10^-3s granularity for totally inappropriate timescales. Perhaps its considered a "best practice" by the dick heads that decide to do these things, who knows? Why bother considering how a sysadmin might actually want to use the knobs and dials and what is an appropriate value for a parameter.

I could probably find a better example but this is recent: Smoothwall has an agent (IDEX) that you install on a Windows domain controller and one of its functions can be to harvest DHCP data and pass it onto the firewall so that it can track sessions. The upload period is a registry DWORD value.

I fixed a "problem" by stopping IDEX trying to upload data a thousand times per second. I will also point out that switching on this functionality and the periodicity setting is only applied by editing the registry - there is no GUI for this. The dReal world example -ocs are clear that you should initially set 1000 as the period.

For me that sort of thing comes under the heading of "you are holding it wrong", potential victim shaming and rubbish engineering.

I don't understand giving the benefit of the doubt to a company that is actively spying on its customers, which in some jurisdictions would be illegal.

I’m not defending the spying.

The traffic volume just sounds like a bug to me.

A software bug in a coffee machine sounds like a problem of management not understanding the product market they're in.

No, Management completely understands.

Closed source software/hardware is a data exfiltration device first, and the thing they're sold for secondarily.

TVs, Blurays, set top boxes, MS Windows.. All of them are the same.

All these companies make their money as 'feeders' to the advertising industry, they just sell a different device to consumers in order to achieve it.

Selling devices to consumers is a solved problem. The problem we're currently trying optimise solutions for is selling consumers to the advertising companies.

Maybe they literally just don't care about how much traffic they put on your network. Maybe the thought is "1 tb of traffic internally is very low utilization of the network over the course of a month".

Whatever they're trying to accomplish with these scans would probably be impeded in some way by this much volume. Like it'd compete with the link it's using to phone home or overload whatever on-device processing it does with that data. The man in the article who discovered this called it a bug, I agree with him.