NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Windows Access to my NAS with a Orbi - Cable Model setup
Looking for some help in correctly configuring my Orbi to access my NAS from a Windows PC. My Setup is ISP Cable Modem to my Orbi. My NAS is attached to my Cable modem I can access my NAS via...
> >> IP Address 192.168.0.14, Connection DHCP, IP Subnet Mask
> 255.255.255.0, [...]> >> 192.168.1.1, subnet 255.255.255.0, use router DHCP, starting .2
> ending .254.Ok. Your main (outer) router is using "192.168.0.*" for its LAN, and
the Orbi (inner router) is using "192.168.1.*" for its LAN.> >> found the option to assign a fixed IP.
Did you stick with the ".14" address, or choose something more
memorable? It's your choice. I'll assume ".14" here, but you could
pick another.Now all you need to do is find where/how to specify a static route on
your main router. The static route spec (on the main router) for this
situation should look something like this:
Destination IP Address: 192.168.1.0
IP Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.14You may also need to specify a "Metric". I'd pick "1", but on a
Netgear router, "2" might be as small as it lets you use. (Or your
Selligent, I know nothing.) With one extra route, it may matter little.An equivalent notation for "destination: 192.168.1.0, subnet mask:
255.255.255.0" would be "192.168.1.0/24".What that tells the main router is that a message with a destination
address of "192.168.1.x" (0 <= x <= 255) should be sent to
"192.168.0.14" (the Orbi WAN/Internet interface), instead of to its
usual default destination (your ISP).
The Orbi (inner router) doesn't need any special instruction,
because, by default, it sends anything foreign-looking out its
WAN/Internet interface, which goes to your main router. Your main
router already knows what to do with any destination on its own LAN
("192.168.0.*"), and anything else should be sent to your ISP.What could go wrong?
antinode wrote:> [...] What do I need to conifgure to put that in place?
Most of the configuration for that option is done on the main router
(the Selligent), about which I know nothing (which is about all I really
wanted to know about it).
Valuable preliminary data
> Model: RBR50|Orbi AC3000 Tri-band WiFi Router
RBR50 or RBR50v2? Look at the product label. We might as well both
be looking at the same/right User Manual. (Visit
http://netgear.com/support , put in your model number, and look for
Documentation. Get the User Manual.)>> It's the V2.
With the Orbi in router mode, what are its WAN/Internet IP
parameters? Look on the Orbi management web site at:
ADVANCED > ADVANCED Home : Internet Port>> IP Address 192.168.0.14, Connection DHCP, IP Subnet Mask 255.255.255.0, Domain Name Server 212.224.255.252
212.224.249.245
All those data might be interesting. (Copy+paste is your friend.) If
the main router has something like a Netgear "Attached Devices" report,
then the Orbi's WAN/Internet IP address should appear there, too. From
the point of view of the main router, that's just another LAN client IP
address. Like that of your NAS box, if it's also connected to the main
router.>> Correct, the Orbi & NAS are in the attached devices list of the main router. No other devices.
What are the Orbi's LAN IP parameters? Look on the Orbi management
web site at:
ADVANCED > Setup > LAN Setup : LAN TCP/IP Setup>> 192.168.1.1, subnet 255.255.255.0, use router DHCP, starting .2 ending .254.
On the main router, there are two major tasks.
1. Arrange for a fixed (main-router-LAN) IP address for the Orbi's
WAN/Internet interface. On a Netgear router, this would be handled at:
ADVANCED > Setup > LAN Setup : Address Reservation
On the Selligent, I know nothing. It might be under a topic like "DHCP
Server".>> found the option to assign a fixed IP.
2. Configure a static route on the main router, to tell it what to
send to the Orbi. Again, I don't know where to find that on the
Selligent. On a Netgear router, I'd expect to find it at:
ADVANCED > Advanced Setup > Static Routes
The details of how to specify that static route would be easier to
describe with all those "Valuable preliminary data", requested above.It probably sounds worse than it is. If you can find a link to a
decent user manual (in English) for the main router, then it might get a
little easier.
> >> IP Address 192.168.0.14, Connection DHCP, IP Subnet Mask
> 255.255.255.0, [...]
> >> 192.168.1.1, subnet 255.255.255.0, use router DHCP, starting .2
> ending .254.
Ok. Your main (outer) router is using "192.168.0.*" for its LAN, and
the Orbi (inner router) is using "192.168.1.*" for its LAN.
> >> found the option to assign a fixed IP.
Did you stick with the ".14" address, or choose something more
memorable? It's your choice. I'll assume ".14" here, but you could
pick another.
Now all you need to do is find where/how to specify a static route on
your main router. The static route spec (on the main router) for this
situation should look something like this:
Destination IP Address: 192.168.1.0
IP Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.14
You may also need to specify a "Metric". I'd pick "1", but on a
Netgear router, "2" might be as small as it lets you use. (Or your
Selligent, I know nothing.) With one extra route, it may matter little.
An equivalent notation for "destination: 192.168.1.0, subnet mask:
255.255.255.0" would be "192.168.1.0/24".
What that tells the main router is that a message with a destination
address of "192.168.1.x" (0 <= x <= 255) should be sent to
"192.168.0.14" (the Orbi WAN/Internet interface), instead of to its
usual default destination (your ISP).
The Orbi (inner router) doesn't need any special instruction,
because, by default, it sends anything foreign-looking out its
WAN/Internet interface, which goes to your main router. Your main
router already knows what to do with any destination on its own LAN
("192.168.0.*"), and anything else should be sent to your ISP.
What could go wrong?
Thank you a lot for your help & patience. One of life's mystery, how to set a satic ip route, is now solved :-). Hop to the next one :-)