route doubt

Am I using the route command correctly? I seldom have to mess with it, and I
fear I'm missing something obvious.

The objective: I want to temporarily hook my linksys WRT54G router (192.168.1.1)
to my home LAN (192.168.0.*) to load custom firmware.

The laziest way to do this, I thought, would be to hook one of the LAN ports on
the linksys to my main switch, and let it figure out the pinouts (can't be arsed
to find a crossover cable right now, but LEDs on both the linksys and the switch
indicate they're happy with the connection). Yes, the linksys's DHCP server is
active, but this is to be a very temporary setup.

So I tried to set up a static route on my main (Linux) router as follows:
# route add 192.168.1.0 eth1

Its routing table now looks like this:

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.255 UH 0 0 0 eth1
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
66.223.224.0 * 255.255.248.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
default 1-224-223-66.gc 0.0.0.0 UG 0 0 0 eth0

Using a command shell on that Linux router, I've tried to ping the linksys at
192.168.1.1. I admit that I hardly ever muck with routes, so perhaps I'm
missing something obvious. Is there a simple fix for this, a complicated fix,
or am I trying to do something that Ought Not Be Done?

(Of course, I could just download all the firmware files to a spare PC and
connect it directly to the Linksys, and I'd have been done long ago. But now
it's a matter of principle. ;) )

Many thanks.

-Lauren
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jul 4 13:12:39 2006