Eric on 15 Nov 2008 13:38:52 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] network hardware follies


On 11/15/2008 11:03 AM, Casey Bralla wrote:
> On Saturday 15 November 2008 9:06:23 am Eric wrote:
>> I'm trying to reset a Linksys RTP300 that my wife obtained for me from
>> Freecycle.  It is a Linux-powered VoIP router.  The history of the device
>> is unknown but I would presume that it's a former Vonage unit.  That may be
>> a totally bogus assumption, I'll admit, but where it came from is
>> irrelevant IF I can get it to work.
> If it is the Lynksys, I assume the data on this page may be of big help.

Ah, good.  Thanks.  I found most of those documents already but not all in one 

>> To begin to hack the device I powered it up and held the reset button for
>> about 1 minute (later extended to 3 minutes.)  In all cases there is no
>> response from the default address ( on one of the LAN ports)
>> after the unit was "reset".  This mirrors my experience with Linksys
>> devices which appear to resist resetting with a tenacity usually attributed
>> to pitbulls.
> That's an odd sounding default address.  My guess would be, or
> maybe

The documentation claims that yes it does seem odd.  If it's in 
the 192.168.1.x range then it may clash with my existing network so I'll 
improvise a separate hardware connection.

>> The power is there (14.4V) and the LED's light up appropriately.  I even
>> opened the device and checked to be sure the reset switch actually had 0
>> volts across it when pressed (of course it did.)
>> The courses of action I can think of are:
>> 1.  Use nmap to scan like crazy trying to find the ip address that the unit
>> is using which I presume is in one of these ranges:
>> (netmask of
>>    OR
>> (netmask of
> These sound like good ranges to search.
>> 2.  Reset it as before but remove the power supply connection and short the
>> power input leads for about 24 hours to be sure it's really really really
>> powered off.  I tried this for 1 minute with no detectable result.
> I doubt if anything more than 60 seconds would be necessary.
>> 3.  Place the unit in a local trash receptacle with unusual force.
> I chuckled at this one.   Maybe this is why it was available on freecycle?

So I thought as well - but the original email claimed that it was working.  Why 
make somebody drive 15 miles to pick up trash was my thought :-)

>> Following course #1 first:
>> I'd like to hook it directly to a pc running Kubuntu and run nmap.  Can I
>> use a "crossover" Ethernet cable for that purpose?  I just happen to have
>> one.  If I do that is the IP address even relevant as long as it goes out
>> of the Ethernet port?
> Cross over would work for a direct connection.   It also might be good to go
> through a hub, just so you can see the blinky-blinky lights.

Have one of those... I'll try it.

>> What kind of nmap scan would be the quickest and still be most likely
>> detect the unit?  I tried a ping scan over the home network and it takes
>> about 40 seconds to scan the range.  At that rate the
>> entire range will be about 3 hours.  I'm trying not to think
>> about the range. Okay, okay... I thought about it: 728 hours or
>> about 1 month.  I'd rather try #2 or #3 first :-)
> I'd do the default nmap scan.  You want to look for port 80 (web pages),
> telnet, ssh, and probably some others that I can't think of.   The ping may
> not echo, even if you get the correct IP address, so I wouldn't trust a
> simple ping.   This may take time to run, but it's a rainy day anyway :)
>> Ideas and suggestions are really welcome!  At this point I'm starting to
>> run out of ideas and #3 is starting to look better and better :-(
>> Eric

#  Eric Lucas
#                "Oh, I have slipped the surly bond of earth
#                 And danced the skies on laughter-silvered wings...
#                                        -- John Gillespie Magee Jr
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --