Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

A fairly substantial upgrade this time, with several new features and improvements:

- rewrite of section of program dealing with telnet access (code cleanup)
- added an option to tweak the SNR margin
- added graphs showing bitswaps per tone and bitswaps per minute
- rearranged the tabs to group related graphs under one main tab
- renamed Error log as 'Event log' and it now includes entries for other events
- added a date indicator to the time scrolling graphs
- true DSL link time is shown on the status bar for those routers which provide this data
- corrected error in VDSL2 band plan determination
- Help button now takes you to the program website instead of local help files

Full information and downloads at http://rsux.plainroad.me.uk

[burakkucat]

Someone has, clearly, been very busy. Thank you for this new, improved release, Eric.

It has already been downloaded (even though the date is not yet 1st February 2013) and is about to be tested. 

[roseway]

>>> (even though the date is not yet 1st February 2013)

I thought I would make Christmas come early this year.

[rhohne]

Can only get it to work on DG834GT if I enable "Requires command to enter shell" (default command gives me second busybox shell). When disabled I get

Code: [Select]

30 Jan 2013 22:23:45 Unknown Event
30 Jan 2013 22:23:45 Recording paused
30 Jan 2013 22:23:43 Recording started
where the unknown event is the "Second stage login failure".

First couple of times I ran it on XP I got access violation errors when exiting rsw, however I'm now unable to reproduce the error.

[roseway]

Thanks, I'll look at those points.

[roseway]

I can see the reason for this now: Netgear routers have to be put into debug mode before you can gain telnet access, and in this mode the telnet command takes you straight into the CLI without having to log in. So when the program tries to log in, it's seen as an invalid CLI command. Using the second stage command just happens to work around this issue because of the login logic of the program.

I'm going to have to make a couple of changes in the login logic, which shouldn't take long.

[broadstairs]

Eric just a couple of very minor points, using the 32bit linux version. The executable does not extract with the executable permission which did happen with all the previous versions. Also on first run it hung on hitting the start button and had to be killed. I then restarted it, went into settings and checked them and hit apply and now its running fine. So it appears that I needed to save settings even though it had indeed picked up all my settings.

Stuart

[rhohne]

Netgear routers have to be put into debug mode before you can gain telnet access, and in this mode the telnet command takes you straight into the CLI without having to log in. So when the program tries to log in, it's seen as an invalid CLI command. Using the second stage command just happens to work around this issue because of the login logic of the program.

The use of enabling the debug mode should be optional, as it is not needed for DGTEAM firmware. With DGTEAM you get the normal login sequence.

[les-70]

  Works well with DG834G with DGteam but I had to discover for myself what has already been commented on.  I am using Annex m and the usual SNRM tweak does work with that on the line. The router disconnects then fails to reconnect.  It is same with DMT but just fine within the DGteam firmware and its GUI options approach. 

 When you have recovered from your initial debugging perhaps you could think on this.  Maybe a command variation is required to re-specify annex m or explicitly force the resync.  If you or others have any suggestions I can try them in telnet.

     Thanks

             

[les-70]

   Must have had a typo in my various tries.       In fact a command I thought I had tried did work  i.e.   adslctl configure --snr 100 --mod m . If you get bored maybe you could add an annex tick box in the configurations and add the "--mod m"  with the "--snr" tweak.   

   Yours hopefully!

[roseway]

Netgear routers have to be put into debug mode before you can gain telnet access, and in this mode the telnet command takes you straight into the CLI without having to log in. So when the program tries to log in, it's seen as an invalid CLI command. Using the second stage command just happens to work around this issue because of the login logic of the program.

The use of enabling the debug mode should be optional, as it is not needed for DGTEAM firmware. With DGTEAM you get the normal login sequence.

Sorry, I didn't make myself clear. The program doesn't have any capability to apply debug mode itself, because that requires use of the web interface. I was assuming (wrongly) that you were using standard Netgear firmware and had put it in debug mode.

As it happens, I've located an old DG834GT and resolved the problem, so my initial theory was wrong.

[roseway]

   Must have had a typo in my various tries.       In fact a command I thought I had tried did work  i.e.   adslctl configure --snr 100 --mod m . If you get bored maybe you could add an annex tick box in the configurations and add the "--mod m"  with the "--snr" tweak.   

   Yours hopefully!

Yes, that sounds a good idea. I'll do this shortly, but probably not immediately.

[roseway]

Eric just a couple of very minor points, using the 32bit linux version. The executable does not extract with the executable permission which did happen with all the previous versions.

I'm not sure how this happened, because I haven't changed the way I build the program, but you're right. I'll check it in future.

Also on first run it hung on hitting the start button and had to be killed. I then restarted it, went into settings and checked them and hit apply and now its running fine. So it appears that I needed to save settings even though it had indeed picked up all my settings.

If you close rs-ux and start it up again now, does it still show this problem, or was it just for the first run of this version?

[krypton]

Thank you for this new release.

Sadly it does not connect anymore, because the new version forces to enter the login details. But my device does not need any authentication at this point. If I input anything random, it fails with "second stage login failure".

Do you have an idea how to get the connection working?

[roseway]

I've just this minute uploaded a corrected version v2.0.1 to http://rsux.plainroad.me.uk