beantwoord

Internet valt elke nacht uit

  • 3 januari 2015
  • 68 reacties
  • 8230 keer bekeken


Toon het eerste bericht

68 reacties

Reputatie 1
Matthijs, wat vervelend om zo bij ons binnen te moeten komen. Ik kan me voorstellen dat je niet tevreden bent over de afhandeling die je meldt. Je reageert echter op een topic die niet per definitie betrekking heeft op het probleem waar jij nu tegenaan loopt. Ik wil graag kijken naar de reden waarom het bij jou niet (goed) werkt. Zou je jouw naw-gegevens in een privévenster kenbaar kunnen maken alsjeblieft? Ik kom er dan zo snel mogelijk op terug. Ondertussen, vanzelfsprekend, mijn oprechte excuses voor de bijzondere situatie waar je in bent beland.
Dag Michael,

Dank voor je reactie. Het is inderdaad een zeer vervelende situatie. Zoals het er nu uitziet ben ik van een werkende Vodafone "alles in een" oplossing gemigreerd naar een "van alles geen" oplossing. Gelukkig komt er morgen iemand van jullie om de lijn door te meten. (En natuurlijk moet ik er weer een halve dag vrij voor nemen...) Ik snap dat het techniek is, en je kunt altijd voor verassingen komen te staan. Daar heb ik dagelijks in mijn werk mee te maken, dus daarvoor alle begrip. Echter: Als er een link lampje brand op het moment dat de glasvezel wordt geplaatst in het kastje (en je komt van een werkende situatie) kun je er gevoegelijk van uit gaan dat er niets mis is met de glasvezel toch? Het lijkt er dan ook alles op dat er aan de wijkcentrale - zijde een onjuiste vlan- tagging is gemaakt, of dat er een onjuiste patch heeft plaatsgevonden. In ieder geval ben ik blij dat er morgen iemand komt om het op te lossen. Ik hou je op de hoogte door een vervolg te melden op dit forum.

Met vriendelijke groet,
Matthijs.
Reputatie 1
In ieder geval ben ik blij dat er morgen iemand komt om het op te lossen. Ik hou je op de hoogte door een vervolg te melden op dit forum.
Zoals afgesproken: Vandaag is de Telfort monteur geweest en er bleek zoals verwacht een foutje in de wijkcentrale te zijn ontstaan bij de migratie. Monteur was met 2 minuten klaar en het werkt nu.

Groet,
Matthijs
Vandaag is de Telfort monteur geweest en er bleek zoals verwacht een foutje in de wijkcentrale te zijn ontstaan bij de migratie. Monteur was met 2 minuten klaar en het werkt nu.
Was nou die fysieke tussenkomst van die monteur echt noodzakelijk of had dit probleem ook op afstand verholpen kunnen worden?
Heb je daar helderheid over?
Reputatie 1
Was nou die fysieke tussenkomst van die monteur echt noodzakelijk of had dit probleem ook op afstand verholpen kunnen worden?
Heb je daar helderheid over?

Nou, bij ons binnen heeft hij niet veel bijzonders gedaan. Alleen een signaal op de vezel gezet om er zeker van te zijn dat hij in de wijkcentrale het juiste vezeltje te pakken heeft. Als de administratie op orde is was een huisbezoek zeker niet nodig geweest.
Als de administratie niet netjes is bijgehouden en het dus op uitzoeken aan gaat komen wel...
Reputatie 8
Badge +2
Hoi Matthijs! Het komt weleens voor dat er iets niet helemaal goed na een omzetting inderdaad, hier valt niet veel aan te doen. Erg fijn om te lezen dat het na wat geduld en aanpassingen alsnog goed werkt nu. Is er nog iets anders dat ik voor jou kan doen? Ik kijk uit naar je reactie.
Hi Micheal, helaas kamp ook ik met hetzelfde probleem. En wel om de 10 seconden ongeveer. Hierdoor ervaart iedereen bij mij thuis een ontzettend onstabiele internet verbinding.

Zit thuis met een xperiabox V8!

Wat heb ik tot nu toe geprobeerd:
1. Complete reset modem
2. Vervangen val alle modem kabels
3. Vervangen van modem met een test modem, zelfde probleem

Zie hierbij ook mijn logs:

Wat te doen, wat te doen!

01/19/2016 19:53:56 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:55 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:53:52 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:49 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:46 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:43 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:42 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:53:39 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:36 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:33 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:30 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:29 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:53:26 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:23 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:20 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:17 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:16 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:53:13 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:10 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:07 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:04 DHCP Client: [ATM3]Send Discover
01/19/2016 19:53:03 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:53:00 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:57 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:54 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:51 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:50 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:52:47 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:44 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:41 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:38 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:37 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:52:34 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:31 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:28 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:25 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:24 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:52:21 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:18 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:15 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:12 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:11 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:52:08 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:05 DHCP Client: [ATM3]Send Discover
01/19/2016 19:52:02 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:59 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:58 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:51:55 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:52 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:49 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:46 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:45 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:51:42 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:39 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:36 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:33 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:32 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:51:29 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:26 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:23 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:20 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:19 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:51:16 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:13 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:10 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:07 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:06 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:51:03 DHCP Client: [ATM3]Send Discover
01/19/2016 19:51:00 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:57 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:54 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:53 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:50:50 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:47 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:44 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:41 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:40 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:50:37 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:34 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:31 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:28 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:27 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:50:24 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:21 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:18 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:15 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:14 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:50:11 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:08 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:05 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:02 DHCP Client: [ATM3]Send Discover
01/19/2016 19:50:01 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:49:58 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:55 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:52 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:49 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:48 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:49:45 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:42 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:39 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:36 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:35 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/19/2016 19:49:32 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:29 DHCP Client: [ATM3]Send Discover
01/19/2016 19:49:26 DHCP Client: [ATM3]Send Discover
Reputatie 8
Badge +2
Hi Quint! Welkom op het forum. De meldingen in de webinterface van het modem zorgen niet voor een instabiele verbinding. Deze meldingen komen alleen voort uit het feit dat het verzoek om een nieuw IP-adres niet wordt gevonden door onze DHCP-server. Indien dit verzoek eens per uur slaagt, is er geen probleem. Er moet dus een andere reden zijn voor deze instabiliteit. Ervaar je dit tijdens gebruik van WiFi of bekabeld internet? Verneem je reactie graag.
Zelfde hier (Groningen)

Wat ik in me pfsense router/firewall zie is dit

Source (Modem) 192.168.2.254 (?) Destination 224.0.0.1

gaat ongeveer op de zelfde frequentie als in de modem

01/29/2016 19:13:07 DHCP Client: [ATM3]Send Discover
01/29/2016 19:13:04 DHCP Client: [ATM3]Send Discover
01/29/2016 19:13:01 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:58 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:57 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:12:54 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:51 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:48 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:45 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:44 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:12:41 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:38 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:35 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:32 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:31 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:12:28 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:25 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:22 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:19 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:18 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:12:15 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:12 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:09 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:06 DHCP Client: [ATM3]Send Discover
01/29/2016 19:12:05 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:12:02 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:59 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:56 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:53 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:52 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:11:49 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:47 sending ACK to 192.168.2.1
01/29/2016 19:11:46 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:42 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:39 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:38 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:11:35 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:32 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:29 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:26 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:25 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:11:22 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:19 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:16 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:13 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:12 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:11:09 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:06 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:03 DHCP Client: [ATM3]Send Discover
01/29/2016 19:11:00 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:59 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:10:56 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:53 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:50 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:47 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:46 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:10:43 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:40 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:37 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:34 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:33 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:10:30 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:27 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:24 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:21 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:20 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:10:17 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:14 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:11 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:08 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:07 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:10:04 DHCP Client: [ATM3]Send Discover
01/29/2016 19:10:01 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:58 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:55 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:54 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:09:51 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:48 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:45 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:42 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:41 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:09:38 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:35 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:32 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:29 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:28 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:09:25 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:22 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:19 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:16 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:15 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:09:12 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:09 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:06 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:03 DHCP Client: [ATM3]Send Discover
01/29/2016 19:09:02 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:08:59 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:56 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:53 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:50 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:49 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:08:46 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:43 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:40 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:37 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:36 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:08:33 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:30 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:27 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:24 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:23 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:08:20 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:17 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:14 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:11 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:10 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:08:07 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:04 DHCP Client: [ATM3]Send Discover
01/29/2016 19:08:01 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:58 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:57 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:07:54 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:51 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:48 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:45 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:44 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:07:41 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:38 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:35 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:32 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:31 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:07:28 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:25 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:22 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:19 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:18 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:07:15 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:12 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:09 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:06 DHCP Client: [ATM3]Send Discover
01/29/2016 19:07:05 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:07:02 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:59 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:56 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:53 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:52 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:06:49 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:46 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:43 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:40 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:39 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:06:36 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:33 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:30 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:27 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:26 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:06:23 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:20 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:17 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:14 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:13 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:06:10 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:07 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:04 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:01 DHCP Client: [ATM3]Send Discover
01/29/2016 19:06:00 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:05:57 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:54 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:51 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:48 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:47 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:05:44 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:41 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:38 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:35 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:34 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:05:31 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:28 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:25 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:22 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:21 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:05:18 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:15 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:12 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:09 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:08 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:05:05 DHCP Client: [ATM3]Send Discover
01/29/2016 19:05:02 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:59 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:56 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:55 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:04:52 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:49 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:46 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:43 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:42 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:04:39 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:36 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:33 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:30 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:29 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:04:26 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:23 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:20 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:17 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:16 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:04:13 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:10 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:07 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:04 DHCP Client: [ATM3]Send Discover
01/29/2016 19:04:03 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:04:00 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:57 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:54 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:51 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:50 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:03:48 TR069:Session end.
01/29/2016 19:03:48 TR069:Sending GetParameterValues error response
01/29/2016 19:03:48 TR069:Received GetParameterValues
01/29/2016 19:03:48 TR069:Received InformResponse
01/29/2016 19:03:47 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:46 TR069:Sending 6 CONNECTION REQUEST inform.
01/29/2016 19:03:44 TR069:Session end.
01/29/2016 19:03:44 TR069:Received InformResponse
01/29/2016 19:03:44 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:43 TR069:Sending 6 CONNECTION REQUEST inform.
01/29/2016 19:03:43 TR069:Session end.
01/29/2016 19:03:43 TR069:Received InformResponse
01/29/2016 19:03:42 TR069:Sending 1 BOOT inform.
01/29/2016 19:03:41 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:38 DHCP Client: [ATM3]Send Discover
01/29/2016 19:03:37 DHCP Client: [ATM3]Could not find DHCP daemon to get information
01/29/2016 19:03:36 NTP Date/Time updated.
07/31/2015 00:02:30 Get system time from NTP server:00.00.00.00
07/31/2015 00:02:28 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:25 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:22 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:19 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:18 DHCP Client: [ATM3]Could not find DHCP daemon to get information
07/31/2015 00:02:15 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:12 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:09 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:06 DHCP Client: [ATM3]Send Discover
07/31/2015 00:02:05 DHCP Client: [ATM3]Could not find DHCP daemon to get information
07/31/2015 00:02:02 DHCP Client: [ATM3]Send Discover
07/31/2015 00:01:59 DHCP Client: [ATM3]Send Discover
07/31/2015 00:01:56 DHCP Client: [ATM3]Send Discover
07/31/2015 00:01:53 DHCP Client: [ATM3]Send Discover
07/31/2015 00:01:53 DHCP Client: [ATM1]Receive Ack from 00.00.00.00,Lease time=7200
07/31/2015 00:01:53 DHCP Client: [ATM1]Send Request, Request IP=00.00.00.00
07/31/2015 00:01:53 DHCP Client: [ATM1]Receive Offer from 00.00.00.00
07/31/2015 00:01:53 DHCP Client: [ATM1]Send Discover
07/31/2015 00:01:52 DSL Media Up !
07/31/2015 00:01:32 192.168.2.250 Admin login success
07/31/2015 00:00:11 sending ACK to 192.168.2.1
07/31/2015 00:00:06 sending ACK to 192.168.2.2
07/31/2015 00:00:06 sending OFFER to 192.168.2.2
@S.Krans

Zoals uit het log blijkt heeft je modem ook 'n keer succes na al dat geroep om 'information' .
Zolang het antwoord maar 1 keer per 2 uur de honger naar gegevens stilt is er niks aan de hand. (Lease time=7200sec)
oke maar dan de vraag waarom vraagt de dhcp om de 2a3 seconden voor een Send Discover het belast alleen de modem/router met onnodige traffic en rekenkracht

Ps hij vraag nog steeds om 01/30/2016 17:40:06 DHCP Client: [ATM3]Send Discover
oke maar dan de vraag waarom vraagt de dhcp om de 2a3 seconden voor een Send Discover het belast alleen de modem/router met onnodige traffic en rekenkracht

Ps hij vraag nog steeds om 01/30/2016 17:40:06 DHCP Client: [ATM3]Send Discover


Bij mij vraagt ie ook om de paar minuten om info en dat moet ook want mijn leasetime is maar 600sec
Geen idee waarom daar zo'n verschil in zit eigenlijk. Ik merk er iig niks van en die paar bits die worden verstuurt en ontvangen belasten de verbinding miz totaal niet.
Zorgen zou ik me er niet om maken maar technisch gezien is 't wel interessant.
Helaas, ik heb hetzelfde probleem. Soms elke dag, soms over paar dagen moet ik de modem resetten. Is er eigenlijk een oplossing gevonden?
Zelfde hier, om de haverklap; 12/08/2016 21:06:31 DHCP Client: [ATM3]Could not find DHCP daemon to get information, ik vermoed dat het komt omdat ik geen automatische incasso accepteer? Ik ben een maand afgesloten door telfort, onterecht alles was betaalt maar zelf durven ze niks toe te geven maar ik ben wel terugbetaalt raar he, ik vermoed dat dit meespeelt in deze storing... Wie zal ut zeggen maar het valt op daarvoor nooit geen problemen gehad.

Reageer