Static route issue

unixfool · 05-18-2006, 06:34 PM

I've a FVS114 that I have established as a border firewall. I also have a Linksys WRT54GX4 that is serving DHCP IPs to hardwired and wireless devices on another subnet.

The diagram is here (hope it resolves correctly in this forum):

Code:

Cable Modem
           |
        FVS114 - - - - - - - - -WRT54GX4 (WAP and CAT5)
           |                                |
           |                                |
      10.150.1.0/24                  192.168.1.0/24
           |                                |
           |                                |
        5 CAT5                     3-5 WAP and 1 CAT5

Currently, I have no static routes added to either switch. When on a laptop, I can get each switch's admin interface, which means the 192.168.1.0/24 subnet can access the 10.150.1.0/24 subnet fine. The problem is that anything on the 10.150.1.0/24 can't access the 192.168.1.0/24 subnet. I can't ping or telnet to any machine on the WRT54GX4 subnet from the FVS114 side.

A friend told me I needed to add a static route on the Netgear. This friend is a network architect and a superb sys admin, so I know he's probably right. I did this before, long ago, but I've forgotten how I got this to work. I should have picked his brain more. Anyways, I've added a static route on the Netgear:

destination: 192.168.1.0
gateway: 10.150.1.1
metric: 2
active: yes
private: yes

I've went as far as changing private to yes and no and it doesn't make a difference (I didn't expect it to but I'm trying everything out of frustration).

I've read the FVS114 docs and I know I have the route correct. I've turned off the WRT54GX4's firewall and enabled NAT and DHCP. The Netgear has its FW on and NAT and DHCP is enabled. Based on this, the static route on the Netgear should be working. I shouldn't need a static route on the Linksys since there's none now and I can ping both networks fine from that subnet.

What little but crucial thing am I missing here??

TIA

acid_kewpie · 05-19-2006, 03:56 PM

ok, so if you wish to route to that network via the internal router then you would want to disable the NAT. when the NAT is enabled it will not pass data to the internal nodes, it will only respond to connections on that network.

I would ask if you actually do need a seperate subnet here though. you can use the wireless, DHCP and switching capabilities of that secondary router without using it as a NAT router. you can easily have a single network across all devices - just connect an internal port up to that router instead of the single external port, and don't set the internal router as the gateway.