[TriLUG] telocity->directvdsl->bellsouth

[David R. Matusiak]

this is a little hard to believe.  how could changing a network address 
"fry" an electronic device?  its not like we're talking about modelines 
on a laptop screen.

what exactly happened again?  and were there no other mitigating 
circumstances?  (i.e. lightning, soda spilled in the top, etc).

just curious, really.
/drm

On Wednesday, January 29, 2003, at 05:40  PM, Jim Ray wrote:

> One was a year old.  The other was two years old.  I tried 10.0.0.0/24
> and it puked hard.
>
>> -----Original Message-----
>> From: Jonathan Hassell [mailto:jon at jonathanhassell.com]
>> Sent: Wednesday, January 29, 2003 5:39 PM
>> To: trilug at trilug.org
>> Subject: RE: [TriLUG] telocity->directvdsl->bellsouth
>>
>> How old are these units you speak of?  I have both the 41 and the 81,
>> and on both I've moved to a 192.168.0.X network without problems.
> Mine
>> are both 2-3 years old, however.
>>
>> Jonathan Hassell
>>
>> -----Original Message-----
>> From: Jim Ray [mailto:jim at neuse.net]
>> Sent: Wednesday, January 29, 2003 5:36 PM
>> To: trilug at trilug.org
>> Subject: RE: [TriLUG] telocity->directvdsl->bellsouth
>>
>> I use the terms network id, number and address synonymously.  Yes, try
>> changing it from the default 192.168.1.X on a LinkSys BEFSR41 or
>> BEFSR81.  Make sure it is under factory warranty first.  It will fry.
>> Toast.  I've done it twice.  It is really cool.  Kudos to LinkSys for
>> replacing the failed units.