Internet bricht min. 1x täglich ab, was tun?

[stephan902]

Hallo,

mein Internet bricht immer wieder während längeren Online-Sessions einfach zusammen und ist erst ein paar Sekunden später wieder da.
Der Router gibt folgenden Error-Log wieder:
Apr 10 22:44:24 info daemon dnsmasq-dhcp[2154]: DHCPACK(br-lan) xxx.168.x.19 e0:cb:4e:c7:ad:ea Stesatec-PC
Apr 10 22:44:24 info daemon dnsmasq-dhcp[2154]: DHCPINFORM(br-lan) xxx.168.x.19 e0:cb:4e:c7:ad:ea
Apr 10 22:36:36 notice user root: [DDNS]DDNS response: good xxx.251.xxx.23
Apr 10 22:36:35 notice user root: [DDNS]DDNS update: current system ip = xxx.251.xxx.23
Apr 10 22:36:34 notice user root: udp-broadcast-relay not start: can't find interface ...
Apr 10 22:36:28 debug local4 pppd[29156]: Script /etc/ppp/ip-up finished (pid 29188), status = 0x0
Apr 10 22:36:28 notice user root: starting ntpclient
Apr 10 22:36:19 notice local4 root: [WAN Check]wan just up ......skip check_pppwan
Apr 10 22:36:12 err local7 syslog: Required parameters missing, make sure that username and password are given
Apr 10 22:36:10 err daemon ipsec_setup: doing cleanup anyway...
Apr 10 22:36:10 err daemon ipsec_setup: stop ordered, but IPsec appear to be stopped already!
Apr 10 22:36:10 err daemon ipsec_setup: Stopping Openswan IPsec...
Apr 10 22:36:10 err daemon ipsec_setup: ...Openswan IPsec stopped
Apr 10 22:36:01 notice user miniupnpd: adding firewall rules for ppp0 to zone wan
Apr 10 22:36:00 notice user miniupnpd: removing firewall rules for ppp0 from zone wan
Apr 10 22:35:53 notice user root: adding ppp0 to firewall zone wan
Apr 10 22:35:53 notice local4 root: [addif] interface wan: ppp0 exist.
Apr 10 22:35:50 notice user root: udp-broadcast-relay not start: can't find interface ...
Apr 10 22:35:47 notice user firewall: Restart user's custom iptables rules
Apr 10 22:35:45 notice local4 root: [IP-UP] IFACE=ppp0 TTY=eth1.7 SPEED=0 LOCAL=xxx.251.xxx.23 REMOTE=xx.186.xxx.46 IPPARAM=wan
Apr 10 22:35:44 debug local4 pppd[29156]: Script /etc/ppp/ip-up started (pid 29188)
Apr 10 22:35:44 notice local4 pppd[29156]: secondary DNS address xxx.0.xx.177
Apr 10 22:35:44 notice local4 pppd[29156]: primary DNS address xxx.0.xx.161
Apr 10 22:35:44 notice local4 pppd[29156]: remote IP address xx.186.xxx46
Apr 10 22:35:44 notice local4 pppd[29156]: local IP address xxx.251.xxx.23
Apr 10 22:35:44 info daemon dnsmasq[2154]: using local addresses only for domain lan
Apr 10 22:35:44 info daemon dnsmasq[2154]: using nameserver xxx.0.xx.161#53
Apr 10 22:35:44 info daemon dnsmasq[2154]: using nameserver xxx.0.xx.177#53
Apr 10 22:35:44 info daemon dnsmasq[2154]: reading /tmp/resolv.conf.auto
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [IPCP ConfAck id=0x2 <addr xxx.251.xxx.23> <ms-dns1 xxx.0.xx.161> <ms-dns3 xxx.0.xx.177>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [IPCP ConfReq id=0x2 <addrxxx.251.xxx.23> <ms-dns1 xxx.0.xx.161> <ms-dns3 xxx.0.xx.177>]
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [IPCP ConfNak id=0x1 <addr xxx.251.xxx.23> <ms-dns1 xxx.0.xx.161> <ms-dns3 xxx.0.xx.177>]
Apr 10 22:35:44 debug local4 pppd[29156]: Protocol-Reject for 'IPv6 Control Protovol' (0x8057) received
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [LCP ProtRej id=0x58 80 57 01 01 00 0e 01 0a 78 cc 52 de 70 a3 d8 d7]
Apr 10 22:35:44 debug local4 pppd[29156]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [LCP ProtRej id=0x57 80 fd 01 01 00 0a 12 06 00 00 00 01]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [IPCP ConfAck id=0xb <addr xx.186.xxx.46>]
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [IPCP ConfReq id=0xb <addr xx.186.xxx.46>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [IPV6CP ConfReq id=0x1 <addr fe80::78cc:52de:70a3:d8d7>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [CCP ConfReq id=0x1 <mppe -H -M -S -L -D +C>]
Apr 10 22:35:44 notice local4 pppd[29156]: peer from calling number 00:30:88:1F:23:55 authorized
Apr 10 22:35:44 notice local4 pppd[29156]: PAP authentication succeeded
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [PAP AuthAck id=0x1 ""]
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [LCP EchoRep id=0x0 magic=0x141382b8]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [PAP AuthReq id=0x1 user="xxxxxx@t-online.de" password=<hidden>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [LCP EchoReq id=0x0 magic=0xf85202f5]
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0xf85202f5>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [LCP ConfAck id=0x56 <mru 1492> <auth pap> <magic 0x141382b8>]
Apr 10 22:35:44 debug local4 pppd[29156]: rcvd [LCP ConfReq id=0x56 <mru 1492> <auth pap> <magic 0x141382b8>]
Apr 10 22:35:44 debug local4 pppd[29156]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf85202f5>]
Apr 10 22:35:44 notice local4 pppd[29156]: Connect: ppp0 <--> eth1.7
Apr 10 22:35:44 info local4 pppd[29156]: Using interface ppp0
Apr 10 22:35:44 warn user kernel: register netdev : ppp0^M
Apr 10 22:35:44 debug local4 pppd[29156]: using channel 58
Apr 10 22:35:44 warn local4 pppd[29156]: hnat_patch_fn /tmp/pppoe.info/eth1.7
Apr 10 22:35:44 info local4 pppd[29156]: PPP session is 9789
Apr 10 22:35:44 debug local4 pppd[29156]: PADS: Service-Name: 'T-Online'
Apr 10 22:35:43 err local4 pppd[29156]: Interface eth1.7 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Apr 10 22:35:43 notice local4 pppd[29156]: pppd 2.4.4 started by root, uid 0
Apr 10 22:35:43 info local4 pppd[29153]: Plugin rp-pppoe.so loaded.
Apr 10 22:35:42 info local4 pppd[14747]: Exit.
Apr 10 22:35:42 notice local4 pppd[14747]: Remove pidfiles /var/run/ppp0.pid /var/run/ppp-wan.pid
Apr 10 22:35:42 info local4 pppd[14747]: Terminating on signal 15
Apr 10 22:35:41 notice local4 root: ========== ifdown wan
Apr 10 22:35:41 notice local4 root: ********** ifup wan
Apr 10 22:35:41 notice local4 root: [WAN Check] check default route failed0), revert WAN state and ifup wan...
Apr 10 22:35:21 notice user root: udp-broadcast-relay not start: can't find interface ...
Apr 10 22:35:16 notice local4 root: [WAN] ***************no default route, add default interface ppp0
Apr 10 22:35:16 debug local4 pppd[14747]: Script /etc/ppp/ip-down finished (pid 28065), status = 0x1
Apr 10 22:35:16 notice local4 pppd[14747]: Modem hangup
Apr 10 22:35:16 notice local4 pppd[14747]: Connection terminated.
Apr 10 22:35:15 notice user root: stopping ntpclient
Apr 10 22:35:13 notice local4 root: [IP-DOWN]revert uci network state in ip-down...
Apr 10 22:35:13 notice local4 root: [IP-DOWN] IFACE=ppp0 TTY=eth1.7 SPEED=0 LOCAL=xx.203.xxx.91 REMOTE=xx.186.xxx.46 IPPARAM=wan
Apr 10 22:35:13 debug local4 pppd[14747]: sent [LCP TermAck id=0xec]
Apr 10 22:35:13 debug local4 pppd[14747]: Script /etc/ppp/ip-down started (pid 28065)
Apr 10 22:35:13 info local4 pppd[14747]: Sent 37773973 bytes, received 174338856 bytes.
Apr 10 22:35:13 info local4 pppd[14747]: Connect time 1440.1 minutes.
Apr 10 22:35:13 info local4 pppd[14747]: LCP terminated by peer
Apr 10 22:35:13 debug local4 pppd[14747]: rcvd [LCP TermReq id=0xec]

 

[Sebbi]

LCP terminated by peer <<< Störung bei deinen Anbieter .... Störung melden wenn das immer wieder auftritt

 

[WingX]

Schonmal was von 24h-Zwangstrennung gehört? So ziemlich jeder DSL-By-Call-Anbieter zieht dir die Verbindung nach 24h weg. Bei dir tritt das halt zu einer ungünstigen Zeit auf. Versuch mal am Wochenende deinen Router mittags neu zu starten. Damit kannst du den Zeitpunkt evtl. auf mittags verschieben, wenns dich nicht stört.

 

[Sebbi]

ah jetzt wo WingX das sagt, fällt mir auch das connect zeit ins auge ... ja das is der 24h zwangstrennung

 

[Asghan]

oder stell im Router feste ein, dass er zB immer morgens um 5 rebooten soll, dann hast tagsüber Ruhe.

 

[stephan902]

oder stell im Router feste ein, dass er zB immer morgens um 5 rebooten soll, dann hast tagsüber Ruhe.

Das wäre gut, aber ich glaub das kann ich nicht einstellen.

Danke. Hab ich mir fast schon gedacht, zumal 1440 Minuten = 24 h.

 

[phreeze]

am Wochenende den Wecker setzen, 5 uhr in der Nacht den Stecker ziehen, und wieder rein, wieder ins Bett Problem gelöst