hello

I'm trying to connect to Zte h168n and with this command "dsl -d mediatek_telnet -u root 192.168.1.1" and it gives me this error no prompt detected

This is mostly the same as the Broadcom code, although the main difference is the different login prompt, which prevented the generic Broadcom device type working for me.

P.S. Thanks for creating this. I found DSLstats recently which helped me diagnose some issues with my phone line, but it looks like that isn't going to receive any more updates, and so it's good to see an open source project taking up the mantle.

Unable to read DSL Stats of the Speedport Pro Plus running Firmware 120141.5.0.013.0

PS C:\Users\Maxim\Downloads\go-dsl-master> ./dsl -d speedport speedport.ip

Connecting… failed: request for /html/login/index.html failed with status 307
PS C:\Users\Maxim\Downloads\go-dsl-master> ./dsl -d speedport 10.10.1.1

Connecting… failed: request for /html/login/index.html failed with status 307

So I "secured" access to my private keys behind a passphrase and the CLI application sort of works:

computer:go-dsl user$ ./dsl

Connecting… passphrase required
Fingerprint: SHA256:rcl9qcANmVORxAH5pPkMDL8TCtu+Z9jDNVmfTKLdjqo
Passphrase: 
Authenticating… done
Loading data… done

           State:    Showtime
            Mode:    VDSL2 Profile 17a
          Uptime:    32 days, 16 hours, 11 minutes

          Remote:    Broadcom 12.4.127 (194.127)
           Modem:    Infineon 5.9.1.4.0.7

     Actual rate:      116797 kbit/s      36998 kbit/s 
 Attainable rate:      140083 kbit/s      40043 kbit/s 
         MINEFTR:       81349 kbit/s    1730261 kbit/s 

         Bitswap:          on                on        
   Rate adaption:         off               off        

    Interleaving:        0.14 ms              0 ms     
             INP:        40.0 symbols      44.0 symbols
  Retransmission:          on                on        

       Vectoring:        full              full        

     Attenuation:         9.8 dB            8.3 dB     
      SNR margin:        12.5 dB            8.5 dB     
  Transmit power:        14.5 dBm          -3.5 dBm    

    RTX TX Count:      335827             37924        
     RTX C Count:       32108            223166        
    RTX UC Count:         762           1487052        

       FEC Count:           0              4298        
       CRC Count:          23               321        

        ES Count:           5               128        
       SES Count:           1                76        

but when I try the same with dsl-gui I get a prompt "The device requests a password" which neither accepts:

1. an empty password
2. the modems password
3. my ssh passphrase:

computer:go-dsl user$ ./dsl-gui 
setting password failed: no password required
setting password failed: no password required
setting password failed: no password required

Which is a pity as the 4 "spectral" plots are really nice and informative.

I've tried the following commands:

./dsl -d speedport speedport.ip -- Result: Connecting… failed: no challenge found

./dsl -d sagemcom speedport.ip -- Result: Connecting… failed: request for /js/gui-core.js failed with status 404

Am I doing something wrong?

Maybe you could add a screen shot of the GUI view of your tool to the github description, so potential users can immediately see what they can expect?

Interpretation of Hlog and QLN plots mostly depends on looking at the precise curves and deviations from theoretical curve "forms". This gets easier if the plot is centered more on the actual range of the individual data compared the the current fixed? and quite generous limits (QLN: -70 to -160 dBm/Hz; Hlog: 0 to -100 dB)

Also a genuine question, why displaying the QLN as bar and not (as is done customarily) as line graph?

Final thought: the up/down qualification in the plots could be slightly more prominent, the current color scheme is quite elegant, but also quite subtle. Maybe turn up the color for these and plot these behind the actual data (currently they seem overlayed)?his would require different colors for max and min on the SNR plots though). But this is mostly cosmetic and a matter of preference, so if you prefer your current design, that also works.

DSLstats for broadcom modems has a very interesting plot for diagnosing potential problem, in which it displays the count of Bitloading changes per carrier. I am not sure how this is implemented, but in theory it should be enough to take the absolute difference between consecutive bitloading data and just plot the count of these bitswap events per carrier. That will not be 100% correct (e.g. two bitswaps between samples might cancel each other out) but should show problematic carriers relative well.