mcktr/check_tr64_fritz

Downloadrate not correct

Closed this issue · 1 comments

achmet9948 commented

Hello,

my downloadrate is 1150 mbit/s on the fritzbox. But the plugin output write only 525 Mbit/s. Can you check it?

<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:X_AVM-DE_GetOnlineMonitorResponse xmlns:u="urn:dslforum-org:service:WANCommonInterfaceConfig:1">
<NewTotalNumberSyncGroups>2</NewTotalNumberSyncGroups>
<NewSyncGroupName>sync_cable</NewSyncGroupName>
<NewSyncGroupMode>CABLE</NewSyncGroupMode>
<Newmax_ds>65632291</Newmax_ds>
<Newmax_us>7188253</Newmax_us>
<Newds_current_bps>2271,5811,1995,2799,3633,5108,6104,7659,8426,6269,1641,3226,7636,1769,1029,392,478,193,523,3998</Newds_current_bps>
<Newmc_current_bps>51,17,68,85,34,103,34,17,68,34,51,34,17,51,34,51,34,0,51,17</Newmc_current_bps>
<Newus_current_bps>2383,32496,5589,12254,18143,805,41492,50183,55369,41257,3159,13231,880,1772,1048,351,483,261,585,1725</Newus_current_bps>
<Newprio_realtime_bps>945,400,473,11,72,39,23,227,683,384,61,521,11,23,618,11,48,26,0,1093</Newprio_realtime_bps>
<Newprio_high_bps>95,191,72,143,0,48,23,48,51,208,140,97,828,844,71,95,0,48,0,223</Newprio_high_bps>
<Newprio_default_bps>1502,32065,5168,12332,18153,825,41380,49954,54934,41157,3090,12677,473,2455,434,350,491,328,593,592</Newprio_default_bps>
<Newprio_low_bps>0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0</Newprio_low_bps>
</u:X_AVM-DE_GetOnlineMonitorResponse>
</s:Body>
</s:Envelope>
OK - Downstream 525 Mbit/s | 'downstream_rate'=525;;;;

image

mcktr commented

Hi @achmet9948

thanks for reporting this. The development for the Bash implementation of this check plugin has more or less stopped. If you want to get an up to date and maintained version of the check plugin please checkout the Golang implementation.

The Golang implementation currently suffers from the same issue. I am currently looking into fixing this and created a first debug version to identify the problem. You may want to join the conversation. :-)

Best regards
Michael