Puzzle: Determine router's IP address

On Mon, 25 Apr 2005 13:25:11 -0400, cdf <(E-Mail Removed)> wrote:
> Dale Dellutri wrote:
> > Is the MAC address printed or embossed on the device case? If so,
> > then cable it to your desktop (crossover needed?), set an unused ip
> > address in your subnet with arp, something like:
> > arp -v -s <desired IP addres> <MAC address> temp
> >
> > Then you can telnet to the desired IP address and set whatever you
> > like once you get into the Netopia 4652 device.

> That's a good suggestion. There are 12 digits/letters on the back of the
> router that do appear to be its MAC address. Didn't work though, I hope
> I am maybe missing someting:

> PC = 192.168.1.2
> router = 192.168.1.1

> # arp -v -s 192.168.1.1 00:00:B6:A2:A3:22 temp

> # cat /proc/net/arp
> IP address HW type Flags HW address Mask
> Device 192.168.1.1 0x1 0x2 00:00:B6:A2:A3:22 *
> eth0

> # ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> From 192.168.1.2 icmp_seq=9 Destination Host Unreachable
> From 192.168.1.2 icmp_seq=10 Destination Host Unreachable
> From 192.168.1.2 icmp_seq=11 Destination Host Unreachable

> # telnet also fails

> So, either "0000B6A2A322" printed on the back of the routher is not its
> MAC address or... I don't know.

Well, it's a _possible_ MAC address. The first six digits are
assigned to Micro-Matic Research of Belgium, who might have
manufactured the NIC for Netopia. But if you tried both staight
through and crossover cables, and both ping and telnet in both cable
cases, then maybe it's just dead. Did the amber/green lights on your
PC's NIC indicate a good connection?

> Regarding your suggestion about serial console interface... regretfully,
> I can't use it since the serial cable is missing.

Serial cables are pretty cheap. Since the router is about $350 new,
it might be worth it to get it going. Or perhaps you can borrow a
9-pin null-modem serial cable?

--
Dale Dellutri <(E-Mail Removed)> (lose the Q's)

Dale Dellutri wrote:
> Well, it's a _possible_ MAC address. The first six digits are
> assigned to Micro-Matic Research of Belgium, who might have
> manufactured the NIC for Netopia. But if you tried both staight
> through and crossover cables, and both ping and telnet in both cable
> cases, then maybe it's just dead. Did the amber/green lights on your
> PC's NIC indicate a good connection?

I got a response from Netopia and, fortunately, there is a way to reset
the router using its hardware "restore factory defaults button". The
problem was that "button" is not a button at all and you need a METAL
paper clip to "press" it. The IP address was something like
67.100.1.178... I could have been guessing it for years :-)

Anyway, it's working now. Thanks to everyone who responded.


P.S. I think your approach with "arp" should've worked and I'm surprised
it did not. When I was doing "ping" the respective green port light on
the router WAS blinking but the ping was failing. Well, I guess I'll
never know...

By Mon, 25 Apr 2005 16:59:34 -0400, cdf <(E-Mail Removed)>
decided to post "Re: Puzzle: Determine router's IP address" to
comp.os.linux.networking:

>Dale Dellutri wrote:
>> Well, it's a _possible_ MAC address. The first six digits are
>> assigned to Micro-Matic Research of Belgium, who might have
>> manufactured the NIC for Netopia. But if you tried both staight
>> through and crossover cables, and both ping and telnet in both cable
>> cases, then maybe it's just dead. Did the amber/green lights on your
>> PC's NIC indicate a good connection?
>
>I got a response from Netopia and, fortunately, there is a way to reset
>the router using its hardware "restore factory defaults button". The
>problem was that "button" is not a button at all and you need a METAL
>paper clip to "press" it. The IP address was something like
>67.100.1.178... I could have been guessing it for years :-)
>
>Anyway, it's working now. Thanks to everyone who responded.
>
>
>P.S. I think your approach with "arp" should've worked and I'm surprised
>it did not. When I was doing "ping" the respective green port light on
>the router WAS blinking but the ping was failing. Well, I guess I'll
>never know...


Post facto, I know, but the small reset hole is pretty standard hardware
stuff for reset-buttons. Usually they don't require metal; paper clips are
handy though, and usually around the right size and are stiff enough....

It seems like you could have made a quick script to ping the gamut of ip
addresses one time each and record each return-hit, much less use one of
many extant port-scanners to the same effect.

/..

--

find / -iname "*gw*" -exec rm -rf {} \;

In heaven, there is no beer,
That's why we drink it here,
And when we're all gone from here,
Our friends will be drinking all the beer!
-- Famous old Czech song about beer --

/.. <(E-Mail Removed)> wrote:
>>
>>P.S. I think your approach with "arp" should've worked and I'm surprised
>>it did not. When I was doing "ping" the respective green port light on
>>the router WAS blinking but the ping was failing. Well, I guess I'll
>>never know...
....
>It seems like you could have made a quick script to ping the gamut of ip
>addresses one time each and record each return-hit, much less use one of
>many extant port-scanners to the same effect.

Too late now, but just for fun... from a host that is physically on
the same Ethernet, do "ping 255.255.255.255" and see what kind of
response(s) you get. That router ought to just spit it right out.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)