Tja Zoni: Hier mal ein Auszug von meinem Modem (Motorola)
Wie du siehst hab ich auch wieder einmal die Connection verloren- war aber dann gleich wieder da ums gleich wieder zu verlieren!
Bei einem Livestream net sehr vorteilhaft!
Was zur zeit aufgeführt wir weis ich nicht- begeistert bin ich nicht davon muss man ja jederzeit damit rechnen- ich brauche aber stabile Verhältnisse fürs aufzeichnen meiner Podcasts!
Jul 24 2013 01:19:59 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:19:29 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0; Jul 24 2013 01:18:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:18:26 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:16:07 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:16:06 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:14:40 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:14:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:14:37 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:29 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:28 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:22 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:22 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2013 01:12:03 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:21:80:fc:a4:27;CMTS-MAC=00:01:5c:24:66:8d;CM-QOS=1.1;CM-VER=3.0;
Speed scheint nicht darunter zu leiden- da rennt noch ein Videostream im Background:
