This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
R8000P Static routing to ISP router for internet access.
Good day
I am struggling in setting up the Static routing for R8000P (Not sure if this would I need) I am not interested in using Access Point.
R1 = ISP provided router allows me to connect to Internet via its WAN port
Private IP network address: 192.200.1.0
Router Gateway address: 192.200.1.254
R2 = Netgear R8000P
Public IP address (WAN port) = 192.200.1.68
Private IP network address: 10.1.1.0
Router Gateway address: 10.1.1.2
I also have WiFI active on 2.4 and 5.0 G.
Moreover, I have a security camera connected to R2 and is operational. Unfortunately, I couldn't access the camera outside of my network and that's where I felt I may need to use the Static routing between R2 to R1 or vice versa.
So... my question regarding Static IP setup in R8000P.
What should I use for my destination IP ? would it be R2 public (WAN) IP address ?
What should I use for my Gateway IP ? would it be R2 Gateway address i.e. 10.1.1.2 or would it be R1 Gateway i.e. 192.200.1.254.
Re: R8000P Static routing to ISP router for internet access.
Router is a L3 (Layer 3) device and its job is to offer data traffic from one network to another. If they can't do that than to me they shouldn't be classified as Router to begin with.
Now to configuration part. If I have a subnetwork, it shouldn't be difficult to configure. Unfortunately, This problem is mainly associated with unmanaged routers. As NAT does the automatic Network translation and is restricted only to Class A, and Class B IP address scheme. That being said, the Class C IP address scheme is what used mostly for private networks and sub networks. This should be able to handled by having static routes with in the route.
Having sub-network is the way to Isolate the devices especially IoT (Internet of Things) devices. As they can easily get DOS attacks. Thus preventing other networks and devices to get compromised. And to communicate among the networks one need routers.
In my particular case, the issue was that my ISP router didn't have the route as stated in previous replies. And guess what as soon as I include the Routes, The devices started working.
Thank you all for your kind assistance and sharing wealth of knowledge.
Re: R8000P Static routing to ISP router for internet access.
Well I needed to know if I have configured the router correctly. Problem is that NAT doesn’t work with Class C IP address scheme. And is usually prescribed for Stub Router as is the case with ISP provided routers.
If so, it is a modem/router. So you are piling router on router,
Two routers on your network can cause headaches. For example, you can end up with local addressing problems. Among other things, the other router can misdirect addresses that the Netgear router usually handles, such as routerlogin.net or the usual IP address for a router, 192.168.1.1.
Unless you have specific reasons for using two routers – to create two separate networks for example – it is often easier to use just one router and then to set up the second router as a wifi access point. Netgear advises this, as does just about every site you will visit.
It may be possible to put the modem/router into modem only (bridge) mode and then to use the second device as the router. Sometimes it is easier to put the second router into AP mode. But that has its own drawbacks:
In your case, you said you didn't want to use the R8000P as an AP. But we still don't know why you want to set up "static routing", a concept that is often misunderstood.
From your message, a first move to fix the symptoms you describe would be to put the T3200 in bridge (modem only) mode.
Re: R8000P Static routing to ISP router for internet access.
Router is a L3 (Layer 3) device and its job is to offer data traffic from one network to another. If they can't do that than to me they shouldn't be classified as Router to begin with.
Now to configuration part. If I have a subnetwork, it shouldn't be difficult to configure. Unfortunately, This problem is mainly associated with unmanaged routers. As NAT does the automatic Network translation and is restricted only to Class A, and Class B IP address scheme. That being said, the Class C IP address scheme is what used mostly for private networks and sub networks. This should be able to handled by having static routes with in the route.
Having sub-network is the way to Isolate the devices especially IoT (Internet of Things) devices. As they can easily get DOS attacks. Thus preventing other networks and devices to get compromised. And to communicate among the networks one need routers.
In my particular case, the issue was that my ISP router didn't have the route as stated in previous replies. And guess what as soon as I include the Routes, The devices started working.
Thank you all for your kind assistance and sharing wealth of knowledge.
