Kitz Forum

Broadband Related => ADSL Issues => Topic started by: renluop on June 03, 2017, 04:46:47 PM

Title: Today's shock resync
Post by: renluop on June 03, 2017, 04:46:47 PM
First here are the final posts by me in another thread
Nothing special in  mind. Have you had any other crashes in any other applications? Usually memory problems show up on different applications depending on the order they are started as they may get different memory locations. If I get unexplained crashes I run Memcheck86 which is a stand-alone memory test program bootable from a CD/DVD or memory stick. You dont need to understand anything about any errors if you get them, it should run error free and if not you have a problem in one of the memory cards (if you have more than one, looks like you may only have one). Then it needs replacing, if it runs error free then obviously its not that.

Might be better to take this discussion to a separate thread if it continues....

Stuart

I wouldn't think it related, but sometimes getting a wireless connection is a !!!!!!!
As you say we'll leave it there on this thread.

Hi renluop Your wireless connection is pertinent to this issue and a few others
Using wireless, if there is a break in wifi, it can cause floating point issues etc in dslstats. 

I use wifi, and have seen a floating point issue after wifi had an issue
I have never reported this though, as the only advise I have seen for dslstats, is to use hardwire connection only, no wifi (guess that means wifi not supported due to issues wifi could give, which are not a result of dslstats)
I hope that helps a little
Many thanks
John

and thereby hangs another problem!
Some say that Billion 8800NL can play up, if there are both an Ethernet cable between router and computer active and also wireless. Wireless connects printer, wife's IPad and bedside radio. I use HomePlugs between router and digbox.
Since getting rid of cable from router tocomputer things seem much better connection wise.

Having thought about it, I am not for now going to run MemTest 86, and BTW there is a MemTest 64 too from www.techpowerup.com. I wonder if it is a genuine development of 86, or something questionable.

Doesn't MemTest lock you out from any other activity for considerable time, especially if a number of passes are needed?
==============
d2d4j 's comment led me to reconnect a cable from computer to the router at around 10.30 with sync a little over 6000 kbps. Tweaking SNR down by 1 dB gave and extra 400 kbps. My Network and Internet Settings showed both wired and wireless connections working with neither a red cross of exclamation mark by them.

Until recently I was away from the computer, and I've found that there had been another invalid floating point  incident. This must have been around 12.30, given the flat line of SNR and Connection Speed. Sync had plummeted to 3481 kbps, and only bits up to #117 are active!

As for the network connections, both wired and wireless are working, yet wireless bears that red cross.

I haven't a clue what is gong on, and i'd bet you're in agreement that I haven't a clue! :blush: :)

if you want I will post graphs etc, should you want to deign to carry this furhter.



Title: Re: Today's shock resync
Post by: d2d4j on June 03, 2017, 06:51:43 PM
Hi renluop

I would personally always advise that you only ever have 1 network connection (either hardwired or wifi)

The pc can get a little confused if not fully and carefully setup for multi networks, more so if on different nodes

It's interesting that you state wifi had Red Cross and a floating point error

I'm sorry if I'm wrong and others may disagree but for 99% of users, it has always been the best advice

Many thanks

John
Title: Re: Today's shock resync
Post by: renluop on June 03, 2017, 10:55:27 PM
So, given your earlier comment about using only a wired connection for DSLStats, because of wireless producing more invalid floating points, that could mean that DSLStats is becoming less useful, because wireless connections are wanted for frequently used h/ware. That's a shame as it's a very useful app.

Multi networks: you mean my present use of wried and wireless?
different nodes: can you expand on that, please? I'm not sure what nodes.
Title: Re: Today's shock resync
Post by: roseway on June 03, 2017, 11:05:00 PM
I can't say that I agree with that advice. It depends on how your system is arranged. You're using a modem/router, and if the PC is connected directly to the router, and DSLstats is running on the PC, there's not going to be any conflict with other devices connecting wirelessly to the router.
Title: Re: Today's shock resync
Post by: d2d4j on June 03, 2017, 11:26:09 PM
Hi

I meant if there are multi network connections (does not matter if hardwired or wifi, mixed or same), you have multiple exit entry points, and could transmit on either

If your not sure what I mean, try setting 2 connections on same gateway (windows immediately gives a warning)

I could be wrong, which I do not mind been wrong and I did say others may disagree, which I do not mind, but I have seen it in action/real life with clients

Many thanks

John
Title: Re: Today's shock resync
Post by: renluop on June 03, 2017, 11:39:40 PM
Hi

I meant if there are multi network connections (does not matter if hardwired or wifi, mixed or same), you have multiple exit entry points, and could transmit on either

If your not sure what I mean, try setting 2 connections on same gateway (windows immediately gives a warning)

I could be wrong, which I do not mind been wrong and I did say others may disagree, which I do not mind, but I have seen it in action/real life with clients

Many thanks

John
I'm lost! :-[ :'(
Title: Re: Today's shock resync
Post by: d2d4j on June 03, 2017, 11:40:26 PM
Hi

Sorry, thinking about how best to explain

Please could I ask how you know which connection is been used for dslstats

Come to that, how do you know which connection is been used mostly, or if the connection changes mid session (connection)

I believe you cannot, nor can you dictate which connection only to use, as windows pc software does not have this capability

Also, if the wifi devices are connected to the network, and your pc is only hardwited to the network, all access to the wifi devices are available as there on the same network (different networks may not be the case)

As i said though, I could be wrong so apologies in advance

Many thanks

John
Title: Re: Today's shock resync
Post by: roseway on June 04, 2017, 07:23:14 AM
I see what you mean John.

I know very little about Windows, but surely you can disable the WiFi interface in the PC, so you can be sure that it's only connecting by direct ethernet?
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 09:07:41 AM
Hi

Sorry, thinking about how best to explain

Please could I ask how you know which connection is been used for dslstats

Come to that, how do you know which connection is been used mostly, or if the connection changes mid session (connection)

I believe you cannot, nor can you dictate which connection only to use, as windows pc software does not have this capability

Also, if the wifi devices are connected to the network, and your pc is only hardwited to the network, all access to the wifi devices are available as there on the same network (different networks may not be the case)

As i said though, I could be wrong so apologies in advance

Many thanks

John
My assumption was that by having an Ethernet cable between router and computer, that would be the situation. I guess that's not so, then?
Title: Re: Today's shock resync
Post by: d2d4j on June 04, 2017, 10:21:08 AM
Hi

@roseway, glad I explained slightly better hopefully sorry

On most windows computers, laptops and all xbox360/one, when hardware network is detected as been active, wifi is turned off automatically (you can over ride this and turn wifi back on though, so you then have multi connections)

Yes, you can disable wifi, but you are best advised to restart pc if you disable wifi, as I do not know the state/condition of pc, so any routes maybe flushed

Personally I would set to hardwired, disable wifi and restart pc. Then leave it as is (no changes) for 7 days or until floating point is seen again

As I said this may or may not the issue with floating point, but you need to exclude it as a cause, and as I said, I have only ever seen floating point error when wifi had an issue (this is nothing to do with dslstats but wifi), and I understand I will have some issues if using wifi with dslstats, so I accept that

Many thanks and I hope that helps a little, but sorry if I'm wrong

John
Title: Re: Today's shock resync
Post by: roseway on June 04, 2017, 10:25:48 AM
Thanks again, that sounds like good advice.
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 10:50:12 AM
My age is telling on me! In the simplest of language i hope someone will summarise how I need set up my network to ensure, as much as possible DSLStats works properly, hardware connected wirelessly does like wise.

BTW the loss of speed corrected it self last night back to 6394 kbps with interleaving 32/4. Momentarily at ~10.30 it shot up to ~7600 kbps with interleaving 64/2. Weird!?
Title: Re: Today's shock resync
Post by: d2d4j on June 04, 2017, 12:02:19 PM
Hi

@roseway, I am not asking for any help on the logs shown below

@renluop, I would do the following (others may disagree sorry)

Disable WIFI

Disable LAN

Set LAN to DHCP (for IP and DNS)

Enable LAN

Open a command prompt (wit Administrator rights)

ipconfig/flushdns

exit

close DSLstats in full

Restart pc

ping router

ping bbc.co.uk

start dslstats

leave network as is for 7 days or until floating point is seen earlier then 7 days.  If floating point issue is not seen within 7 days, it is likey to be the wifi causing the issue.  If it reappears, it may not be the wifi causing the issue, but you are still best to advised to leave network in a hardwired configuration until your happy with stability of programs (not just dslstats), and then you can change as you want/need.  However, I would advise you use only 1 network interface (either hardwired or wifi)

I hope that helps a little

also, below is a sample of my dslstats, but I have not contacted Roseway, for 2 reasons, firstly, it is 5.9 but a few versions behind, and secondly, it is connected over wifi.

Lastly, I do not watch my stats, very rarely login to view them, nor do I become obessive with getting the max speed (I would rather have a stable connection running slower then a fast connection with errors/retransmits).  We have a very unique network setup here, with multiple external IP's, on many Vlans, firewalls, perimeter monitoring, VPN's VPS's etc...

I remember when openreach first installed FTTC, they said they had to show FTTC working before sign off using client computer.  HAHA, I said good luck and no access to our systems would be given.  We agreed his laptop connected, so that as good enough.  poor chap, his face was a picture when he saw what he might have to change on all systems.  Oh and it was the time when the hg612 had to be wall mounted, which we are still using our orginal hg612.

Many thanks

John

02 Jun 2017 11:19:36   Configuration files stored in C:\Users\*********\AppData\Local\dslstats\
02 Jun 2017 11:19:36   The configured modem/router is Huawei HG612
02 Jun 2017 11:19:36   Option "HG612-Modem-Stats co-operation" was set
02 Jun 2017 11:19:36   Snapshot folder is C:\Users\*********\AppData\Local\dslstats\
02 Jun 2017 11:19:39   Recording started

02 Jun 2017 11:19:53   IP address is now 111.111.111.111
02 Jun 2017 13:57:45   Implausible down traffic value reported by modem/router
02 Jun 2017 15:10:46   Implausible down traffic value reported by modem/router
02 Jun 2017 15:13:45   Implausible down traffic value reported by modem/router
02 Jun 2017 15:15:45   Implausible down traffic value reported by modem/router
02 Jun 2017 17:10:45   Implausible down traffic value reported by modem/router
02 Jun 2017 21:52:56   Timeout while collecting bitloading data
02 Jun 2017 21:52:57   Telnet timeout
02 Jun 2017 21:58:56   Timeout while collecting bitloading data
02 Jun 2017 21:58:57   Telnet timeout
02 Jun 2017 22:16:56   Timeout while collecting bitloading data
02 Jun 2017 22:16:57   Telnet timeout
02 Jun 2017 22:25:57   Timeout while collecting bitloading data
02 Jun 2017 22:25:57   Telnet timeout
02 Jun 2017 22:26:56   Timeout while collecting bitloading data
02 Jun 2017 22:26:57   Telnet timeout
02 Jun 2017 22:27:57   Timeout while collecting bitloading data
02 Jun 2017 22:27:57   Unable to collect stats 3 or more times in succession
02 Jun 2017 22:27:58   Telnet timeout
02 Jun 2017 22:28:56   Timeout while collecting bitloading data
02 Jun 2017 22:28:57   Telnet timeout
02 Jun 2017 22:29:57   Timeout while collecting bitloading data
02 Jun 2017 22:29:57   Telnet timeout
02 Jun 2017 22:30:56   Timeout while collecting bitloading data
02 Jun 2017 22:30:57   Telnet timeout
02 Jun 2017 22:32:56   Timeout while collecting bitloading data
02 Jun 2017 22:32:56   Telnet timeout
02 Jun 2017 22:33:58   Timeout while collecting SNR per tone
02 Jun 2017 22:33:59   Telnet timeout
02 Jun 2017 22:34:57   Timeout while collecting bitloading data
02 Jun 2017 22:34:57   Unable to collect stats 3 or more times in succession
02 Jun 2017 22:34:57   Telnet timeout
02 Jun 2017 22:57:45   Implausible down traffic value reported by modem/router
02 Jun 2017 22:59:43   *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
02 Jun 2017 22:59:43   Second stage login failed
03 Jun 2017 01:47:45   Implausible down traffic value reported by modem/router
03 Jun 2017 04:54:45   Implausible down traffic value reported by modem/router
03 Jun 2017 04:59:45   Implausible down traffic value reported by modem/router
03 Jun 2017 06:00:42   Unable to login to modem/router
03 Jun 2017 07:56:44   Implausible down traffic value reported by modem/router
03 Jun 2017 08:39:58   Timeout while retrieving stats
03 Jun 2017 08:39:58   No stats received
03 Jun 2017 11:21:46   Deleted snapshots in folder C:\Users\*********\AppData\Local\dslstats\2017-05-27
03 Jun 2017 13:12:56   Timeout while collecting bitloading data
03 Jun 2017 13:12:57   Telnet timeout
03 Jun 2017 13:14:56   Timeout while collecting bitloading data
03 Jun 2017 13:14:57   Telnet timeout
03 Jun 2017 13:15:56   Timeout while collecting bitloading data
03 Jun 2017 13:15:57   Telnet timeout
03 Jun 2017 13:17:57   Timeout while collecting bitloading data
03 Jun 2017 13:17:57   Telnet timeout
03 Jun 2017 13:19:56   Timeout while collecting bitloading data
03 Jun 2017 13:19:57   Telnet timeout
03 Jun 2017 13:20:56   Timeout while collecting bitloading data
03 Jun 2017 13:20:57   Telnet timeout
03 Jun 2017 13:23:56   Timeout while collecting bitloading data
03 Jun 2017 13:23:57   Telnet timeout
03 Jun 2017 13:24:56   Timeout while collecting bitloading data
03 Jun 2017 13:24:57   Telnet timeout
03 Jun 2017 13:25:57   Timeout while collecting bitloading data
03 Jun 2017 13:25:58   Unable to collect stats 3 or more times in succession
03 Jun 2017 13:25:58   Telnet timeout
03 Jun 2017 13:26:56   Timeout while collecting bitloading data
03 Jun 2017 13:26:57   Telnet timeout
03 Jun 2017 13:27:56   Timeout while collecting bitloading data
03 Jun 2017 13:27:57   Telnet timeout
03 Jun 2017 13:29:57   Timeout while collecting bitloading data
03 Jun 2017 13:29:58   Telnet timeout
03 Jun 2017 13:30:57   Timeout while retrieving stats
03 Jun 2017 13:30:57   No stats received
03 Jun 2017 13:31:57   Timeout while retrieving stats
03 Jun 2017 13:31:57   Unable to collect stats 3 or more times in succession
03 Jun 2017 13:31:57   No stats received
03 Jun 2017 13:32:56   Timeout while collecting bitloading data
03 Jun 2017 13:32:57   Telnet timeout
03 Jun 2017 13:33:56   Timeout while retrieving stats
03 Jun 2017 13:33:56   No stats received
03 Jun 2017 13:34:58   Timeout while collecting SNR per tone
03 Jun 2017 13:34:59   Telnet timeout
03 Jun 2017 13:36:56   Timeout while collecting bitloading data
03 Jun 2017 13:36:57   Telnet timeout
03 Jun 2017 13:37:57   Timeout while collecting bitloading data
03 Jun 2017 13:37:57   Telnet timeout
03 Jun 2017 13:38:56   Timeout while collecting bitloading data
03 Jun 2017 13:38:56   Unable to collect stats 3 or more times in succession
03 Jun 2017 13:38:57   Telnet timeout
03 Jun 2017 13:39:58   Timeout while retrieving stats
03 Jun 2017 13:39:58   No stats received
03 Jun 2017 13:40:56   Timeout while collecting bitloading data
03 Jun 2017 13:40:57   Telnet timeout
03 Jun 2017 13:41:56   Timeout while retrieving stats
03 Jun 2017 13:41:56   No stats received
03 Jun 2017 13:42:44   *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
03 Jun 2017 13:42:44   Second stage login failed
03 Jun 2017 13:43:57   Timeout while collecting bitloading data
03 Jun 2017 13:43:57   Telnet timeout
03 Jun 2017 13:44:58   Timeout while retrieving stats
03 Jun 2017 13:44:58   No stats received
03 Jun 2017 13:45:56   Timeout while retrieving stats
03 Jun 2017 13:45:56   No stats received
03 Jun 2017 13:46:56   Timeout while retrieving stats
03 Jun 2017 13:46:56   No stats received
03 Jun 2017 13:47:56   Timeout while retrieving stats
03 Jun 2017 13:47:56   No stats received
03 Jun 2017 13:48:56   Timeout while retrieving stats
03 Jun 2017 13:48:56   No stats received
03 Jun 2017 13:50:56   Timeout while retrieving stats
03 Jun 2017 13:50:56   No stats received
03 Jun 2017 15:16:56   Timeout while collecting bitloading data
03 Jun 2017 15:16:57   Telnet timeout
03 Jun 2017 15:17:56   Timeout while collecting bitloading data
03 Jun 2017 15:17:57   Telnet timeout
03 Jun 2017 15:18:56   Timeout while collecting bitloading data
03 Jun 2017 15:18:57   Unable to collect stats 3 or more times in succession
03 Jun 2017 15:18:57   Telnet timeout
03 Jun 2017 15:20:56   Timeout while collecting bitloading data
03 Jun 2017 15:20:57   Telnet timeout
03 Jun 2017 15:21:57   Timeout while retrieving stats
03 Jun 2017 15:21:57   No stats received
03 Jun 2017 15:23:56   Timeout while collecting SNR per tone
03 Jun 2017 15:23:58   Telnet timeout
03 Jun 2017 15:24:56   Timeout while retrieving stats
03 Jun 2017 15:24:56   No stats received
03 Jun 2017 15:25:56   Timeout while collecting bitloading data
03 Jun 2017 15:25:56   Unable to collect stats 3 or more times in succession
03 Jun 2017 15:25:57   Telnet timeout
03 Jun 2017 15:26:56   Timeout while retrieving stats
03 Jun 2017 15:26:57   No stats received
03 Jun 2017 15:27:56   Timeout while collecting bitloading data
03 Jun 2017 15:27:57   Telnet timeout
03 Jun 2017 15:28:56   Timeout while retrieving stats
03 Jun 2017 15:28:56   No stats received
03 Jun 2017 15:29:56   Timeout while collecting bitloading data
03 Jun 2017 15:29:57   Telnet timeout
03 Jun 2017 15:30:57   Timeout while collecting bitloading data
03 Jun 2017 15:30:58   Telnet timeout
03 Jun 2017 15:31:56   Timeout while collecting bitloading data
03 Jun 2017 15:31:57   Telnet timeout
03 Jun 2017 15:32:56   Timeout while collecting bitloading data
03 Jun 2017 15:32:57   Telnet timeout
03 Jun 2017 16:28:56   Timeout while retrieving stats
03 Jun 2017 16:28:56   No stats received
03 Jun 2017 16:29:57   Timeout while retrieving stats
03 Jun 2017 16:29:57   No stats received
03 Jun 2017 16:30:57   Timeout while collecting bitloading data
03 Jun 2017 16:30:57   Unable to collect stats 3 or more times in succession
03 Jun 2017 16:30:57   Telnet timeout
03 Jun 2017 16:31:56   Timeout while collecting bitloading data
03 Jun 2017 16:31:57   Telnet timeout
03 Jun 2017 16:35:56   Timeout while collecting SNR per tone
03 Jun 2017 16:35:57   Telnet timeout
03 Jun 2017 16:48:45   Implausible down traffic value reported by modem/router
03 Jun 2017 17:36:56   Timeout while collecting bitloading data
03 Jun 2017 17:36:57   Telnet timeout
03 Jun 2017 17:39:56   Timeout while collecting SNR per tone
03 Jun 2017 17:39:57   Telnet timeout
03 Jun 2017 17:46:56   Timeout while retrieving stats
03 Jun 2017 17:46:56   No stats received
03 Jun 2017 17:47:56   Timeout while collecting bitloading data
03 Jun 2017 17:47:57   Telnet timeout
03 Jun 2017 17:48:56   Timeout while collecting bitloading data
03 Jun 2017 17:48:56   Unable to collect stats 3 or more times in succession
03 Jun 2017 17:48:57   Telnet timeout
03 Jun 2017 17:49:57   Timeout while retrieving stats
03 Jun 2017 17:49:57   No stats received
03 Jun 2017 17:50:56   Timeout while collecting bitloading data
03 Jun 2017 17:50:57   Telnet timeout
03 Jun 2017 18:52:44   Implausible down traffic value reported by modem/router
03 Jun 2017 18:54:45   Implausible down traffic value reported by modem/router
03 Jun 2017 19:59:42   Unable to login to modem/router
03 Jun 2017 20:44:47   Implausible down traffic value reported by modem/router
03 Jun 2017 21:09:46   Implausible down traffic value reported by modem/router
03 Jun 2017 21:10:48   Implausible down traffic value reported by modem/router
03 Jun 2017 21:20:46   Implausible down traffic value reported by modem/router
03 Jun 2017 22:24:42   Unable to login to modem/router
04 Jun 2017 00:16:42   Unable to login to modem/router
04 Jun 2017 08:51:43   *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
04 Jun 2017 08:51:43   Second stage login failed
04 Jun 2017 09:29:57   Timeout while collecting bitloading data
04 Jun 2017 09:29:57   Telnet timeout
04 Jun 2017 09:37:56   Timeout while collecting bitloading data
04 Jun 2017 09:37:57   Telnet timeout
04 Jun 2017 11:22:45   Deleted snapshots in folder C:\Users\*********\AppData\Local\dslstats\2017-05-28
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 02:06:08 PM
Quote
Disable WIFI

Disable LAN

Set LAN to DHCP (for IP and DNS)

having taken steps 1 & 2, how do I achieve 3?  cannot get in to the router, Ethernet and wi-fi being disabled. :-\
Title: Re: Today's shock resync
Post by: d2d4j on June 04, 2017, 02:26:37 PM
Hi renluop

Sorry, you are setting the IPv4 option of your pc to dhcp and not your router.

The reason for disabling the Lan on pc and make the change is to break sessions, so it sets correctly hopefully.

So you do all on pc only

Many thanks

John
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 04:34:07 PM
I've had a go at it, hopefully correctly and successfully! Eric advised me to slim down what data I collect, which I will do, and @d2d4j I'll let the network be as you say.

I'm not sure of the pings' reasons, but have attached them. What is the reason for them?

In passing DSL connection was lost just now and came back with slightly lower speed and new IP address in same series 209.93.*.*. hope that was just a lease renewal and nothing else.
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 04:42:13 PM
and now this! *7345']
Quote
04 Jun 2017 16:28:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB

04 Jun 2017 16:28:49   IP address is now 209.93.105.215
04 Jun 2017 16:36:51   DSL connection dropped
04 Jun 2017 16:36:51   No DSL connection
04 Jun 2017 16:38:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 16:38:48   IP address is now 209.93.105.238
Title: Re: Today's shock resync
Post by: d2d4j on June 04, 2017, 04:44:41 PM
Hi renluop

Many thanks

The dsl connection is maintained by your router - you pc should not be able to directly affect the dsl so it will have been a renewal, as you revived a different external ip.

The pings are not really needed, but confirm the time to router and BBC. If wifi, these would be higher

I hope that helps

Many thanks

John
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 06:53:02 PM
But this seems an inordinate number of address changes; more often than I change my pants.
Quote
04 Jun 2017 16:05:51   Recording started

04 Jun 2017 16:05:56   IP address is now 209.93.***.**7

04 Jun 2017 16:28:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB

04 Jun 2017 16:28:49   IP address is now 209.93.***.**5
04 Jun 2017 16:36:51   DSL connection dropped
04 Jun 2017 16:36:51   No DSL connection
04 Jun 2017 16:38:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 16:38:48   IP address is now 209.93.***.*3*
04 Jun 2017 16:56:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 16:56:51   IP address is now 46.208.**.**6
04 Jun 2017 17:28:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 17:29:02   Unable to determine IP address
04 Jun 2017 17:30:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 17:32:45   No DSL connection
04 Jun 2017 17:34:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 17:38:45   DSL connection dropped
04 Jun 2017 17:38:45   No DSL connection
04 Jun 2017 17:40:45   No DSL connection
04 Jun 2017 17:42:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 17:44:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 17:56:45   DSL connection dropped
04 Jun 2017 17:56:45   No DSL connection
04 Jun 2017 17:58:45   No DSL connection
04 Jun 2017 18:00:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 18:02:45   No DSL connection
04 Jun 2017 18:04:45   No DSL connection
04 Jun 2017 18:06:45   Unable to collect stats 3 or more times in succession
04 Jun 2017 18:06:45   No DSL connection
04 Jun 2017 18:08:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 18:08:48   IP address is now 147.***.***.155
04 Jun 2017 18:10:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 18:10:48   IP address is now 147.***.***.215
04 Jun 2017 18:12:46   No DSL connection
04 Jun 2017 18:14:45   No DSL connection
04 Jun 2017 18:16:45   Unable to collect stats 3 or more times in succession
04 Jun 2017 18:16:45   No DSL connection
04 Jun 2017 18:18:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 18:22:45   DSL connection dropped
04 Jun 2017 18:22:45   No DSL connection
04 Jun 2017 18:24:45   No DSL connection
04 Jun 2017 18:26:46   DSL connection restored. SNRMup =  dB, SNRMdown =  dB
04 Jun 2017 18:26:48   IP address is now 147.147.***.1**
and this SNR graph with its rapid rise, fall, sync and u/stream interleave from 4 to 1. can all that be normal behaviour? Be thre gremlins somewhere?

And yet another drop and change of IP!!!!
Title: Re: Today's shock resync
Post by: ejs on June 04, 2017, 07:01:39 PM
Is the SNRM still tweaked?
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 07:15:47 PM
Yes @ 4 dB.Not so long ago it gave no trouble @ 3 dB, and that was for months on end!

is there a chance I am using wrong router ports for router to vomputer, and router to HomePlug? billion  says
LAN 1-4
Quote
Connect a UTP Ethernet cable (Cat-5 or Cat-5e) to one of the four LAN ports when
connecting to a PC or an office/home network of 10Mbps /100Mbps /1000Mbps.
Note: 3-port 10/100Mbps switch (port#2-4), and 1-port Gigabit switch(port #1)
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 07:31:57 PM
Just had an invalid floating point warning. Seems @d2d4j idea was short lived in effectiveness. :rain:
Title: Re: Today's shock resync
Post by: ejs on June 04, 2017, 07:46:19 PM
Yes @ 4 dB.Not so long ago it gave no trouble @ 3 dB, and that was for months on end!

If you're going to go down the standard line and broadband fault troubleshooting and reporting steps, I suggest leaving the SNRM alone.
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 08:03:56 PM
Back to 6 you mean? Ideas what could be causing so many drops, if not too low a target margin? no sign of noise too.
Title: Re: Today's shock resync
Post by: d2d4j on June 04, 2017, 08:27:57 PM
Hi renluop

Please confirm your pc network cable is connected directly to the router (not the power line adapter)

Dslstats and/or your pc are not causing your dropouts/resyncs

If your pc is connected by power line adaptors, you need to fully remove these and have a direct network connection from pc to router, as the power line adaptors could be causing the floating point issue (if connected of course). If it is a direct network connection, it would suggest something within your windows or hardware on pc

Many thanks

John
Title: Re: Today's shock resync
Post by: ejs on June 04, 2017, 08:31:05 PM
Back to 6 you mean?

Yes, I meant remove any tweaking applied.
Title: Re: Today's shock resync
Post by: renluop on June 04, 2017, 09:12:46 PM
Hi renluop

Please confirm your pc network cable is connected directly to the router (not the power line adapter)

Dslstats and/or your pc are not causing your dropouts/resyncs

If your pc is connected by power line adaptors, you need to fully remove these and have a direct network connection from pc to router, as the power line adaptors could be causing the floating point issue (if connected of course). If it is a direct network connection, it would suggest something within your windows or hardware on pc

Many thanks

John

the computer and router have a standard Ethernet cable between them. Another Ethernet cable runs from the router to the powerline adaptor in a nearby wall socket. This through the electric circuit supports IPlayer etc on my Humax Freesat HDR.
Title: Re: Today's shock resync
Post by: renluop on June 05, 2017, 07:26:34 AM
A quick check with AM radio revealed pulsation near answerphone base unit. It was at ~ 1 sec intervals, not loud, more like gentle hand clapping, like metronome.

Of any significance?
Title: Re: Today's shock resync
Post by: tickmike on June 05, 2017, 11:35:52 AM
Just had an invalid floating point warning.
Can someone tell me what this is and from where.
Title: Re: Today's shock resync
Post by: d2d4j on June 05, 2017, 12:48:38 PM
Hi tickmike

It's a mathematical calculation error, usually for rounding or decimal etc

It appears onscreen and not logged in the program which has/had the issue

Dslstats itself does not I believe do any calculations as it's reporting the numbers given to it from the modem (sorry if I'm wrong) but it probably does calculations for the graphs, which is where the floating point error may be happening.

The floating point error is generic term and does not give indication as the where or what caused it. However, it is a mathematical error, ergo has to be caused by calculations

This could be the graphic card, graphing calculations or similar

That said though, if there were a specific bug in dslstats graphing, I would expect it to show on all installation of dslstats where as, if it only appears to happen on 1 or 2 users installations, it is more likely unique to their computer

It could even be that the program needs starting using administrative rights, so it can correctly function due to Windows permissions been different for users/administrators and it's ability to read/write

The above is just a brief outline and others may post more in depth, but a google will bring lots of pages up

The reason for advising a hardwired network is to ensure no interruption to data stream

Many thanks

John
Title: Re: Today's shock resync
Post by: roseway on June 05, 2017, 01:05:34 PM
DSLstats does do a number of floating point calculations in the graphing, but all of these instances are error trapped and shouldn't result in a floating point error message for the user. But it does use a lot of library functions, and it's possible that the FP error originates in one of these. I do have access to all the source code, but there's a lot of it, and chasing down a FP error which I can't reproduce is beyond me. I think that these errors only occur as a result of discontinuities in the data flow between the program and the modem, hence the advice to use a direct (and good quality) connection.
Title: Re: Today's shock resync
Post by: tickmike on June 05, 2017, 02:16:23 PM
@ roseway
@ d2d4j
Thanks I understand a bit better now.  :)
Title: Re: Today's shock resync
Post by: ejs on June 05, 2017, 07:33:20 PM
A quick check with AM radio revealed pulsation near answerphone base unit. It was at ~ 1 sec intervals, not loud, more like gentle hand clapping, like metronome.

Of any significance?

It's impossible to say. You might have heard exactly the same thing on the AM radio in the same place when the broadband was working fine. You could try unplugging the answerphone's phone and power connections, and seeing if it makes any difference to your broadband.
Title: Re: Today's shock resync
Post by: renluop on June 06, 2017, 04:29:45 PM
It's impossible to say. You might have heard exactly the same thing on the AM radio in the same place when the broadband was working fine. You could try unplugging the answerphone's phone and power connections, and seeing if it makes any difference to your broadband.
This time the pulses were faster. I did as suggested, then restarted the router. Resync was insignificantly increased by about 30  kbps.
Title: Re: Today's shock resync
Post by: parkdale on June 06, 2017, 10:12:29 PM
I was thinking about possible floating point errors :-\ we generally use unbuffered memory which does not have the ninth bit check? (I think it's 9 :fingers:)
I wonder if in certain computers this may manifest itself as a calculation error which windows has had some famous examples of in the past.
Below is a link to how floating point errors are dealt with
https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html
This is way out of my comfort zone of understanding :-[
I wondered if the same errors would appear in a fully buffered computer memory, or am I being too 'out there'.
Title: Re: Today's shock resync
Post by: d2d4j on June 06, 2017, 11:18:24 PM
Hi parkdale

That's heavy reading

I think this is no longer an issue, for 2 reasons, firstly, renluop system I thought was dell, and would be accounted for FP, and secondly, it would have been very quickly picked up if the dell had an issue on FP, by the number of users of the dell pc

I do remember the start of FP, and we could set FP at bios level (enable/disable etc), which for many years has not been a bios option (similarly, we could set timings - think it was option between 2086 and 3086 systems)

I could be wrong sorry, as now feeling soo old

Many thanks

John