Page 1 of 1
UPC Technicolor TC7200.U
Posted: 19 Feb 2014, 16:36
by admin
As of december 2013 my new Cable router:
Code: Select all
Technicolor TC7200.U
sn SAAP3xxxxx01
Mac1 CC35xxxxxxE6
Mac2 CC35xxxxxxE7
ssid1 UPC165xxx1 (2.4GHz)
wpa2 ********
ssid2 UPC665xxx1 (5.0GHz)
wpa2 ********
With 4 x 1GBps HUB, following info WAN offline:
Code: Select all
CM Software Information
Standards Compliancy DOCSIS 3.0
Software Version STD6.01.12
Hardware Version 1.0
HFC MAC Address cc:35:xx:xx:xx:e6
Gateway Serial Number SAAP3xxxxx01
EuroDOCSIS: installed
Installed Certification DOCSIS: installed
EuroPacketCable: installed
System Uptime 0 days 04h:51m:39s
Network Access Denied
CM IP Address ---.---.---.---
WAN Online:
Code: Select all
CM Software Information
Standards Compliancy DOCSIS 3.0
Software Version STD6.01.12
Hardware Version 1.0
HFC MAC Address cc:35:xx:xx:xx:e6
Gateway Serial Number SAAP3xxxxx01
EuroDOCSIS: installed
Installed Certification DOCSIS: installed
EuroPacketCable: installed
System Uptime 0 days 00h:46m:21s
Network Access Allowed
CM IP Address 10.18.xxx.xxx
CM Connection Information
Connectivity State Operational
Boot State Operational
Security Enabled
CM IP Address 10.18.xxx.xxx
CM Lease Time D: 07 H: 00 M: 00 S: 00
CM Lease Expiration Wed Dec 11 18:01:43 2013
System Time Wed Dec 04 18:11:59 2013
Internet Status
IP Address 46.129.xxx.xxx
Subnet Mask 255.255.255.0
MAC Address CC:35:xx:xx:xx:E8
Duration D: 03 H: 00 M: 00 S: 00
Expires on 2013-12-07 18:07:33
Host Name (if required by ISP)
Domain Name (if required by ISP)
-----
As this is new and 'from provider', I leave it just passing Internet, and as the provider told me, they activated ' HotSpots' on the 16 Wifi channels this device has
I can activate 2 x 2,4 GHz and 2 x 5GHz WiFi, so i guess that leaves 12 channels for the HotSpots.
Ports that need to be routed are working, so far this device. Not (much) more yet ...
DG.
WAN Renew Does not work
Posted: 07 Mar 2014, 22:00
by admin
This is the code from the web interface:
Code: Select all
<!-- hide me
function RenewWanLease(oForm)
{
oForm.elements["WanLeaseAction"].value = 1;
}
function ReleaseWanLease(oForm)
{
oForm.elements["WanLeaseAction"].value = 2;
}
// show me -->
Still the button does not do anything, most probably UPC assigns addresses according MAC and will not change unless it is suppose to by the ISP.
UPC box log:
Code: Select all
2014-03-07 03:04:11: [Info] WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A)...
2014-03-07 02:49:07: [Info] WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A...
2014-03-07 01:48:49: [Info] WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A)...
2014-03-07 01:33:44: [Info] WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A...
2014-03-06 20:32:37: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-03-06 20:31:53: [Info] TLV-11 - unrecognized OID;CM-MAC=cc:35:xx:xx:xx:xx;CMTS-MAC=c...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=cc:35:...
2014-03-06 20:31:49: [Minor] Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=cc:35:...
--- -- --:--:--: [Warn] DHCP WARNING - Non-critical field invalid in response ;CM-MAC...
--- -- --:--:--: [Info] Honoring MDD; IP provisioning mode = IPv4
--- -- --:--:--: [Info] WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A)...
2014-03-06 18:51:45: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-03-06 18:47:41: [Major] Received Response to Broadcast Maintenance Request, But no Un...
--- -- --:--:--: [Major] No Ranging Response received - T3 time-out;CM-MAC=cc:35:40:2f...
2014-03-06 18:44:44: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-03-06 18:35:47: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-03-06 16:50:32: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-03-03 05:07:04: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2014-03-03 05:06:57: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2014-03-03 05:06:50: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2014-03-01 12:00:29: [Major] Started Unicast Maintenance Ranging - No Response received - ...
2014-02-26 12:56:57: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2014-02-26 12:56:45: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2014-02-24 11:42:33: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-02-24 11:41:26: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
..
Re: UPC Technicolor TC7200.U
Posted: 13 May 2014, 20:43
by admin
After Lightning strike 3 houses away (
http://apeldoorn.nieuws.nl/nieuws/20140 ... n-de-Maten) port 3 of the router/hub is defect and port 4 only runs 100MBit.
Asked ISP for new modem/router.
DG.
Re: UPC Technicolor TC7200.U
Posted: 17 May 2014, 10:23
by admin
As from today, new TC7200U modem:
Code: Select all
STATUS
This page displays cable modem system information.
CM Software Information
Standards Compliancy DOCSIS 3.0
Software Version STD6.01.12
Hardware Version 1.0
HFC MAC Address 88:f7:c7:1x:xx:xx
Gateway Serial Number SAAP33534423
EuroDOCSIS: installed
Installed Certification DOCSIS: installed
EuroPacketCable: installed
System Uptime 0 days 00h:40m:39s
Network Access Allowed
CM IP Address 10.18.2xx.1xx
Community Wi-Fi SSID UPC WifiSpots
Community Wi-Fi Status Enabled
Number of devices connected to Community Wi-Fi 0
Re: UPC Technicolor TC7200.U
Posted: 19 Jun 2014, 02:49
by admin
TC7200U loggings
-----------------
Code: Select all
--- -- --:--:--: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
--- -- --:--:--: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
--- -- --:--:--: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
--- -- --:--:--: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
--- -- --:--:--: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
--- -- --:--:--: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
--- -- --:--:--: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
--- -- --:--:--: [Info] WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A)...
2014-06-19 01:58:19: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:58:05: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:57:44: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:57:21: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:56:54: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:56:39: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:56:22: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:56:06: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:55:39: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:55:20: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:54:59: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:54:43: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:54:08: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:53:48: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:53:25: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:53:03: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:52:35: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:52:17: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:51:56: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:51:33: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:51:07: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:44: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:27: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:08: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
Code: Select all
2014-06-19 01:51:21: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:51:07: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:51:07: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:44: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:50:44: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:27: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:50:27: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:50:08: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:50:08: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:49:40: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:49:40: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:49:16: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:49:15: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:48:54: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:48:54: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:48:34: [Warn] B-INIT-RNG Failure - Retries exceeded;CM-MAC=88xx:xx:xx:xx:x...
2014-06-19 01:48:34: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
2014-06-19 01:48:05: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2014-06-19 01:45:54: [Major] Started Unicast Maintenance Ranging - No Response received - ...
2014-06-19 01:12:30: [Info] TLV-11 - unrecognized OID;CM-MAC=88:xx:xx:xx:xx:xx;CMTS-MAC=c...
2014-06-19 01:12:26: [Minor] Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=88:xx:...
2014-06-19 01:12:19: [Minor] Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=88:xx:...
2014-06-19 01:12:18: [Minor] Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=88:xx:...
2014-06-19 01:12:18: [Minor] Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=88:xx:...
2014-06-19 01:12:16: [Warn] DHCP WARNING - Non-critical field invalid in response ;CM-MAC...
2014-06-19 01:12:12: [Info] Honoring MDD; IP provisioning mode = IPv4
2014-06-19 01:12:05: [Major] No Ranging Response received - T3 time-out;CM-MAC=88:xx:xx:xx...
Re: UPC Technicolor TC7200.U
Posted: 19 Feb 2015, 23:16
by admin
UPC Box gets busy?
Below a ping reply during a reboot of this modem/router.
A lot of timeouts at the end when i only use the internal web interface, which also does not respond good.
(iSCSI also running between NAS and ESXi server.)
Sometimes compete parts are not shown, even looks disconnected itself.
If disconnected, you can only login again by rebooting the modem/router, as you will always get 'Admin already signed in' error when trying to login.
Code: Select all
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Hardware error.
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=323ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1801ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=144ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=158ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=80ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=191ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=165ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=173ms TTL=64
Reply from 192.168.0.1: bytes=32 time=184ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=191ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=41ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=56ms TTL=64
Reply from 192.168.0.1: bytes=32 time=43ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=121ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=241ms TTL=64
Reply from 192.168.0.1: bytes=32 time=97ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=135ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=24ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=63ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=149ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=38ms TTL=64
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 195, Received = 158, Lost = 37 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1801ms, Average = 30ms
Control-C
^C
Re: UPC Technicolor TC7200.U
Posted: 11 Nov 2015, 19:49
by admin
As of april 2015 the internet UPC and Ziggo are now both under the name of Ziggo.
We can see now when login into the router they also changed UCP logo to Ziggo logo.
Tested the Ziggo Hotspots, which should be active according 'My Ziggo' login.
But i can't get my PC connected to the Ziggo Hotspot, as it does to the WiFi (LAN) login on the same router.
Not that interesting, so leave this as is.
DG.
Re: UPC Technicolor TC7200.U
Posted: 17 Nov 2016, 17:27
by admin
