Sinds december ben ik overgestapt van Ziggo naar KPN glasvezel. Van 40Mbit upload naar 1000Mbit is een waanzinnige verbetering - superblij mee!
Alleen … onze verbinding klapt er meerdere keren per dag uit. Inmiddels is al 3x een monteur hier aan de deur geweest en natuurlijk werkt het dan weer perfect, ook al blijkt uit een tooltje waarmee ik de internet connectivity meet (elke 60 seconden verbinding leggen met kpn.com) dat er wel degelijk verbrekingen zijn. De laatste monteur beweerde met 200% zekerheid dat het probleem door iets in mijn interne netwerk wordt veroorzaakt. Maar wat dan? En hoe breng je dat in kaart?
Vanmiddag rond 17:00 ben ik weer begonnen met meten via mijn computer en van 18:13 tot 18:21 was er wederom geen verbinding. Op aanraden van de klantenservice ben ik in de logs gedoken van het KPN modem (My modem > Maintenance > logs).
In het eerste niveau (Debug or higher) wordt het volgende gelogd:
| Date/Time | Severity | Module | Message |
|---|---|---|---|
| 09.01.2022 21:03:17 | Info | SYS | Modem login was successful |
| 09.01.2022 20:53:16 | Info | SYS | Modem login was successful |
| 09.01.2022 20:29:01 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=5&duration=2790) |
| 09.01.2022 20:29:01 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=5&duration=2790) |
| 09.01.2022 20:29:01 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=5&duration=2790) |
| 09.01.2022 20:25:42 | Debug | DNS | DNS name resolution failure (https://app-measurement.com/sdk-exp) |
| 09.01.2022 20:25:27 | Debug | DNS | DNS name resolution failure (0.a.c.0.9.b.e.f.f.f.a.c.8.2.a.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0) |
| 09.01.2022 20:25:12 | Debug | DNS | DNS name resolution failure (undefined) |
| 09.01.2022 20:25:12 | Debug | DNS | DNS name resolution failure (undefined) |
| 09.01.2022 20:16:42 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 20:16:42 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 20:16:42 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 20:16:36 | Debug | DNS | DNS name resolution failure (https:) |
| 09.01.2022 20:15:41 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 20:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 19:42:44 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 19:42:44 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 19:42:44 | Debug | DNS | DNS name resolution failure (&eventtype=close&reason=4&duration=12) |
| 09.01.2022 19:42:38 | Debug | DNS | DNS name resolution failure (https:) |
| 09.01.2022 19:24:09 | Debug | DNS | DNS name resolution failure (0.a.c.0.9.b.e.f.f.f.a.c.8.2.a.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0) |
| 09.01.2022 19:15:40 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 19:15:38 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 18:54:19 | Debug | DNS | DNS name resolution failure (https://app-measurement.com/sdk-exp) |
| 09.01.2022 18:44:48 | Debug | DNS | DNS name resolution failure (242.213.245.87.in-addr.arpa) |
| 09.01.2022 18:44:33 | Debug | DNS | DNS name resolution failure (100.98.156.139.in-addr.arpa) |
| 09.01.2022 18:42:02 | Info | SYS | Modem login was successful |
| 09.01.2022 18:30:41 | Debug | DNS | DNS name resolution failure (https://app-measurement.com/sdk-exp) |
| 09.01.2022 18:22:12 | Debug | DNS | DNS name resolution failure (https://app-measurement.com/sdk-exp) |
| 09.01.2022 18:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 18:15:37 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 17:57:16 | Debug | DNS | DNS name resolution failure (https://app-measurement.com/sdk-exp) |
| 09.01.2022 17:55:49 | Info | SYS | Modem login was successful |
| 09.01.2022 17:26:36 | Debug | DNS | DNS name resolution failure (29.71.253.172.in-addr.arpa) |
| 09.01.2022 17:26:28 | Debug | DNS | DNS name resolution failure (225.241.170.108.in-addr.arpa) |
| 09.01.2022 17:26:22 | Debug | DNS | DNS name resolution failure (199.244.85.209.in-addr.arpa) |
| 09.01.2022 17:26:16 | Debug | DNS | DNS name resolution failure (123.250.85.209.in-addr.arpa) |
| 09.01.2022 17:26:12 | Debug | DNS | DNS name resolution failure (253.66.253.172.in-addr.arpa) |
| 09.01.2022 17:26:06 | Debug | DNS | DNS name resolution failure (193.241.170.108.in-addr.arpa) |
| 09.01.2022 17:26:00 | Debug | DNS | DNS name resolution failure (91.211.250.142.in-addr.arpa) |
| 09.01.2022 17:25:56 | Debug | DNS | DNS name resolution failure (197.242.85.209.in-addr.arpa) |
| 09.01.2022 17:24:52 | Debug | DNS | DNS name resolution failure (0.a.c.0.9.b.e.f.f.f.a.c.8.2.a.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0) |
| 09.01.2022 17:23:02 | Debug | DNS | DNS name resolution failure (_bookmarkdavs._tcp.p49-bookmarks.icloud.com) |
| 09.01.2022 17:16:52 | Debug | DNS | DNS name resolution failure (171.238.250.142.in-addr.arpa) |
| 09.01.2022 17:16:39 | Debug | DNS | DNS name resolution failure (127.70.251.142.in-addr.arpa) |
| 09.01.2022 17:16:34 | Debug | DNS | DNS name resolution failure (161.241.170.108.in-addr.arpa) |
| 09.01.2022 17:16:29 | Debug | DNS | DNS name resolution failure (211.54.251.142.in-addr.arpa) |
| 09.01.2022 17:16:23 | Debug | DNS | DNS name resolution failure (181.48.251.142.in-addr.arpa) |
| 09.01.2022 17:16:19 | Debug | DNS | DNS name resolution failure (129.70.251.142.in-addr.arpa) |
| 09.01.2022 17:16:13 | Debug | DNS | DNS name resolution failure (179.48.251.142.in-addr.arpa) |
| 09.01.2022 17:16:09 | Debug | DNS | DNS name resolution failure (129.241.170.108.in-addr.arpa) |
| 09.01.2022 17:16:09 | Debug | DNS | DNS name resolution failure (static.kpn.net) |
| 09.01.2022 17:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 17:15:36 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 17:06:33 | Info | SYS | Modem login was successful |
In het niveau daaronder (Info or higher) krijg ik de volgende logs:
| Date/Time | Severity | Module | Message |
|---|---|---|---|
| 09.01.2022 20:53:16 | Info | SYS | Modem login was successful |
| 09.01.2022 20:15:41 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 20:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 19:15:40 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 19:15:38 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 18:42:02 | Info | SYS | Modem login was successful |
| 09.01.2022 18:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 18:15:37 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 17:55:49 | Info | SYS | Modem login was successful |
| 09.01.2022 17:15:39 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been closed |
| 09.01.2022 17:15:36 | Info | SYS | TR-069 connectivity to (hengelo0.cust.kpn.net) has been initiated |
| 09.01.2022 17:06:33 | Info | SYS | Modem login was successful |
In alle andere niveaus daaronder zitten alleen logs van 2013, dus lijkt mij niet relevant.
Weet iemand hier hoe ik deze logs moet interpreteren en wat er eventueel aan te doen is om dit probleem op te lossen?
Beste antwoord door BrandedChannels
Bekijk origineel
