Bogus throughput at startup
Bug #1099563 reported by
StoatWblr
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UPnP Router Control |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
The package usually reports bogusly high throughputs in the first 2 seconds after startup, then settles to real values.
IE: ADSL modem, 17Mb/s downlink, 800-3000Mb/s reported momentarily.
This makes graphing unreliable for the first 90 seconds of operation and could be avoided by not treating the first counter read as an offset from zero (It's a read to establish the current zero point)
Also: Periodically counters seem to be double-read (or missed on an interval, then picked up at the next read), resulting in a bogus spike reading of double the current throughput. I'm not sure how this should be tackled.
Thanks for the package :)
Revision history for this message
| Daniele Napolitano (dnax88) wrote | #1 |
| Changed in upnp-router-control: | |
| status: | New → Confirmed |
| Changed in upnp-router-control: | |
| status: | Confirmed → Incomplete |
To post a comment you must log in.
Hi, thank you for the time spent filling this bug report.
I'm aware of that behavior, the information returned from the router, with inconsistent timings arent't really usable for making the network graph. I'm considering of increase the time of every graph point from 1 second to 5 seconds or more to archive that problem.
Meanwhile, can you run URC from the console in debug mode for give me more informations?
upnp-router-control --debug