Lost internet connection

[kcs11]

  Status_Event Log.docx (Size: 16.58 KB / Downloads: 12)
  Status_Event Log.docx (Size: 16.58 KB / Downloads: 12)

Hi to all the proactive Helpers out there!

So I've been using my sb5101i modem for over a year now, without a problem. Recently, somehow it kicked me offline, leaving me with all lights flashing on the modem and no internet connection ever since. I may think it has something to do with a simple poweroutage, so when it came back on, it rebooted my modem.

I've been using the older version (version 1.06rc6) of haxorware. Will my modem be affected by the bpi+ enforcement changes if I upgrade it to the current version (1.1 rev.39)?

I'm not sure what went wrong with my connection, can someone please help me out here.

My stats, modem, and event logs are provided below.

Your help is greatly appreciated. Thank you.
==================
sb5101i, hax0rware version 1.Orc6
San Fernando Valley, Los Angeles, California
timeWarnerc able

===================






























===============================================================

Status Event Log

Built on Fri Nov 21 12:05:16 2008
Uptime: 10s
Status: Ranging Complete
DS: -7.2 dBmV/36.2 dB US: 54.5 dBmV
Haxorware
Version 1.0rc6
Event Log
Time Priority Code Description
2011-10-03 03:58:25 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:13 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-10-03 00:46:29 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2011-10-03 00:46:16 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2011-09-26 02:46:57 Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2011-09-23 17:25:45 Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:02:55 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:45 Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:02:17 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:16 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:12 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:12 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:11 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:11 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:58 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:57 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:46 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:45 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:22 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:20 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:55 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:54 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:30 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:29 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:05 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2011-09-23 17:10:12 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2011-09-23 17:09:34 Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti
2011-09-23 17:09:23 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:39:41 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:38:41 Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:38:13 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:12 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:51 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:51 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:47 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:46 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:37 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:36 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:33 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:32 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:20 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:13 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:11 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:36:56 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:36:54 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:36:30 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:36:29 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:36:25 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:36:25 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:36:03 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:36:03 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:36:01 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:36:00 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:36 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:35 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:34 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:33 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:24 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:21 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:21 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:19 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:18 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:35:17 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:35:15 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:34:50 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:34:45 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:34:44 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:34:27 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:34:27 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:34:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:34:19 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:55 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:54 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:44 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:44 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:43 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:43 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:43 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:42 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:24 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:24 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:33:22 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:33:01 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:59 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:32:36 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:35 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:32:33 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:32 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:32:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:32:21 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:20 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:32:08 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:06 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:31:43 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

[Mordeth]

Selective areas within the SFV area have been upgraded to Doc 1.1 recently...meaning you need valid certs. There are many areas that are still @Doc 1.0, but it seems that is no longer for your node.

Some of you might ask as why I did not name the cities....well, there are a lot of holes in the SFV that can operate with even BPI "disabled", so it's meaningless. TWC seems to be upgrading the security one node a at time and in no logical order, as one would think that they would start/finish either by one zip code or within one particular city's limits, but that is not the case.

[kcs11]

Selective areas within the SFV area have been upgraded to Doc 1.1 recently...meaning you need valid certs. There are many areas that are still @Doc 1.0, but it seems that is no longer for your node.

Some of you might ask as why I did not name the cities....well, there are a lot of holes in the SFV that can operate with even BPI "disabled", so it's meaningless. TWC seems to be upgrading the security one node a at time and in no logical order, as one would think that they would start/finish either by one zip code or within one particular city's limits, but that is not the case.

Thank you for your response, Mordeth. How can I tell if I'm on Doc. 1.0 or 1.1?

[skribblz]

If you can change your mac address to any valid one and have it work you are in 1.0, but if you are stuck at ranging with a valid mac, it means you are on 1.1 and you need matching certs that go along with that mac.

[Mordeth]

In my my reply to your post, I stated..."but it seems that is no longer for your node"...which was the answer to your question? In any case, I concur with "skribblz"...as in your Baseline Privacy page/photo, you have it at Doc 1.0. For the hell of it, you can just try changing it to Doc 1.1 (optional in the setting) and just see what happens. We all learn from trial and error.