Nach den ersten stabilen Stunden, kamen in der Nacht zwei kurze dazu und dan nochmal heute im späten Nachmittag drei bis es dann um 20 Uhr kpl. ausgefallen ist. Ein Restart des Modems hat leider nicht geholfen. Die Verbindung lässt sich nicht mehr aufbauen, ähnlich als ich die UDMP am falschen Port angeschlossen hatte. Mein Log:
Dec 19 18:11:21 UDMPro user.info ubios-udapi-server: wan-failover-monitor-icmp: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) wf-monitor (#2) has dpinger update: 1.1.1.1/ping.ubnt.com is down {"alarm":true,"id":"ppp0-mon2-1.1.1.1-ping.ubnt.com","latencyAverage":12634.0,"latencyStdDev":7186.0,"lossPercentage":52.63159942626953}
Dec 19 18:11:21 UDMPro user.info ubios-udapi-server: wan-failover-monitor-icmp: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) wf-monitor (#2) has dpinger update: 8.8.8.8/ping.ubnt.com is down {"alarm":true,"id":"ppp0-mon2-8.8.8.8-ping.ubnt.com","latencyAverage":26380.0,"latencyStdDev":5237.0,"lossPercentage":52.63159942626953}
Dec 19 18:11:22 UDMPro user.info ubios-udapi-server: wan-failover-groups: WAN Failover Groups is using ppp0 (table 201), eth9 is down (no ip)[ddddd], ppp0 is down [_d___]
Dec 19 18:11:29 UDMPro daemon.info pppd[8506]: No response to 3 echo-requests
Dec 19 18:11:29 UDMPro daemon.notice pppd[8506]: Serial link appears to be disconnected.
Dec 19 18:11:29 UDMPro daemon.info pppd[8506]: Connect time 120.1 minutes.
Dec 19 18:11:29 UDMPro daemon.info pppd[8506]: Sent 474466439 bytes, received 1401685914 bytes.
Dec 19 18:11:29 UDMPro user.warn ubios-udapi-server: res-interfaces: Cannot delete PPPoE route: Failed to delete route 0.0.0.0/0 dev ppp0: Object not found
Dec 19 18:11:29 UDMPro user.warn ubios-udapi-server: res-interfaces: Cannot delete PPPoE route: Failed to delete route ::/0 dev ppp0: Object not found
Dec 19 18:11:35 UDMPro daemon.notice pppd[8506]: Connection terminated.
Dec 19 18:11:35 UDMPro daemon.info pppd[8506]: Sent PADT
Dec 19 18:11:35 UDMPro daemon.notice pppd[8506]: Modem hangup
Dec 19 18:11:40 UDMPro daemon.info pppd[8506]: PPP session is 36444
Dec 19 18:11:40 UDMPro daemon.warn pppd[8506]: Connected to xx:xx:xx:xx:xx:xx via interface eth8
Dec 19 18:11:40 UDMPro daemon.info pppd[8506]: Using interface ppp0
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: Connect: ppp0 <--> eth8
Dec 19 18:11:40 UDMPro daemon.info pppd[8506]: CHAP authentication succeeded
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: CHAP authentication succeeded
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: peer from calling number xx:xx:xx:xx:xx:xx authorized
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: local IP address xxx.xxx.xxx.xxx
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: remote IP address xxx.xxx.xxx.xxx
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: primary DNS address xxx.xxx.xxx.xxx
Dec 19 18:11:40 UDMPro daemon.notice pppd[8506]: secondary DNS address xxx.xxx.xxx.xxx
Dec 19 18:11:40 UDMPro user.info ubios-udapi-server: wan-failover-monitors: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) could not resolve ping.ubnt.com (a): Unsupported address family
Dec 19 18:11:40 UDMPro user.info ubios-udapi-server: wan-failover-monitors: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) could not resolve facebook.com (a): Unsupported address family
Dec 19 18:11:40 UDMPro user.info ubios-udapi-server: wan-failover-monitors: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) could not resolve google.com (a): Unsupported address family
Dec 19 18:11:40 UDMPro user.info ubios-udapi-server: wan-failover-monitors: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) could not resolve twitter.com (a): Unsupported address family
Dec 19 18:11:44 UDMPro user.info ubios-udapi-server: wan-failover-monitor-icmp: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) wf-monitor (#2) has dpinger update: 1.1.1.1/ping.ubnt.com is up {"alarm":false,"id":"ppp0-mon2-1.1.1.1-ping.ubnt.com","latencyAverage":1247.0,"latencyStdDev":5438.0,"lossPercentage":0.0}
Dec 19 18:11:44 UDMPro user.info ubios-udapi-server: wan-failover-monitor-icmp: WAN Failover Monitors (ppp0/xxx.xxx.xxx.xxx) wf-monitor (#2) has dpinger update: 8.8.8.8/ping.ubnt.com is up {"alarm":false,"id":"ppp0-mon2-8.8.8.8-ping.ubnt.com","latencyAverage":1734.0,"latencyStdDev":7561.0,"lossPercentage":0.0}
Dec 19 18:11:45 UDMPro user.info ubios-udapi-server: wan-failover-groups: WAN Failover Groups is using ppp0 (table 201), eth9 is down (no ip)[ddddd], ppp0 is up [_u___]
Dec 19 18:11:57 UDMPro daemon.info mcad: mcad[2144]: ace_reporter.geo_info_send(): Sending geo-info request from ppp0
Dec 19 18:11:57 UDMPro daemon.info mcad: mcad[2144]: ace_reporter_udapi_interface.udapi_geo_info_update_per_wan(): Received valid geo-info response from ppp0
Dec 19 20:02:23 UDMPro daemon.info pppd[8506]: No response to 3 echo-requests
Dec 19 20:02:23 UDMPro daemon.notice pppd[8506]: Serial link appears to be disconnected.
Dec 19 20:02:23 UDMPro daemon.info pppd[8506]: Connect time 110.8 minutes.
Dec 19 20:02:23 UDMPro daemon.info pppd[8506]: Sent 79764914 bytes, received 1995844872 bytes.
Dec 19 20:02:23 UDMPro user.warn ubios-udapi-server: res-interfaces: Cannot delete PPPoE route: Failed to delete route 0.0.0.0/0 dev ppp0: Object not found
Dec 19 20:02:23 UDMPro user.warn ubios-udapi-server: res-interfaces: Cannot delete PPPoE route: Failed to delete route ::/0 dev ppp0: Object not found
Dec 19 20:02:23 UDMPro user.info ubios-udapi-server: wan-failover-groups: WAN Failover Groups is using ppp0 (table 201), eth9 is down (no ip)[ddddd], ppp0 is down (no ip)[ddddd]
Dec 19 20:02:29 UDMPro daemon.notice pppd[8506]: Connection terminated.
Dec 19 20:02:29 UDMPro daemon.info pppd[8506]: Sent PADT
Dec 19 20:02:29 UDMPro daemon.notice pppd[8506]: Modem hangup
Dec 19 20:03:09 UDMPro daemon.warn pppd[8506]: Timeout waiting for PADO packets
Dec 19 20:03:09 UDMPro daemon.err pppd[8506]: Unable to complete PPPoE Discovery
Dec 19 20:03:49 UDMPro daemon.warn pppd[8506]: Timeout waiting for PADO packets
Dec 19 20:03:49 UDMPro daemon.err pppd[8506]: Unable to complete PPPoE Discovery
Dec 19 20:04:29 UDMPro daemon.warn pppd[8506]: Timeout waiting for PADO packets
Alles anzeigen
Die FritzBox innerhalb des UDMP Netzes hat diese temporären Ausfälle nicht wirklich gut vertragen. Die integrierte Telefonanlage war im Anschluss nicht mehr erreichbar, es hat nur ein Neustart der FritzBox geholfen. Ultra nervig.
DSL Status im Vigor:
War weiterhin verbunden, kann jetzt aus den Daten nicht erkennen, ob es Probleme gegeben hat. Wie kann man eigentlich bei der Vigor das Log direkt aufrufen?! Ich hatte es zwischendurch mal geschafft über den Port2 die Logs an meinen Server zu senden, aber das geht warum auch immer gerade nicht.
Ich hatte in dem Zeitraum nichts an der Konfiguration verändert, oder anders angesteckt. Das ist wirklich verrückt.
In den nächsten Tagen werde ich mal versuchen das Vigor Teil wieder als Router zu konfigurieren und dann die UDMP dahinter hängen, mal sehen ob in dem Fall auch nach einiger Zeit Probleme auftreten werden.
Oder hat jemand noch eine andere Idee?