Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on January 04, 2014, 07:56:30 AM
-
This release has one new feature, plus a number of small tweaks and fixes. The new feature is an embedded webserver which enables you to monitor several of the graphs and stats pages remotely, either over your LAN or over the internet. To use the webserver over the internet you have to configure your router to forward one selected port (port 55555 by default). More details here: http://www.s446074245.websitehome.co.uk/webserver.html (http://www.s446074245.websitehome.co.uk/webserver.html)
Full list of changes since v 4.31:
- fixed longstanding bug which could sometimes cause access violation when autosaving snapshots
- QLN and HLog graph timestamps are now refreshed only after a stop or pause (i.e. when the
data is re-read)
- fixed issue which resulted in incorrect VDSL2 band plan detection on some systems (hopefully)
- the legend displayed on most graphs can now optionally be at the top right or top left
- the Configuration tab is now at the right hand end (to the right of the Event Log tab)
- added an embedded webserver to enable remote monitoring of the DSL connection
- added startup check to ensure that only one instance of DSLstats is running
[Edit] A file was missing from the download archives. This has now been corrected and the version updated to 4.40.1
http://dslstats.plainroad.me.uk
-
Up and running but on vdsl since 16:30 yesterday, I have a good 80/20 sync but poor and erratic throughput at the moment on TalktalkB. I suspect/hope something needs setting correctly in TT GEA hand over in the exchange. They may not have done with the late time of the install. A few of points, two perhaps as I am new to vdsl
1. Using the HG622 as modem router at the moment I get some narrow blue strips in the bit loading. What are these?
2. As with the previous version the Hlog tones display does get to the full width but cuts at about 3650 - you can see the rest if you scroll but it would nice to use the same scale as the tones.
3. As well as the copy to clip board on the stats, a save option putting a .txt file with the snapshots would be nice? Maybe I am missing something.
4 Are there any security issues with the web server?
-
An extra point, The max speed on the connection speed graph is 200Mb/s which seems rather optimistic! I can't spot how to change it and it limits resolution of the actual speeds
-
Up & running here now. Not using the webserver though. I dont have any issue with it, just dont believe I need it.
Stuart
-
1. Using the HG622 as modem router at the moment I get some narrow blue strips in the bit loading. What are these?
They are intended to indicate tones which are unallocated or in overlapping bands. If you look at the pbParams data (under Telnet Data) and check the Medley Phase information, you'll see there are some tones which aren't in any allocated band, and there may also be some tones which appear in more than one band. For example, it's quite common for the first upstream band and the first downstream band to overlap. In these circumstances there's no way to know whether the tones in question are being used for upstream or downstream.
2. As with the previous version the Hlog tones display does get to the full width but cuts at about 3650 - you can see the rest if you scroll but it would nice to use the same scale as the tones.
I've neglected this issue. I'll put it on the list for attention.
3. As well as the copy to clip board on the stats, a save option putting a .txt file with the snapshots would be nice? Maybe I am missing something.
You're not missing anything. I'll add it to the list.
4 Are there any security issues with the web server?
DSLstats doesn't by itself do anything to expose you to the internet. If you run the webserver and set up the port forwarding in your router, then that port is potentially open to abuse, and that risk is exactly the same as with any program which makes use of port forwarding. All I can say is that I've used published and tested code and all DSLstats does is serve some simple web pages.
-
I am using a DGN2200 V1, and cannot get it to work.I had it working before xmas, then went away for 10days, when i came back it had stopped working.It seems that unlock code had stopped working.
-
I haven't changed anything in the way DSLstats collects data from the router, so I think your issue must be with the DGN2200. Enabling telnet access is a bit complicated, and the setup will be lost if you power down the router. Have you tried re-enabling telnet access?
-
An extra point, The max speed on the connection speed graph is 200Mb/s which seems rather optimistic! I can't spot how to change it and it limits resolution of the actual speeds
It's supposed to autoscale so that the maximum is a sensible round number above the highest value reported. I may need to refine it a bit. Is it possible that your maximum attainable has exceeded 100 Mbps?
-
Thought I would try out the webserver, but am having issues
Configuration files stored in C:\ws\dropzone\rsw\rs-w32\
04 Jan 2014 17:16:04 Unable to copy webserver templates to C:\ws\dropzone\rsw\rs-w32\webserver\ . Webserver disabled.
04 Jan 2014 17:16:04 Webserver started
04 Jan 2014 17:16:07 Recording started
04 Jan 2014 17:16:23 Some webserver snapshot(s) could not be saved
No stats.htlm or fullstats.html are created
Is there an html wrapper for the bitloading.png graph?
Is the refresh interval for the html pages configurable, as these seem to be fixed at 30 seconds?
Is there any way of preventing DSLstats from doing a complete screen refresh when the webserver is enabled?
If the webserver is enabled and then disabled and later enabled again then I get an access violation error message box pop up and DSLstats aborts.
-
Yes the max attainable is 108Mb/s but I am first or about first on the cabinet so I expect it to drop. I am surprised it is that high as I am about 400m from the cabinet.
It is not doing me much good at the moment -- actual downloads have been between 5mb/s and 76mb/s most often about 17mb/s. I tried TTB technical support to today they were puzzled as the 80/20 sync was visible but the "line card" said "connection does not exist". I am not sure that a line card is actually involved through. I thought that TT has GEA handover where ever they have LLU as at my exchange. Action promised Monday. I hope it some easy to fix handover issue in the exchange.
God knows what the DLM is thinking at the moment TTB had me connecting and reconnecting with the supplied ECI and the HG622 and a unlocked HG612 when I said I had one. 6 times in 20 min seemed dodgy to me! There saw more stats with 612 and nothing with the ECI but that may be luck. With the ECI they could not even see the sync but it had connected and was giving much the same speeds. At least I have usable if erratic internet access and nice connection stats for now.
-
Is there an html wrapper for the bitloading.png graph?
Yes, sorry, this was left out of the download archives. This explains the error messages in the event log. The file is called bitloading.html, and it should be in the same directory as the other DSLstats files. Its contents are:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="refresh" content="30; url=bitloading.html"; text/html; charset=ISO-8859-1>
<title>Bitloading</title></head><body>
<h1>Bitloading</h1>
<img alt="" src="bitloading.png"><br>
<br>
</body></html>
Is the refresh interval for the html pages configurable, as these seem to be fixed at 30 seconds?
It's not configurable from the program at present, but you could change it manually if you wish. It's the number 30 in the second line of all the html files. I should point out that this doesn't affect the behaviour of the main program in any way; it simply sets the rate at which the remote user's browser refreshes the page.
Is there any way of preventing DSLstats from doing a complete screen refresh when the webserver is enabled?
When the webserver is saving the snapshots it has to briefly bring each webserver-enabled graph into focus before saving the snapshot. This is so fast that I haven't seen any visible effect on the systems I've tested it on, but obviously that isn't the case everywhere. I'll see if I can find a different way to handle this.
If the webserver is enabled and then disabled and later enabled again then I get an access violation error message box pop up and DSLstats aborts.
I haven't seen this behaviour. I'll check it out.
I'll upload archives with the missing html file included shortly.
-
Hi Roseway and excellent DSLstats updates, I don't have any issues with the updates it's something I don't understand the lower left hand side System uptime: and DSL uptime:
the modem did get a retrain reason 4 six days ago and DSL uptime: shows this but don't know what the system uptime: relates to ?
-
@les-70: I think I need to make the graph rescaling a bit more fine grained than it currently is. I'll have a look at this for the next version (by which time your max attainable will probably be below 100 Mbps :) ).
-
Hi Roseway and excellent DSLstats updates, I don't have any issues with the updates it's something I don't understand the lower left hand side System uptime: and DSL uptime:
Thanks for the comments. System uptime is the time since the modem was last (re)booted. It's obtained from the CLI command cat /proc/uptime.
-
Thanks for the comments. System uptime is the time since the modem was last (re)booted. It's obtained from the CLI command cat /proc/uptime.
Thankyou Roseway so System uptime: clock resets after powering off/on the modem.
Cheers RW
-
Thanks for the heads up on the missing bitloading.html. Had a quick look at the source files and it is there.
-
I've just uploaded corrected archives v4.40.1
-
Thank you for the latest round of updates. The ability to choose the location of the graph legend is purrfect. :)
There is just one thing that I feel I should mention . . .
Configuration ---> Snapshots There is an option, under the Autosave graphs: heading, to Snapshot all active graphs on exit.
Now I don't want to sound ungrateful but that is not what I require. (And surely that configuration option is misplaced? Shouldn't it be located under the Items to Monitor tab?)
I would like to see an option that takes a snapshot, on exit, of only the graphs that are set to autosave.
-
(And surely that configuration option is misplaced? Shouldn't it be located under the Items to Monitor tab?)
I can't say that I agree with that, unless one of us is misunderstanding the other. The option is about snapshots - when it's enabled, on exit, snapshots are taken of all graphs which are currently enabled.
I would like to see an option that takes a snapshot, on exit, of only the graphs that are set to autosave.
That sounds like a useful option. I can certainly implement that.
-
The option is about snapshots - when it's enabled, on exit, snapshots are taken of all graphs which are currently enabled.
Ah, I see. So it takes a snapshot of all currently monitored items. So that definitely is not what I was expecting.
I would like to see an option that takes a snapshot, on exit, of only the graphs that are set to autosave.
That sounds like a useful option. I can certainly implement that.
Thank you. I shall look forward to that, in the fullness of time.
-
I am afraid that having got vdsl (in a very wobbly state of between 1 and 54 Mb/s today) I find that there are any many things which puzzle me, so apologies if this the is one of a few well known things that I will asking.
I wonder why dslstats reports the dslam/msan type as "not reported" (with an HG612 on a ECi cabinet). xdslcmd info --vendor gives a response of IFTN as expected. Is dslatats hoping for the info via another command? and if so might a --vendor be used to get it?
As an aside I notice that the 035 blob does not have Hlog and QLnN for the upstream tones but the HG612 038 does - no doubt well known but it makes the Hg612 038 graphs look better
-
I wonder why dslstats reports the dslam/msan type as "not reported" (with an HG612 on a ECi cabinet). xdslcmd info --vendor gives a response of IFTN as expected. Is dslatats hoping for the info via another command? and if so might a --vendor be used to get it?
DSLstats does use the --vendor command as the source of the information, so it looks as though something isn't working quite right. Could you copy the output of the --vendor command here, please?
As an aside I notice that the 035 blob does not have Hlog and QLnN for the upstream tones
Somewhere on the forum I've read that this is the case with HG612 and an ECI DSLAM. But I don't recall it being mentioned that the 038 blob does report the upstream. That's a worthwhile, if small, improvement.
-
HG612 on ECI DSLAM 038 vendor output -- hope this helps
# xdslcmd info --vendor
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 37237 Kbps, Downstream rate = 106484 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps
ChipSet Vendor Id: IFTN:0xb203
ChipSet VersionNumber: 0xb203
ChipSet SerialNumber: 5502226656
#
-
Thanks, that's just what I wanted. I'm a bit puzzled as to why DSLstats isn't working right with it, but I'll sort it out.
-
Thank you for this new version.
Only a minor cometic bug, but the graph line thickness setting is not applied on the SNRM per band graphs.
-
Oops sorry. Your puzzled comment made me try fully closing and restarting dslstats. It then works!!! Sorry for the false report. I don't know why the vendor info had died but dslstats had suffered a loss during a swap between 035 and 038 which otherwise it seemed fine with. I will try to be more careful. :-[
-
Oops sorry. Your puzzled comment made me try fully closing and restarting dslstats. It then works!!! Sorry for the false report. I don't know why the vendor info had died but dslstats had suffered a loss during a swap between 035 and 038 which otherwise it seemed fine with. I will try to be more careful. :-[
Thanks for letting me know. However, I suspect that you'll now find that it's not reporting upstream QLN and HLog values. I'm not certain about this, but I'll be checking it out tomorrow.
-
Thank you for this new version.
Only a minor cometic bug, but the graph line thickness setting is not applied on the SNRM per band graphs.
Thanks, it will be fixed.
-
Just for info the upstream stats stick with the Hg612 038 also with the Hg622 and its 035. The snapshots of qln and hlog cut off like the display and of course you can't scroll them.
-
Thanks for clarifying that.
-
Just for info it has taken just one neighbor (installed to day) to reduce my attainable from 107 to 93! I am hoping that subsequent additions may benefit from the log scale but I may be misunderstanding how adding connections one by one would influence things.
-
I may be misunderstanding how adding connections one by one would influence things.
Crosstalk possibly?
-
I am quite sure it is cross-talk but wonder given log scales whether each subsequent connections produce such big snrm jump. The snrm dropped by 5db. I am hoping that, assuming the same added noise level each time, the next connection drop won't be another 5db but a smaller number given that db are a log scale. I may just be muddled and will later calculate adding a series of fixed error voltages to a known signal voltage and then expressing the ratios in db's
I am sure this as clear as mud! ???
-
- fixed issue which resulted in incorrect VDSL2 band plan detection on some systems (hopefully)
Thank you Eric, work perfectly here.
/Luiz
-
Thank you Luiz.
-
Just moved to 4.40.1 and only new issue is the colours of the bands. I am using a HG612 with 038 firmware. It seems to rather like more blue!!
-
Are you sure you've got the correct version there? The graph says it's v4.01.
-
oops again, glad your awake even if I am not!!!
-
The SNRM per band still needs to be added into the .ini as you have to still have to select it manually.
Cheers nice update!
-
The SNRM per band still needs to be added into the .ini
I'll check that out.
-
Hi Eric :)
just wanted to let you know Iam still getting failed QLN and HLOG graphs, ive just checked all my saved folders from every time ive had it running and all graphs save properly except QLN and HLOG, it saves them but theres no data, they are 0KB in size
there is nothing in the event log that may show whats happening:
Configuration files stored in C:\Users\Paul\AppData\Local\dslstats\
13 Jan 2014 14:57:45 Recording started
13 Jan 2014 14:58:01 IP address is now 2.123.149.148
Download succeeded. File saved to C:\DSL-Stats\dslstats32W-4.40.1.zip
13 Jan 2014 15:14:43 Updated version downloaded
see:
(http://i.imgur.com/cE6XkYm.jpg)
-
I'll check that out again, snadge. Just to be sure - the QLN and HLog graphs are visible in the program, I presume?
-
I'll check that out again, snadge. Just to be sure - the QLN and HLog graphs are visible in the program, I presume?
yeah fine in program... :)
-
Thanks for this program, the pi version works great :)
-
Thanks for letting me know. :)
-
Summary of current situation:
As with the previous version the Hlog tones display does get to the full width but cuts at about 3650 - you can see the rest if you scroll but it would nice to use the same scale as the tones.
The QLN and HLog graphs now have a "Horizontal compression" control like the Bitswaps per tone graph.
As well as the copy to clip board on the stats, a save option putting a .txt file with the snapshots would be nice?
The Stats text can now be manually saved or set to autosnapshot.
Is the refresh interval for the html pages configurable, as these seem to be fixed at 30 seconds?
The refresh interval is now configurable in the program.
Is there any way of preventing DSLstats from doing a complete screen refresh when the webserver is enabled?
All the webserver (and snapshot) activity now takes place off screen, so there's no display disruption.
If the webserver is enabled and then disabled and later enabled again then I get an access violation error message box pop up and DSLstats aborts.
Fixed.
I would like to see an option that takes a snapshot, on exit, of only the graphs that are set to autosave.
Implemented.
Only a minor cosmetic bug, but the graph line thickness setting is not applied on the SNRM per band graphs.
Fixed.
The SNRM per band still needs to be added into the .ini as you have to still have to select it manually.
Fixed (as far as I can tell)
just wanted to let you know I am still getting failed QLN and HLOG graphs, ive just checked all my saved folders from every time ive had it running and all graphs save properly except QLN and HLOG, it saves them but theres no data, they are 0KB in size
Fixed.
I intend to release v4.41 in a day or two.
-
Many thanks for all the hard work, I look forwards to the update. but I may be daring to ask for More...... ;D
On the config custom commands I use the "when dsl connection is down" option but seem to have an erratic issue with unwanted commands sometimes being sent after coming out of standby. I "think" the issue may just the network adapter taking longer to get going than dslstats. I am not sure how you are testing the connection is up and what order things happen in.
I should not be having trouble if you first check whether to modem is accessible and always just stop dead and do nothing at all if it is not instantly accessible. i.e. modem inaccessible tested first and giving stop dead and wait for next sample, and not the same as connection down. Maybe this is not the current order? If it is I need to test more!
I am in effect wondering if you are checking for a connection e.g. by ping getting nothing and then - by which time my network adapter is up - logging on? If not can you say what order things run in so I can do more intelligent tests.
Thanks in advance
-
The way the program detects the state of the modem is built into the sampling process. At each stage there is a success or failure, and if there's a failure a message is displayed to say what failed. Up to and including the result "No stats received", further actions are aborted until the next sample is due.
What I may not have got quite right is the linking of the custom commands to the various failure results, so I'll be looking more closely at that. I'm also uncomfortable about what happens during and after standby, because I have no idea in what order the different parts of the system come back to life. What I'd like to do is put DSLstats on pause immediately before the system goes into standby, and unpause it after the system has returned to life, but implementing this is beyond me at the moment.
-
Fortunately it always seem fine for me with Standby apart from this issue. If the first test is modem accessibility (not web accessibility) and if it is not accessible you do nothing apart from wait till the next sample I don't think I should have a problem. If you could check that some time it would be much appreciated.
-
If the first test is modem accessibility (not web accessibility) and if it is not accessible you do nothing apart from wait till the next sample I don't think I should have a problem.
That's what's meant to happen, but I will check again to make sure.