Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 7 8 [9] 10

Author Topic: DSLstats v6.5 released  (Read 43965 times)

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 40053
  • Penguins CAN fly
    • DSLstats
Re: DSLstats v6.5 released
« Reply #120 on: June 20, 2020, 03:06:55 PM »

@tiffy: If you look at Telnet Data --> Traffic, you'll see the output of the command ifconfig (or alternative command as shown at the left hand side of the configuration). It's a list of all the network interfaces which are active in the device. Mine looks like this:

Code: [Select]
ifconfig
bcmsw     Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:118 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Base address:0xda00

br0       Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:68856245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53419591 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3672975270 (3.4 GiB)  TX bytes:2295088945 (2.1 GiB)

br1       Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:84820 errors:0 dropped:0 overruns:0 frame:0
          TX packets:91497 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9524862 (9.0 MiB)  TX bytes:4575440 (4.3 MiB)

eth0      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:61508924 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114215918 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4088558649 (3.8 GiB)  TX bytes:390757044 (372.6 MiB)
         

eth0.0    Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:65165477 errors:0 dropped:0 overruns:0 frame:0
          TX packets:118134768 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:242145966 (230.9 MiB)  TX bytes:3615219680 (3.3 GiB)

eth1      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         

eth1.0    Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33366127 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:2259707256 (2.1 GiB)

eth2      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         

eth2.0    Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33366121 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:2259706722 (2.1 GiB)

eth3      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:68859675 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53434748 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:618632271 (589.9 MiB)  TX bytes:2510658207 (2.3 GiB)
         

eth3.0    Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B4 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:68858401 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53419507 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3673775371 (3.4 GiB)  TX bytes:2295084635 (2.1 GiB)

eth4      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B6 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:424 errors:0 dropped:0 overruns:0 frame:0
          TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:26762 (26.1 KiB)  TX bytes:26762 (26.1 KiB)

ptm0      Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B7 
          inet6 addr: fe80::4e9e:ffff:fe0c:f6b7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3309839 errors:0 dropped:129 overruns:0 frame:0
          TX packets:1591266 errors:0 dropped:23 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3350130921 (3.1 GiB)  TX bytes:204436716 (194.9 MiB)

ptm0.1    Link encap:Ethernet  HWaddr 4C:9E:FF:0C:F6:B7 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3056847 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1726037 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3484061415 (3.2 GiB)  TX bytes:248237557 (236.7 MiB)

 >

At the end of the description of each interface it shows RX bytes and TX bytes (number of bytes received and sent). You can infer from these figures which interface is likely to be the one handling total traffic through the device.
Logged
  Eric

tiffy

  • Reg Member
  • ***
  • Posts: 976
Re: DSLstats v6.5 released
« Reply #121 on: June 20, 2020, 03:54:23 PM »

@roseway:
Many thanks Eric for the additional information, much appreciated.

I'll have a little play, hopefully learn something.
Logged
Zen 40/10 - DSLStats/RPi3B - ZyXEL VMG1312-B10A Modem/VMG-3925-B10B Router Huawei Cab

bndwdthseekr

  • Member
  • **
  • Posts: 26
Re: DSLstats v6.5 released
« Reply #122 on: July 16, 2020, 07:35:48 PM »

I have encountered a bit of a bug in the graph shots used for the web interface. After restarting DSLstats, a few of the graphs display a cut version of the whole graph as seen below. When I go into the bits tab and 'change tone range', then click the arrows or move the slider, then it will start posting the full graph again.

The same problem occurs with the Hlog and QLN graphs. ???

Anyone know how to fix this?
Logged
My current broadband hardware:
Modem: Cisco EHWIC-VA-DSL-A
Routing device: Raspberry Pi 4 Model B Rev 1.1

Hopefully Starlink soon?

tiffy

  • Reg Member
  • ***
  • Posts: 976
Re: DSLstats v6.5 released
« Reply #123 on: August 11, 2020, 05:54:20 PM »

DSLStats V.6.5.9., latest available version.
Have started to use the "Data Store" facility again, not via "FTP Uploads" which was the case back in MDWS days, just harvest the data files from my RPi 3B to my Win 10 desktop PC over the LAN in order to display historic data using the "Broadstairs" utility.

To keep the file count to minimum and not really requiring the Bitloading, SNR per tone, HLog & QLN historical data, I have opted to de-select the associated hourly downloads as per the Data Store  GUI options, however, I am still getting the 4 *.zip files per hour regardless of the options being selected or not.
(see attached screen snapshot)

I fully appreciate that Eric (roseway) is unable to offer support for his excellent utility at present but just wondering if this is an issue, known or otherwise or am I getting in a muddle once again ?
Logged
Zen 40/10 - DSLStats/RPi3B - ZyXEL VMG1312-B10A Modem/VMG-3925-B10B Router Huawei Cab

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 40053
  • Penguins CAN fly
    • DSLstats
Re: DSLstats v6.5 released
« Reply #124 on: August 11, 2020, 06:25:15 PM »

The only thing I can think of is that you may need to close down DSLstats to save the settings, and restart it before the changes take effect.
Logged
  Eric

tiffy

  • Reg Member
  • ***
  • Posts: 976
Re: DSLstats v6.5 released
« Reply #125 on: August 13, 2020, 11:42:54 AM »

@roseway:

Thanks for the response Eric, much appreciated.

I record my line stat's on a 4 day cycle so delayed trying a program shutdown/re-boot, now done but has had no effect on the de-selection of the Data Store *.zip files, still being stored regardless of selection or otherwise.

In my case not a big issue, I use a very simple Windows batch file periodically run with Task Scheduler, I can just omit to copy the *.zip files to my Win PC, I already delete the RPi daily Data Store files once copied.
You do of course have the FTP Uploading facility incorporated within the DSLStats program but I never managed to get this working across my LAN, the simple batch file utility although not very elegant works for me.
Logged
Zen 40/10 - DSLStats/RPi3B - ZyXEL VMG1312-B10A Modem/VMG-3925-B10B Router Huawei Cab

bndwdthseekr

  • Member
  • **
  • Posts: 26
Re: DSLstats v6.5 released
« Reply #126 on: January 21, 2021, 02:31:52 AM »

Anyone know what could cause this in the event log? It prints this message every update.

Code: [Select]
20 Jan 2021 21:24:51 Error processing bitloading
20 Jan 2021 21:25:06 Error processing bitloading
Logged
My current broadband hardware:
Modem: Cisco EHWIC-VA-DSL-A
Routing device: Raspberry Pi 4 Model B Rev 1.1

Hopefully Starlink soon?

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 40053
  • Penguins CAN fly
    • DSLstats
Re: DSLstats v6.5 released
« Reply #127 on: January 21, 2021, 10:16:18 AM »

Unfortunately this is a catch-all response which saves the program from misbehaving when an unknown error occurs in the section mentioned. The cause is quite probably something unexpected in the bitloading data from the particular modem in use.
The only thing I can suggest is to try a different Broadcom based modem.
Logged
  Eric

bndwdthseekr

  • Member
  • **
  • Posts: 26
Re: DSLstats v6.5 released
« Reply #128 on: January 22, 2021, 10:21:33 AM »

Unfortunately this is a catch-all response which saves the program from misbehaving when an unknown error occurs in the section mentioned. The cause is quite probably something unexpected in the bitloading data from the particular modem in use.
The only thing I can suggest is to try a different Broadcom based modem.

The strange part is it works when I first start the program (see attached), but I don't think its updating the bitloading graph after a certain point. Maybe Ill compile dslstats from source and try to narrow down the problem.


Code: [Select]
xdslctl info --Bits

The output of the command is :

/bin/xdslctl: ADSL driver and PHY status

Status: Showtime

Last Retrain Reason: 0

Last initialization procedure status: 0

Max: Upstream rate = 1276 Kbps, Downstream rate = 12208 Kbps

Channel: FAST, Upstream rate = 1024 Kbps, Downstream rate = 6944 Kbps



Tone number      Bit Allocation

   0 0

   1 0

   2 0

   3 0

   4 0

   5 0

   6 6

   7 5

   8 7

   9 8

   10 9

   11 10

   12 11

   13 11

   14 12

   15 12

   16 12

   17 12

   18 13

   19 12

   20 13

   21 13

   22 13

   23 12

   24 13

   25 12

   26 12

   27 12

   28 11

   29 11

   30 10

   31 9

   32 0

   33 0

   34 2

   35 2

   36 2

   37 3

   38 3

   39 3

   40 4

   41 4

   42 4

   43 5

   44 5

   45 5

   46 5

   47 6

   48 6

   49 7

   50 8

   51 8

   52 9

   53 9

   54 9

   55 10

   56 10

   57 10

   58 11

   59 11

   60 11

   61 11

   62 11

   63 11

   64 0

   65 11

   66 11

   67 11

   68 11

   69 11

   70 11

   71 11

   72 11

   73 11

   74 11

   75 11

   76 11

   77 12

   78 12

   79 11

   80 11

   81 11

   82 11

   83 11

   84 11

   85 11

   86 11

   87 11

   88 11

   89 11

   90 11

   91 11

   92 11

   93 11

   94 11

   95 11

   96 11

   97 11

   98 11

   99 11

   100 10

   101 11

   102 10

   103 11

   104 10

   105 10

   106 10

   107 10

   108 11

   109 11

   110 2

   111 11

   112 10

   113 10

   114 11

   115 10

   116 10

   117 10

   118 10

   119 10

   120 10

   121 11

   122 11

   123 10

   124 10

   125 10

   126 9

   127 9

   128 9

   129 9

   130 9

   131 9

   132 9

   133 9

   134 9

   135 9

   136 9

   137 9

   138 9

   139 9

   140 9

   141 9

   142 9

   143 9

   144 9

   145 9

   146 8

   147 9

   148 9

   149 9

   150 9

   151 9

   152 9

   153 9

   154 9

   155 9

   156 9

   157 9

   158 9

   159 9

   160 9

   161 9

   162 8

   163 8

   164 8

   165 8

   166 8

   167 8

   168 9

   169 8

   170 8

   171 8

   172 8

   173 8

   174 8

   175 8

   176 7

   177 8

   178 8

   179 8

   180 8

   181 8

   182 8

   183 8

   184 8

   185 8

   186 8

   187 8

   188 8

   189 8

   190 8

   191 8

   192 8

   193 8

   194 8

   195 8

   196 8

   197 8

   198 8

   199 8

   200 8

   201 8

   202 8

   203 8

   204 8

   205 8

   206 8

   207 8

   208 8

   209 7

   210 8

   211 8

   212 8

   213 8

   214 8

   215 8

   216 8

   217 8

   218 8

   219 8

   220 8

   221 7

   222 7

   223 7

   224 8

   225 7

   226 7

   227 7

   228 7

   229 7

   230 6

   231 7

   232 7

   233 7

   234 7

   235 7

   236 6

   237 7

   238 6

   239 7

   240 7

   241 6

   242 6

   243 6

   244 6

   245 6

   246 6

   247 5

   248 5

   249 5

   250 5

   251 5

   252 5

   253 4

   254 4

   255 0





BFR#
« Last Edit: January 22, 2021, 12:47:10 PM by bndwdthseekr »
Logged
My current broadband hardware:
Modem: Cisco EHWIC-VA-DSL-A
Routing device: Raspberry Pi 4 Model B Rev 1.1

Hopefully Starlink soon?

22over7

  • Reg Member
  • ***
  • Posts: 101
Re: DSLstats v6.5 released
« Reply #129 on: February 07, 2021, 11:17:15 PM »

After what seems like several happy and complacent years of running dslstats32RPi-6.5.9/dslstats ,
our neighbourhood in Edinburgh experienced a splendid 15 minute power-cut.
So naturally, when it turned on, I turned to my friend 6.5.9. to tell me the gory details, and where my SNR stands.
The pi running he/she/it/them chunters on indefatigably(?),
but  6.5.9 now keels over and over with a segfault after about a minute each time.

My modem (Zyxel1312-B10A) is well enough to send this, and I can login by ssh, http etc.
somethings in dslstats' infrastructure must have changed enough to push it into the
clutches of the grim reaper.

Or not? Is any hope of resuscitating (no medic, me) my pal, or some looking up, in hope, her/his/their progeny?


Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 40053
  • Penguins CAN fly
    • DSLstats
Re: DSLstats v6.5 released
« Reply #130 on: February 08, 2021, 06:34:06 AM »

At risk of stating the obvious, 6.5.9 is 6.5.9. It hasn't changed in any way since it was first released. The version which is available to download from http://dslstats.me.uk hasn't been touched since it was originally uploaded.
Logged
  Eric

skyeci

  • Kitizen
  • ****
  • Posts: 1201
    • Zen ECI line stats
Re: DSLstats v6.5 released
« Reply #131 on: February 08, 2021, 10:28:49 AM »

I would looking at your sd card on the pi. I have had issues with crashes from dsl stats which after changing the sdcard all is well...so assumed the old card was becoming faulty.
Logged
Zen 80/20 - Zyxel VMG3925-b10b(bridge mode) + Opnsense(i5 Qotom) with IPV6 , AC-88U WAP- ECI cab,

click for ECI VDSL cab line stats by pi3


click for line stats by pi3/Huawei VDSL cab 

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 32622
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: DSLstats v6.5 released
« Reply #132 on: February 11, 2021, 02:37:08 AM »

Quote
but  6.5.9 now keels over and over with a segfault after about a minute each time

A segfault means that DSLstats is attempting to read (or failing to write to) something which is no longer there (in memory).
This infers that segments of the storage drive has become corrupt.  The storage drive (memory drive) can be a hard drive, SDcard,  USB memory stick or even CD/DVD depending upon the type of memory medium DSLstats is running from. 

Basically - your storage medium is duff - most likely caused by the power cut if the operating system was busy at the time and something was attempting to write to disk at the time power went off.  Depending upon the type of storage your operating system may be able to run a repair or declare segments as unusable.    However. take it as a warning telling you to get new drive asap, before the whole drive fails.

To be more specific the error you are seeing means that part of the drive holding the prog DSLstats is now corrupt and therefore it can no longer run properly   OR DSLstats is trying to read data stored on parts of the drive which are now corrupt    OR the drive is now so corrupt that DSLstats cant record (write) any new data.   

For more info see Unreadable File Record Segments

---------------

PS I did happen to see your reply to one of my moderators the other night, but I was not in a position to type at that time. :( 
FYI He was trying to be helpful - for all he knew and from the info in your first post it could have been part of the drive that held the OS which was corrupt.  As he said, power cuts are well known to cause failure of the memory drives particularly on R-Pi's which do not always take kindly to not being shut down correctly.   It wasn't clear that you were running from a USB memory stick.  If everything else on the memory stick appears to be working OK then I'd guess the bad segments are where DSLstats was stored on the drive so its caused the prog to become corrupt, so you will need to redownload it.   It is time though to get a new drive because you dont know what other segments are damaged too or if other parts of the drive may not also fail in the near future.   


Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Alex Atkin UK

  • Kitizen
  • ****
  • Posts: 2098
    • My Broadband History
Re: DSLstats v6.5 released
« Reply #133 on: February 11, 2021, 01:47:53 PM »

Sadly a lot of people don't seem to understand that NAND is far more sensitive to power cuts.  A write under a low power state in some cases can cause permanent damage.

SSDs I believe get round this by detecting a power cut and having enough residual energy in a capacitor to finish writing safely, SD cards and USB sticks are unlikely to be that clever plus likely use cheaper less resilient NAND to begin with.
Logged
INTAKE (ECI) Zen: Home Hub 5A OpenWrt Plusnet: VMG-3925-B10B Voxi 4G: Hauwei B535-232 Router: pfSense (i5-7200U) WiFi: Ubiquiti nanoHD
Thinkbroadband Quality Monitors & Zen Referral

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 1727
Re: DSLstats v6.5 released
« Reply #134 on: February 17, 2021, 10:14:06 AM »

Does anyone know if DSLstats can be used with a Technicolor DGA0122? If so is the configuration simple. Asking for a friend (really).
Logged
Line rental: Pulse8, Broadband: AAISP Home::1 FTTC 80/20, Mobile: id Mobile
Pages: 1 ... 7 8 [9] 10