Static Route Problem

[bschoolm]

I have a lan on 192.168.251.x (Router: 192.168.251.1)

I have a wireless lan giving out 192.168.0.x (Router: 192.168.0.1)

I'd like computers on both subnets to be able to connect to each other.

My understanding is that I should do the following:

(on the wireless lan)
Destination: 192.168.251.0
Subnet: 255.255.255.0
Gateway: 192.168.0.1
Metric: 1

This is not working... what am I doing wrong??

 

[Genx87]

Easiest way to fix this is to simply turn the wireless router into a node and turn off its dhcp. Plug the wireless router into the 192.168.251.x network on its switch.

When people connect to the wireless it will authenticate them then send the DHCP request back to your wired router.

 

[spidey07]

yep, you'll need the wired and wireless all on the same network.

 

[bschoolm]

I have it setup that way right now actually, but I wanted to figure out this static route thing for my general knowledge.

Thanks!

 

[ch33zw1z]

Originally posted by: bschoolm
I have a lan on 192.168.251.x (Router: 192.168.251.1)

I have a wireless lan giving out 192.168.0.x (Router: 192.168.0.1)

I'd like computers on both subnets to be able to connect to each other.

My understanding is that I should do the following:

(on the wireless lan)
Destination: 192.168.251.0
Subnet: 255.255.255.0
Gateway: 192.168.0.1
Metric: 1

This is not working... what am I doing wrong??

Originally posted by: bschoolm
I have it setup that way right now actually, but I wanted to figure out this static route thing for my general knowledge.

Thanks!

your posts contradict each other. Is the setup working or not?

 

[bschoolm]

Sorry about that.

It is not working with the setup in my 1st post using the static route.

It does work/has always worked if I disable DHCP and just make the wireless router an access point.

 

[RebateMonger]

You didn't say what model your router is. But it's unlikely you'll be able to route between two subnets without an additional "real" router. Or your single router would need to be capable of handling VLANS.

The "Static Routing" feature of most consumer-level "routers" is intended to forward traffic to a second router (such as an ISDN device), where it is then routed to a different network (typically to the Internet). But that second router would have to be able to "route", not just NAT, or else you'll only be able to initiate traffic from one direction.

Netgear's explanation of the Static Routing feature of their consumer routers.

Or, if you are trying to set up static routing inside of Windows, then it'll need to point to a second router to do the actual routing. And the second router needs to be a "real" router, that routes and doesn't just provide NAT. Otherwise, you'll only be having one-way communications with the devices on that second subnet.

 

[nweaver]

yeah, with consumer level gear, you can probably get wireless to talk to wired (or vice versa) but not both at the same time.

 

[bschoolm]

Thanks for the post everyone.

I have a NetGear MR814 and I used that Static Routing instructions in the Netgear's manual, but its not working. I guess it will not work with the consumer level. Seems like if the router has a "static route option" it would work though.

Can someone verify the entries that I put in the static route are correct (my original post)?

Thank you

 

[nweaver]

the answer is...it depends.....

Where are you putting that route?

 

[bschoolm]

Internet --------> Router A ------------------> Router B
..............................| ........................................|
..............................| ........................................|
..............................| ........................................|
..............................\/ ......................................\/
..........................Computer A.........................Computer B
.............................192.168.251.3......................192.168.0.3
................................Gateway: x.x.251.1.............Gateway: x.x.0.1

This is my settings on Router B:
Destination: 192.168.251.0
Subnet: 255.255.255.0
Gateway: 192.168.0.1
Metric: 1

Should computer B be able to access Computer A now?

 

[JackMDS]

If set correctly (without Static Routing) computer B should be able to access A, however A would Not Access B. If you put B on the DMZ it would access it.

 

[DJediMaster]

You may need to set up a virtual interface on your router B that belongs to the 192.168.251.0 network. That way it knows how to get there. Right now it seems that it doesn't know how to get there through the gateway x.x.0.1. The best way to see this is try to telnet or ssh into router B and try pinging router A. It probably won't know how to get to it.

Route all traffic going to the destination (192.168.251.0) like you did but use the virtual interface you set up as the gateway(on the 192.168.251.0 network) instead. The router has to know about both networks to foward the packet correctly.

 

[bschoolm]

Makes sense...

Thanks for everyones help.