Accessing a router which isn’t a DHCP server

I had a WRT54G in this exact situation.

1. Ensure your modem / router (in your case a Comcast Modem) to hand out DHCP addresses.
2. Ensure your modem and your Linksys both have IP addresses on the same subnet, but different addresses (192.168.1.1 and 192.168.1.2 are good examples)
3. Disable DHCP on your Linksys.

This is a sort of 'pass-though' - the Linksys will route all DHCP requests through to the rest of the network - where the router will catch them.

Since the rest of the network is on the same LAN as the Linksys, it shouldn't be given any dramas by NAT. Just don't use the WAN port.

I've used this exact setup for several years, and it has worked flawlessly. I can even take my wireless point to a friend's house and use it - especially if he has a different subnet, it won't interfere, and doesn't require any setup (again, the pass-through effect).

Edit: And if you have need of a 5th port, the WRT54G has the ability to use the WAN port as a LAN port. I'm not sure where it is, it's been a while since I replaced my WRT54G, but it's a superb unit.

This seems to be a common confusion: Wireless client mode means your router is working as a full-fledged router, except it is connecting to upstream via a wireless connection, not an ethernet one. Thus you cannot use your router as a wireless AP: its wifi is used to connect it to upstream, not downstream. Also, the Tomato router clients do not belong to the same LAN as the upstream router, in your case the Cisco E4200.

Many people seem to confuse this with bridge repeater mode. In this mode, your tomato router does not work as a router, just as a bridge that relays the communications of its ethernet clients via wifi to the upstream router: the ethernet clients and the primary router, as well as the Tomato router, belong to the same LAN.

Using the above distinction it is easy to see your error: you are using the same network (192.168.1.0/24) for both the upstream LAN and the downstream one, while isntead you are trying to use the Tomato router in the Wireless client mode.

Easy solution: change the LAN side network of the Tomato router to something very different, say 192.168.99.0/24, both in the LAN settings and in the settings of the DHCP server. This should cure your issues.

It is rather clear that any program finding out that WAN and LAN belong to the same network (192.168.1.0/24 in your case) will be utterly confused.

You may have to reboot for the changes to take effect.

EDIT:

since you have now made clear that you are interested in placing all of your machines in the same LAN network, I have to clarify that Tomato firmware does not allow this, since it has n support for bridge repeater mode. You can obtain such functionality instead either in DD-WRT (see the man page here) or in TomatoUSB, which is

an alternative Linux-based firmware for powering Broadcom-based ethernet routers

Yours is one such router, so that it is fully supported by TomatoUSB, see the table in this page. It has several improvements over pure Tomato, so that you may find it altogether advantageous to switch to it, even apart from your specific query.

You can find a good introduction to setting up a TomatoUSB-powered router in Bridge Repeater mode here, and you can even find a YouTube video to guide you in the process.

At any rate, it is very very simple:

first, using the Web GUI of your Linksys wrt54gl router in TomatoUSB, set up your only interface (it will be a bridge called br0) to have a static IP address, belonging to the same network of your primary router (thus 192.168.1.0/24) but outside the range of the primary router's DHCP server, so that no conflicts may arise.

Then go to the Wireless setup page, enable wireless, choose in the drop-down menu the operating mode Wireless Ethernet Bridge, and then insert the name and password of your primary router's Wireless network. Save and wait 10 seconds, or reboot your Linksys wrt54gl.

That's it.