- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jumpin68ny wrote:I would assume that at some point he should be able to ping the dhcp addresses too but possibly would have to enable RIP on the VZ or Linksys router for that to happen?
In your original post you said there would be a need for a static route on the 2.x router pointing to 192.168.1.1 You didn't mention that again on your 2nd post. Is it in fact needed?
Assuming NAT is disabled and routing tables are set up properly then yes, the users on both networks should be able to ping devices on both networks.
By default Network 2.x router will know about the 2.x network since it's a local network. In a typical linksys switch there will be a default gateway of last resort or what I referred to as 0.0.0.0 0.0.0.0 192.168.1 so the router running 2.x network should NOT need any additional static routes. One thing for the orignal poster is to confirm that when they set up the Linksys router with a 192.168.1.35 address he needs to configure the default gateway of 192.168.1.1. Maybe that was not done.
Now, in the VZ Router (1.x network), RIP is not needed but a static route is needed to point 192.168.2.0 255.255.255.0 to 192.168.1.35. I assume in the OP's example 192.168.1.35 is pointing to the WAN IP address of the Network 2.x router.
I have posted this topic on other networking forums but didn't get much help:
http://www.dslreports.com/forum/remark,28570109
http://www.tomshardware.com/answers/id-1772468/wan-lan-connection.html
when you say "One thing for the orignal poster is to confirm that when they set up the Linksys router with a 192.168.1.35 address he needs to configure the default gateway of 192.168.1.1. Maybe that was not done."
I'm not quite sure I'm following you there.
on my 192.168.1.0 network, 192.168.1.35 is set as a static IP for the router on 192.168.2.0. I believe I also tried setting up a static route in my linksys router to go to 192.168.1.0, but nothing has seemed to work yet.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here's some screenshots from my linksys router:
*note, the 'mode' below is only set to gateway so that I can browse the web and make this post while on my 2.X network, otherwise it would be on router.*
then I SSH'd to a linux box on my 192.168.1.X network to try and ping my client machine in my 192.168.2.X network:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your Gateway should be 192.168.1.1 not 192.168.2.0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actiontec has a Public WAN Address. The LAN Address is 192.168.1.1
This is pretty standard, default information.
In the Actiontec router under advanced à Routing I add 192.168.2.0 192.168.1.200 255.255.255.0
(192.168.1.200 is the IP address of my Linksys Router)
I have a Linksys Router connected on the Internet (WAN) and gave it IP address of 192.168.1.200 255.255.255.0 The LAN is 192.168.2.1
I changed the operating mode to router.
From the 192.168.2.x network I can ping any device on the 192.168.1.x network
From the 192.168.1.x network I can ping any device on the 192.168.2.x network
However I cannot get to the internet from 192.168.2.x and I believe this is where you are at:
Now what I did next was the following in the Actiontec Router go to:
System Monitoring, Advanced Status, Full Status / System wide Monitoring of connections
Click Network (home/office) then settings
At the bottom of that screen is a section called Additional IP Address
I added 192.168.2.1 255.255.255.0 (192.168.2.1 being the IP address of the Linksys IP address)
And now from 192.168.2.x network I can get on the internet and ping the devices on my 192.168.1.x network. I sent this to you from that network.
Let me know.
Jim
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, that woks great, albeit the Additional Ip Addresses is slightly different on a Westell.
Messed around for nearly an hour trying to get ping to work against devices on the secondary subnet and finally it occurred to me that maybe icmp was disabled on win7 machines. Enabled remote on one of them and ran rdp from the VZ subnet and immediately connected.
So it works fine with a Linksys router. All I have to do now is work out how to make it work with the Netgear and Dlink routers
Thanks Peter
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
much appreciation goes out to jumpin68ny for helping me out with this issue!
- « Previous
-
- 1
- 2
- Next »