[atlas] Availability report accuracy

On 2016/01/02 18:57 , Gerhard Joch wrote:
> I want to jump into this topic too, but before a Happy New Year to
> everybody.
> 
> Was wondering too, for December my probe got an total availability of
> only 98.17% - and which is in fact not true. I'm on a VDSL line 50 mbit
> from German Telekom, and every night my router has to re-establish the
> connection to get a new public IP. According to the log files from my
> router this whole process takes only a couple of seconds, but in the
> Monthly probe report from atlas the time between Disconnected and new
> Connected is around 20 to 30 minutes, see examples below:
> 
> +---------------------+---------------------+------------+--------------+
> | Connected (UTC)     | Disconnected (UTC)  | Connected  | Disconnected |
> |---------------------+---------------------+------------+--------------+
> | 2015-12-26 02:35:51 | 2015-12-27 02:06:06 |   0d 23:30 |     0d 00:27 |
> | 2015-12-27 02:31:20 | 2015-12-28 02:04:36 |   0d 23:33 |     0d 00:25 |
> | 2015-12-28 02:39:09 | 2015-12-29 02:04:29 |   0d 23:25 |     0d 00:34 |
> | 2015-12-29 02:31:40 | 2015-12-30 02:03:09 |   0d 23:31 |     0d 00:27 |

Hi,

I'm not completely sure, but I think the problem is that the probe is
waiting for a TCP connection timeout.

I guess that for some reason the probe doesn't get a TCP RST. Might be a
firewall problem somewhere.

Philip