NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WNDR3400v3 Wireless devices have a different subnet than wired. How can I forward requests between?
How can I setup my router to provide routing between 192.168.1.x and 192.168.0.x?
All of my wired devices have an ip address of 192.168.1.x, and all of the wireless have 192.168.0.x. As a result, I cannot ping nor connect to the wired side, from devices on wireless.. But I'd like to, especially for remote desktop, without going out to the WAN like with LogMeIn. I could get the two networks connected, then I could just use RDP on the LAN.. Would be nice.
I don't really want to Re-Ip any of the sides, or have them both on the same subnet. My question is, how can I setup my router to provide routing between these two networks?
6 Replies
> WNDR3400v3 Wireless devices have a different subnet than wired. How
> can I forward requests between?It might help if you began at the beginning. How many routers have
you? Modem (or other ISP interface gizmo)? What, exactly, is connected
to what, exactly? (Hint: If a device has multiple Ethernet ports, then
"connected to device" is not enough detail.)Assuming that you have two routers, why? Why is one of them not
configured as a wireless access point?What are the WAN/Internet and LAN IP addresses of each router? "a.b"
of "a.b.c.d" would be enough of your public IP address to satisfy my
curiosity; all other IP addresses reported should be actual.> All of my wired devices have an ip address of 192.168.1.x, [...]
And they're connected to what?
> [...] and all of the wireless have 192.168.0.x.
And they're connected to what?> I don't really want to Re-Ip any of the sides, or have them both on
> the same subnet. [...]Why not? (Would that make too much sense, or be too easy?)
> [...] My question is, how can I setup my router to provide routing
> between these two networks?
Which "my router"?Assuming that you've cascaded two routers, the usual way is to
configure a static route on the outer router (the one closer to the
ISP). With my weak psychic powers, I have little idea what that device
might be, so offering specific advice is difficult.Note that the WAN/Internet IP address of the inner router must be
fixed (static, or reserved dynamic), because that address appears in the
static-route rule (on the outer router).With two cascaded routers, "double NAT" could still be a problem.
(Using one router and one or more WAPs avoids that problem.)Hello Antinode,
You are correct I didn't give much detail. All of the devices are either connected to the NetGear WNDR3400v3's ethernet ports, or accessed through it's own wireless capabilities. The ISP router it is uplinked through (through the WAN port), has no connection other than this router. I basically moved everything down to it.
So all devices, wired or wireless, going through the Netgear WNDR3400v3.
On the Netgear Router, in the Admin page, it seems to be running DHCP separately for each.. Perhaps I can just widen the subnet mask? Or I can set the range of the 2nd DHCP server to correspond with the end of the 1st DHCP server's range? I didn't see any features that say anything like "Make Wireless devices visible to wired devices on the same router". I suspect it's only unreachable due to the subnet.
I guess I was hoping there was a simple box to check somewhere that would just route between the two subnets within the Netgear.
Of course also I like your suggestion for a static route from the outer-router (that was fun to say) would loop the traffic back into the Netgear on the other subnet just fine. Thoughts?
I'm also curious about what an Access Point configuration would be, would all devices then just fall onto the internal network provided by my ISP's router, and bypass most of this (redundant at this point for me?) functionality?
> [...] All of the devices are either connected to the NetGear
> WNDR3400v3's ethernet ports, or accessed through it's own wireless
> capabilities. [...]In that case, all your devices which use DHCP should get addresses
from the DHCP pool on the WNDR3400v3, and they all should be in the same
subnet.> [...] The ISP router [...]
Still not a very detailed description of anything.
> So all devices, wired or wireless, going through the Netgear
> WNDR3400v3.And if you power-off your WNDR3400v3, all these devices lose their
Internet access?
And if you power-off your (unspecified) "The ISP router", they all
stay connected to your LAN? (But not to the Internet, of course.)> On the Netgear Router, in the Admin page, it seems to be running DHCP
> separately for each.. [...]Huh? Which "the Admin page"? "each" what? The WNDR3400v3 should
have one DHCP address pool, specified somewhere around (I'd expect)
ADVANCED > Setup > LAN Setup : Use Router as DHCP Server.> I guess I was hoping there was a simple box to check somewhere that
> would just route between the two subnets within the Netgear.There should not be "two subnets within the Netgear". I suspect that
there are not "two subnets within the Netgear".> Of course also I like your suggestion for a static route from the
> outer-router (that was fun to say) would loop the traffic back into the
> Netgear on the other subnet just fine.
It was a fine suggestion, but it makes sense only if you actually
have two routers, with client devices connected to both. Which you
deny.> Thoughts?
> What are the WAN/Internet and LAN IP addresses of each router? "a.b"
> of "a.b.c.d" would be enough of your public IP address to satisfy my
> curiosity; all other IP addresses reported should be actual.Still wondering.
My guess still is that your wireless devices are connected to one
router, and your wired devices to the other. That would explain the
different LAN subnets, and the trouble communicating between devices on
the two LAN subnets.