NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX40 static route
I need to configure a static route to make 192.168.100.1 routeable from the local network. Where some routers can configure this to route to the upstream/internet interface, the RAX40 requires an IP ...
> I need to configure a static route to make 192.168.100.1 routeable
> from the local network. [...]
I don't know what that means.
General advice: You might have more success if you described the
actual problem which you are trying to solve, rather than asking how to
implement some particular "solution" ("configure a static route [...]")
which may have little or nothing to do with the actual problem (whatever
it might be).
Ok, I have a starlink dish with an ip of 192.168.100.1. I have an RAX40 connected to it. I need devices connected to the RAX40 on the 192.168.1.0/24 network to be able to route to 192.168.100.1 via the uplink interface.
> [...] I have a starlink dish [...]
Not a very detailed description of that device.
> [...] with an ip of 192.168.100.1. [...]
That's its LAN IP address? Why, exactly, are you trying to add the
RAX40 to your (unspecified) "a starlink dish"? Better wireless-network
coverage, or what?> [...] I need devices connected to the RAX40 on the 192.168.1.0/24
> network to be able to route to 192.168.100.1 via the uplink interface.
How did you configure the WAN/Internet interface on the RAX40?
If the WAN/Internet interface on the RAX40 is configured properly,
then devices on its LAN should use it as their default gateway, and you
shouldn't need to worry about routes.
If your (unspecified) "a starlink dish" includes a router (which,
given that "192.168.100.1" address, seems likely), then you might want
to configure the RAX40 as a wireless access point.Visit http://netgear.com/support , put in your model number, and look
for Documentation. Get the User Manual (at least). Read. Look for
"Set up the router as a WiFi access point".antinode wrote:
> [...] I have a starlink dish [...]
> Not a very detailed description of that device?.
SpaceX's Starlink is an internet provider. They use satilite dishes, so this is essentially my modem.
> [...] with an ip of 192.168.100.1. [...]
> That's its LAN IP address? Why, exactly, are you trying to add the
> RAX40 to your (unspecified) "a starlink dish"? Better wireless-network
> coverage, or what?Yes, 192.168.100.1 is the dish's IP.
I'm connecting it because I want internet access. I'm setting up the static route because I'd like to know when its obstructed, down and/or has no satillite.
> [...] I need devices connected to the RAX40 on the 192.168.1.0/24
> network to be able to route to 192.168.100.1 via the uplink interface.
> How did you configure the WAN/Internet interface on the RAX40?
Its DHCP so its just the defaults. All I've done on the entire RAX40 is SSID, password and the static route.
> If the WAN/Internet interface on the RAX40 is configured properly,
> then devices on its LAN should use it as their default gateway, and you
> shouldn't need to worry about routes.You're correct and the LAN is 192.168.1.1/24 so it ought to just work, yet it does not. Any ideas why?
> If your (unspecified) "a starlink dish" includes a router (which,
> given that "192.168.100.1" address, seems likely), then you might want
> to configure the RAX40 as a wireless access point.Unfortunately, the dish does not include a router. It had an external router, but it was slow and had no admin access.