Print

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

[roseway]

>>> But it would be nice to auto grab at say 2 hours.

I can certainly make it an option.

[kitz]

Thank you eric.   I previously thought DSLstats was very good, but its only when you have an issue on the line that you start thinking 'Wouldn't it be good if it could do this or that'.   The configurable options certainly make it the best realtime tool there is for the HG612 and other supported routers.   Together with BE's scripts for FTTC, the HG612 has some pretty comprehensive monitoring tools

[les-70]

  Eric, Thanks from me too! I am finding it really useful and solid in its use.  I have dropped back from my HG622 to my old and reliable DG834Gv4 with DGTeam and can report that, as expected, the "traffic settings" for a DG834GT work for the DG834Gv4 as well.

[roseway]

Thanks Les, I really appreciate that.

[tickmike]

Hello Eric.
I have had to start using my 'SpeedTouch 536' again because my Netgear DG834GT kept dropping the connection .
Is there any similar router settings I can use ? or is it not compatible with the ones on the list ?.

[roseway]

Hello Michael,

I guess it's just possible that DSLstats will work with the ST536 if you select one of the other Thomson routers as the template for the configuration, but I rather doubt it, I'm afraid.

[tickmike]

Hello Michael,

I guess it's just possible that DSLstats will work with the ST536 if you select one of the other Thomson routers as the template for the configuration, but I rather doubt it, I'm afraid.

There is no 'ST536' in the list    Whats the Belkin one with the name 'Bob' ?.
re " other Thomson routers"  can you tell me which they are please. 

[roseway]

The Thomson routers are actually shown as Technicolor in the list. It doesn't matter which one you choose, because they all have the same configuration. As I said, I rather doubt that DSLstats will work with the ST536 anyway, but selecting one of the Technicolor routers would be a place to start if you want to try.

The Belkin one is F1P1243EGau which seems to be known as "BoB" in some places.

[tickmike]

'ST536'  that's my router code 
I can get some of the readings but no graphs 

[roseway]

That doesn't surprise me unfortunately. I expect I could get it to work given time, but time is in short supply at the moment.

[roseway]

Eric having tested the 0.0.38 interface for a few days it seems to track the internet traffic just fine. This morning I swapped to the ppp256 for a few minutes and it was recording traffic down like it was going out of fashion! See the attached snapshots of the ppp256 data over just 2 or 3 minutes. So at least on my HG622 0.0.38 seems best.

Stuart

Stuart, I've now become even more confused about this issue. I've just swapped out my usual HG612 and put an HG622 in its place, and on my system there isn't a 0.0.38 interface listed. The nearest interface name is nas_0_38 which looks as though it may have the right information. So I'm using the same router as you, and we're connected to the same ISP, but the two routers seem to have different interfaces.

Code: [Select]

ifconfig
br0       Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:48 
          inet addr:192.168.1.254  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19492 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19605 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1172414 (1.1 MiB)  TX bytes:2397818 (2.2 MiB)

eth0      Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:48 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19998 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19884 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1687513 (1.6 MiB)  TX bytes:2664343 (2.5 MiB)
          Interrupt:40 Base address:0x6a00

eth0.4    Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:48 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:445 errors:0 dropped:0 overruns:0 frame:0
          TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:192507 (187.9 KiB)  TX bytes:37410 (36.5 KiB)
         

eth0.5    Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:48 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19731 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1495006 (1.4 MiB)  TX bytes:2626933 (2.5 MiB)

imq0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16000  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:11000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

imq1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16000  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:11000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

imq2      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16000  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:11000
          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
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1176 (1.1 KiB)  TX bytes:1176 (1.1 KiB)

nas_0_38  Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:49 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1293 errors:533 dropped:0 overruns:0 frame:0
          TX packets:1211 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1438000 (1.3 MiB)  TX bytes:219235 (214.0 KiB)

nas_0_38_0 Link encap:Ethernet  HWaddr 04:C0:6F:E8:D3:49 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:841 errors:0 dropped:0 overruns:0 frame:0
          TX packets:705 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:85215 (83.2 KiB)  TX bytes:51509 (50.3 KiB)

ppp256    Link encap:Point-to-Point Protocol 
          inet addr:aa.bb.cc.dd  P-t-P:92.20.144.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:728 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:73848 (72.1 KiB)  TX bytes:190502 (186.0 KiB)

sar       Link encap:UNSPEC  HWaddr FE-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00 
          UP NOTRAILERS RUNNING NOARP  MTU:0  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:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:50 Base address:0x5220

swc       Link encap:UNSPEC  HWaddr FE-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00 
          UP NOTRAILERS RUNNING NOARP  MTU:0  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:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:42 Base address:0x6a40

Correction to the above: I've just downloaded a 250 MB file and it didn't register at all on the nas_0_38 interface, so that's not the one. It registered on the br0 and ppp256 interfaces (but reversed) but neither of these delivers consistent values. As things stand at present, none of the interfaces delivers values which I can take as correct.