A second IP address for a second second life

Since my wife and I have been having problems when connecting to Second Life at the same time, I went ahead and ordered a second IP Address from my cable company, Comcast. It costs $6.95 extra per month. To keep my budget within reason, I called up my cell phone company and asked them to change my phone plan. So after moving money around in the budget, it turns out that I’ll have about eighteen dollars more per month.

Anyhow the extra IP address was made available to me immediately – or so I was told. Rite now I’m just confused as to how to set one of my computers up to use the extra IP address. I have a Linksys Router (BEFW11S4 V2/V3) and a Terayon cable modem (TJ715x).

I discovered today that the cable modem has its own service located at http://192.168.100.1. This is interesting because I’ve seen this IP address before. I think our computers used to have its address in there network settings when we were troubleshooting our connection problems in the past. I always assumed that we were somehow connecting to a neighbors wireless DHCP hub.

A page went on to give information about many types of cable modems. This modem also has some diagnostic information at http://192.168.100.1/diagnostics_page.html. It has a password on the page. Chances are, if you know how to access the page, you probably know that the password is “icu4at!”.

Problem is, I went in here searching for something telling me how many computers are allowed to connect to the modem. I hear that the cable company needs to set my CPE parameter, and that it can only be changed by Tier 3 reps. I don’t know what I’m doing, and I’m not quite certain if I’m getting anywhere either.

Date (Y/M/D) Time Event ID Counter Level Event Text
1970/01/01 00:00:33 82000200 25 Critical No Ranging Response received – T3 time-out.
1970/01/01 00:00:33 82000300 1 Critical Ranging Request Retries exhausted
1970/01/01 00:00:33 85000200 1 Critical UCD invalid or channel unusable – T3 timeout: Giving up on UCD 6.
1970/01/01 00:00:31 82000200 25 Critical No Ranging Response received – T3 time-out.
1970/01/01 00:00:31 82000300 1 Critical Ranging Request Retries exhausted
1970/01/01 00:00:31 85000200 1 Critical UCD invalid or channel unusable – T3 timeout: Giving up on UCD 6.
1970/01/01 00:00:37 82000200 9 Critical No Ranging Response received – T3 time-out.
2005/08/23 00:08:45 82000400 2 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:00:09 82000200 2 Critical No Ranging Response received – T3 time-out.
2005/08/23 00:49:55 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:00:09 82000200 2 Critical No Ranging Response received – T3 time-out.
2005/08/23 01:38:21 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:00:07 82000200 1 Critical No Ranging Response received – T3 time-out.
2005/08/25 22:35:53 82000400 4 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
2005/08/28 08:53:43 84000500 1 Critical SYNC Timing Synchronization failure – Loss of Sync
2005/08/28 22:01:37 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
2005/08/29 00:06:09 84000500 1 Critical SYNC Timing Synchronization failure – Loss of Sync
2005/08/29 00:06:23 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:18:43 82000200 3 Critical No Ranging Response received – T3 time-out.
2005/12/01 11:56:07 82000400 4 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
2005/12/09 15:26:12 84000500 1 Critical SYNC Timing Synchronization failure – Loss of Sync
2005/12/09 15:26:37 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:01:04 82000200 2 Critical No Ranging Response received – T3 time-out.
1970/01/01 00:01:08 84000500 1 Critical SYNC Timing Synchronization failure – Loss of Sync
1970/01/01 00:01:10 82000200 1 Critical No Ranging Response received – T3 time-out.
2005/12/09 15:31:46 84000500 3 Critical SYNC Timing Synchronization failure – Loss of Sync
2005/12/11 00:47:31 82000400 1 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
1970/01/01 00:00:06 2242905932 1 Notice SNMP Poll – Eth Link Up.
2005/12/13 15:39:32 2242905917 1 Notice SNMP Poll – Mac Link Up.
2005/12/13 15:39:32 2242905786 1 Notice SNMP Poll – DS Link Up.
2005/12/13 15:39:32 2242905803 1 Notice SNMP Poll – US Link Up.
2005/12/13 15:39:33 2242905723 1 Notice SNMP_AGENT_COLD_START

Comments are closed.

%d bloggers like this: