dauernder IP-Wechsel

[merkur70]

hallo,bei meinem anschluss wechselt täglich,manchmal stündlich meine ip-adresse.
immer von ner 77........ auf 95.......,standort münchen zu herdeke in nrw.
wie kommt das denn?.
gruß merkur

[fLoo]

ModemLog bitte mal Posten, dann sieht man mehr

[amax]

Geschieht jetzt in meiner Region auch (2)....
Nachdem ich fast ein halbes Jahr auf einer Ip fest hing, kam es jetzt auch schon 2-3 mal am Abend vor.
Nicht immer, aber oft genug.
Die Teamspeakverbindung, etc, ist dann natürlich futsch....
Einfach mal im Router auf die Lease-Time schauen, notieren und dann vergleichen.

[merkur70]

hier der modemlog.



Basic


Basic Status

Event Log - DOCSIS

DOCSIS PacketCable

Date/Time Event ID Event Level Description
05/26/2009 00.34 68010300 05 DHCP RENEW WARNING - Field invalid in response
05/18/2009 01.43 68010300 05 DHCP RENEW WARNING - Field invalid in response
05/15/2009 17.04 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
05/15/2009 10.38 84000100 03 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
05/14/2009 13.43 68010300 05 DHCP RENEW WARNING - Field invalid in response
05/14/2009 13.12 2436694044 03 Resetting the cable modem due to docsDevResetNow
05/14/2009 00.12 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
05/14/2009 00.09 69011200 06 SW download Successful - Via Config file
05/14/2009 00.07 69010200 06 SW Download INIT - Via Config file bpr010600189b8c4e020002
05/14/2009 00.06 68000300 03 DHCP WARNING - Non-critical field invalid in response.
05/14/2009 00.06 82000200 03 No Ranging Response received - T3 time-out
05/14/2009 00.06 82000200 03 No Ranging Response received - T3 time-out
05/14/2009 00.06 82000300 03 Init RANGING Critical Ranging Request Retries exhausted
05/14/2009 00.05 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
05/12/2009 10.39 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
05/11/2009 10.24 68010300 05 DHCP RENEW WARNING - Field invalid in response
05/08/2009 11.04 68000300 03 DHCP WARNING - Non-critical field invalid in response.
05/08/2009 11.04 82000200 03 No Ranging Response received - T3 time-out
05/08/2009 11.02 82000200 03 No Ranging Response received - T3 time-out
05/08/2009 11.02 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
05/08/2009 10.58 68000300 03 DHCP WARNING - Non-critical field invalid in response.
05/08/2009 10.57 85000100 03 No UCD's Received - Timeout
05/08/2009 10.52 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
05/07/2009 09.55 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 02.09 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 02.09 68000100 03 DHCP FAILED - Discover sent, no offer received
01/01/1970 02.09 82000200 03 No Ranging Response received - T3 time-out
01/01/1970 00.01 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 00.00 82000200 03 No Ranging Response received - T3 time-out
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 00.00 82000200 03 No Ranging Response received - T3 time-out

[Power-Gamer2004]

Auf die IP-Änderungen hast du kein Einfluß.
In deinem Segment wird halt gerade permanent die IP geändert, warscheinlich wird auch an irgendwas gearbeitet.