3 ms·
The ASUS/Trend Micro feature is not basic bandwidth reporting. Yeah, I've run this kind of basic reporting on a Raspberry Pi before - if that's all that you're
by haswell 10y ago
The ASUS/Trend Micro feature is not basic bandwidth reporting. Yeah, I've run this kind of basic reporting on a Raspberry Pi before - if that's all that you're tracking, not much processing power is required.
These routers are giving other breakdowns of the data - by device, by service, by application, etc. See sibling comment as well.
Edit: Screenshot of example: https://www.evernote.com/shard/s10/sh/0128aee2-dbae-48c3-b4db-c07bc08f21d0/96d724727266b977 https://www.evernote.com/shard/s10/sh/0128aee2-dbae-48c3-b4d...
- tmd83 10y agoI don't see how its a cpu issue. The router definitely isn't sending every packet but some kind of aggregate already whether by port or something. My guess is that the upstream service just have the map from the aggregate to app (dropbox or whatever). Now this allows them up update the mapping as apps change or add new app tracking but that can be easily done through a firmware update if they really want to. I don't disagree that this might make it easier for them to support the feature but definitely not essential. If it wasn't the culture of sending things out as much this would have been designed differently.