-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix wrong values for max down-/upstream #97
Conversation
@dirkpauli @uclara Can you please test the build? https://github.com/mcktr/check_fritz/actions/runs/274989817 Please note that it is now necessary to provide the This is still a work in progress since I don't know if the changes work out as expected. |
I tested all three versions (1.13, 1.14 and 1.15 - what's the difference?) in my FRITZBox 6591 Cable that runs on a Vodafone Kabel Deutschland line with 1000/50 Mbit/s. All there versions give the same value: check_fritz_1.13:
check_fritz_1.14:
check_fritz_1.15:
For all there versions I used this command lines:
PS: I noticed that Ulli |
@uclara Thanks! 👍
The difference is the used Go version. It is sufficient when you use the latest (1.15). Can you show us a screenshot from the Fritz!Box interface and the values from there? I have menu entry called Best regards |
@uclara Just for test purposes what do you get if you leave out the parameter |
@mcktr: if I omit the
|
@uclara Thansk for the screenshots. I'll guess then this works didn't it? The returned values from the check plugin are the same that the Fritz!Box reports in the web interface. Okay the I'll now fix the usage functions and then we can merge this and finally release an updated version. |
Great job! I will try all modes again to be sure that all works as expected and will give you a feedback. BTW: do you know if I need a valid user/password combination for the login or does a valid user with the default password used to login to the FRITZ!Box is also enough to get a valid login? Ulli |
Hi Michael,
thanks - the downstream_max and upstream_max methods now show the correct values. downstream_usage and upstream_usage however, still show the silly high values. seems the data are not taken from the same place for those different methods?
Unfortunately, I only have that cable box available, so I cannot provide DSL or LAN tests.
Regards
Dirk
Gesendet: Sonntag, 27. September 2020 um 11:35 Uhr
Von: "Michael Insel" <[email protected]>
An: "mcktr/check_fritz" <[email protected]>
Cc: "dirkpauli" <[email protected]>, "Mention" <[email protected]>
Betreff: Re: [mcktr/check_fritz] WIP: Fix wrong values for max down-/upstream (#97)
@dirkpauli @uclara Can you please test the build?
https://github.com/mcktr/check_fritz/actions/runs/274989817
Please note that it is now necessary to provide the --modelgroup cable parameter on cable boxes. If possible please also verify this on a DSL Fritz!Box (but without the --modelgroup parameter) and if you have access to one Fritz!Box that is connected via LAN1 to the internet I am also interested in the results (in that case please test both with and without the parameter).
This is still a work in progress since I don't know if the changes work out as expected.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Query the correct TR-064 action to collect the correct values for downstream_usage and upstream_usage methods.
1bf51d0
to
e7ccfd0
Compare
@uclara @dirkpauli Thank you both for testing, I highly appreciate your help! 👍 I updated the pull request. Now all four functions should work as expected. Please give it another try. :-) You can find the binaries for the updated pull request here, it is sufficient when you test the binaries build with Go 1.15. https://github.com/mcktr/check_fritz/actions/runs/275424475 If your feedback is positive I think I can release version 1.2.0 on the next Friday. The *_usage functions weren't patched, but now they are. :-)
I am not sure what you mean. If you turn on the setting |
@mcktr I tested the remaining things: LAN1 connected FRITZ!Box 6490 Cable:
DSL connected FRITZ!Box 7490:
|
@mcktr I created a script to check all my FRITZ!Boxes that I have in my family environment ;-) Version: check_fritz version 5a4c4a4 FRITZBox 7490 via ADSL --modelgroup DSL :
--modelgroup Cable :
FRITZBox 7490 via Lan1 --modelgroup DSL :
--modelgroup Cable :
FRITZBox 7490 via Lan1 to FTTH Router --modelgroup DSL :
--modelgroup Cable :
FRITZBox 6591 Cable via Cable --modelgroup DSL :
--modelgroup Cable :
FRITZBox 6490 Cable via Lan1 --modelgroup DSL :
--modelgroup Cable :
|
@uclara Wow thank you! So there still is a problem with boxes that are connected via LAN1 to the internet. I'll have a look but I don't know if there is a solution for this. I'll let you know :-) Best regards |
I tried a lot of things in the last days to fix the LAN1 problem... unfortunately nothing worked out. I'll merge this PR and tag a new version but creating a follow-up issue to investigate further on the problem with a fresh mind. :-) Best regards |
Query the correct TR-064 action to collect the correct values for max downstream and upstream.
Important:
Since the correct values for the max down-/upstream are stored in a different TR-064 action on cable boxes it is now necessary to define the
--modelgroup
parameter for cable boxes.TODO
downstream_usage
upstream_usage
fixes #72
fixes #96