Some routing help..

[Bok]

Struggling with this..

I have a home network configured on the 192.168.1.0 domain.

Fairly recently I upgraded my wireless router which I use for a few PC's. It had to be on a different subnet so it's set to be on 192.168.2.0, with a WAN ip of 192.168.1.150..

All well and good, my laptops get assigned IP addresses in the 192.168.2.15* just fine and connect to the outside world ok routing through this router , as does the wii and my son's PC..

But I want to be able to get to these pc's the other way from one of my desktops (so I can monitor BOINC via boincview).

I've been messing about with setting up static routes but haven't been able to get it to work at all? Not sure if it's the router or my routes!!

I put in

route add 192.168.2.0 mask 255.255.255.0 192.168.1.150

and then a tracert to 192.168.2.151 seems to try to go through the router but never gets there..

Any advice ?

[IronBits]

With NAT, it's going to very difficult.
Set the wireless up as a gateway, not a router, then they will all have same ip subnet ;)

Also try and pull the subnet mask out on all systems so the devices can see both “nets” as a single net, without having to use a router.

[gopher_yarrowzoo]

Personally I'd only have 1 master device giving out IP's
If you just need a wireless point would a Wireless Access Point not have done? no real configuration of it and it means you could fix ip's in your main router for the wireless stuff
I can see why you may need to do that but change the DHCP of the main router to a smaller pool or
all devices subnet mask to 255.255.252.0, maybe 255.255.254.0 would work.
that way 192.168.1.x and 192.168.2.x would see each other
I'd personally have each router set as 192.168.1.25x
primary being 254 this new one being 253 on it's "LAN" facing port and the wireless as 192.168.2.254 if required..
KISS :)

[Bok]

I think the wireless router has to be the one giving out ip's to wireless machines via dhcp, so I'm stuck with it on the .2.x subnet, but I can't figure out how I could get my other machines to get an address from it as it's only really listening on the wireless side for dhcp requests that I can tell. None of the lan machines see it as a dhcp server.

I even tried natting some connections forward through the router but couldn't get that to work either.. :(

I'll play around a bit more tomorrow and see if I can do anything with it. Probably missing something obvious..

Bok :cheers:

[LAURENU2]

I think the wireless router has to be the one giving out ip's to wireless machines via dhcp, so I'm stuck with it on the .2.x subnet, but I can't figure out how I could get my other machines to get an address from it as it's only really listening on the wireless side for dhcp requests that I can tell. None of the lan machines see it as a dhcp server.

I even tried natting some connections forward through the router but couldn't get that to work either.. :(

I'll play around a bit more tomorrow and see if I can do anything with it. Probably missing something obvious..

Bok :cheers:
I think you wrong about

I think the wireless router has to be the one giving out ip's to wireless machines via dhcp

I have set wire or wireless routers to be a pass-through or hub or Dchp router just give the 2nd and 3rd router a static IP address so you can manage it

You can set one router to be a gateway ( 192.168.1.10 )and the 2nd (192.168.1.1 )to be a Dchp server and the 3rd ( 192.168.2.1 )to be a managed hub or a subnet

[Bok]

yes, you're right actually. I could set it up like that. I'd just have to set up a dhcp server on one of my linux servers.

Thanks for pointing it out. I was overcomplicating things :)

Bok :cheers:

[IronBits]

Set the wireless up as a gateway, not a router, then they will all have same ip subnet http://www.free-dc.org/forum/images/smilies/wink.gif