Goedemiddag,
Ongeveer 2 maanden geleden is de Cisco epc3212 verplicht vervangen door Connectbox. Helaas ervaar ik sinds de wissel naar de Connectbox veel connectie problemen. Met gamen(snelle shooters) merk ik heel duidelijk een flinke achteruitgang in de verbinding. Ook de VPN verbinding naar het werk toe is trager geworden.
Met de Cisco epc3212 modem had ik echt geen enkel probleem.
Na wat zoekwerk blijkt dat Ziggo helaas modems gebruikt met de waardeloze Puma chipset. Snap echt niet waarom deze nog geleverd worden. En nee de software updates lossen de problemen niet op, omdat het een hardware probleem is.
Het thuisnetwerk is allemaal kwaliteitsspullen, met CAT6A kabels. Daar ligt het dus niet aan.
Graag ontvang ik de Ubee UBC1318ZG ter vervangen van de connectbox.
Gebundelde downstream-kanalen |
Kanaal | Frequentie (Hz) | Vermogen (dBmV) | SNR (dB) | Modulatie | Kanaalnummer |
1 | 610000000 | 2 | 37 | 256qam | 2 |
2 | 602000000 | 2 | 37 | 256qam | 1 |
3 | 618000000 | 2 | 37 | 256qam | 3 |
4 | 626000000 | 2 | 37 | 256qam | 4 |
5 | 634000000 | 2 | 37 | 256qam | 5 |
6 | 642000000 | 2 | 37 | 256qam | 6 |
7 | 650000000 | 2 | 37 | 256qam | 7 |
8 | 658000000 | 1 | 37 | 256qam | 8 |
9 | 666000000 | 2 | 37 | 256qam | 9 |
10 | 674000000 | 2 | 36 | 256qam | 10 |
11 | 682000000 | 2 | 37 | 256qam | 11 |
12 | 690000000 | 1 | 37 | 256qam | 12 |
13 | 698000000 | 1 | 37 | 256qam | 13 |
14 | 706000000 | 1 | 37 | 256qam | 14 |
15 | 714000000 | 1 | 36 | 256qam | 15 |
16 | 722000000 | 1 | 37 | 256qam | 16 |
17 | 730000000 | 1 | 37 | 256qam | 17 |
18 | 738000000 | 1 | 37 | 256qam | 18 |
19 | 746000000 | 0 | 37 | 256qam | 19 |
20 | 754000000 | 0 | 36 | 256qam | 20 |
21 | 762000000 | 0 | 36 | 256qam | 21 |
22 | 770000000 | 0 | 36 | 256qam | 22 |
23 | 778000000 | -1 | 36 | 256qam | 23 |
24 | 786000000 | 0 | 36 | 256qam | 24 |
| | | | | |
Gebundelde downstream-kanalen | |
Kanaal | Locked Status | RxMER (dB) | Pre RS Errors | Post RS Errors | |
1 | Goed (Locked) | 37.356 | 206531428043 | 5192 | |
2 | Goed (Locked) | 37.636 | 206499385323 | 3933 | |
3 | Goed (Locked) | 37.356 | 206455466539 | 4022 | |
4 | Goed (Locked) | 37.356 | 206528829938 | 3360 | |
5 | Goed (Locked) | 37.356 | 206520439797 | 3657 | |
6 | Goed (Locked) | 37.356 | 206389702051 | 3701 | |
7 | Goed (Locked) | 37.636 | 206439551641 | 3526 | |
8 | Goed (Locked) | 37.636 | 206528826170 | 3702 | |
9 | Goed (Locked) | 37.356 | 206389678408 | 3499 | |
10 | Goed (Locked) | 36.610 | 206447938007 | 3786 | |
11 | Goed (Locked) | 37.356 | 206528833499 | 3090 | |
12 | Goed (Locked) | 37.356 | 206528833704 | 2681 | |
13 | Goed (Locked) | 37.356 | 206528824598 | 2556 | |
14 | Goed (Locked) | 37.356 | 206345451281 | 120445 | |
15 | Goed (Locked) | 36.610 | 206372868826 | 20021 | |
16 | Goed (Locked) | 37.356 | 206523841506 | 3344 | |
17 | Goed (Locked) | 37.356 | 206528825338 | 2499 | |
18 | Goed (Locked) | 37.356 | 206447820577 | 2461 | |
19 | Goed (Locked) | 37.356 | 206520284436 | 2481 | |
20 | Goed (Locked) | 36.610 | 206491849311 | 3431 | |
21 | Goed (Locked) | 36.387 | 206528835291 | 4588 | |
22 | Goed (Locked) | 36.610 | 206528836679 | 3686 | |
23 | Goed (Locked) | 36.610 | 206401862581 | 5343 | |
24 | Goed (Locked) | 36.387 | 206528822980 | 7877 | |
Gebundelde upstream-kanalen |
Kanaal | Frequentie (Hz) | Vermogen (dBmV) | Symbol Rate (ksps) | Modulatie | Kanaalnummer |
1 | 37100000 | 39 | 5.120 | 64qam | 4 |
2 | 23300000 | 39 | 2.560 | 64qam | 6 |
3 | 30200000 | 39 | 2.560 | 64qam | 5 |
4 | 44000000 | 41 | 5.120 | 64qam | 3 |
5 | 50900000 | 41 | 5.120 | 64qam | 2 |
6 | 57800000 | 41 | 5.120 | 64qam | 1 |
| | | | | |
Gebundelde upstream-kanalen |
Kanaal | Kanaal soort | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | 2.0 | 0 | 0 | 16 | 0 |
2 | 2.0 | 0 | 0 | 14 | 0 |
3 | 2.0 | 0 | 0 | 15 | 0 |
4 | 2.0 | 0 | 0 | 10 | 0 |
5 | 2.0 | 0 | 0 | 12 | 0 |
6 | 2.0 | 0 | 0 | 9 | 0 |
5-8-2022 00:10 | notice | GUI Login Status - Login Sucess from LAN interface; client ip=[95.96.79.156];CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
4-8-2022 17:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
3-8-2022 04:00 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
1-8-2022 05:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
31-7-2022 08:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
28-7-2022 17:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
27-7-2022 19:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
26-7-2022 09:31 | warning | [AC:22:05:B2:B5:11][DFS] Radar signal detected, DFS sequence applied, channel changed from 100 to 44 |
25-7-2022 05:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
24-7-2022 11:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
21-7-2022 17:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
20-7-2022 23:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
18-7-2022 05:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
17-7-2022 19:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
14-7-2022 17:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
13-7-2022 06:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
11-7-2022 05:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
10-7-2022 21:06 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
7-7-2022 17:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
6-7-2022 16:09 | critical | No Ranging Response received - T3 time-out;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |
4-7-2022 05:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=ac:22:05:b9:a9:69;CMTS-MAC=00:a2:89:26:57:21;CM-QOS=1.1;CM-VER=3.0; |