NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LlamaLarry
Feb 17, 2021Luminary
Setting Static Route for Starlink
I live in a rural rea and just installed Starlink (yay), but seem to be having a problem setting the static route needed to access Dishy's statistics pages. Setup below:
ATT LTE ---|
|--> LB2120 in Bridge and with Failover (192.168.2.1) --> SRS60 (192.168.1.1)
Dishy (192.168.100.1) ---|
I tried the following route:
IP 192.168.100.0
Mask 255.255.255.0
Gateway 192.168.1.1
Metric 2
Can ping 192.168.100.1 and cannot access the webpages.
I am sure I am setting this up improperly, so i am hopeful someone will chime in.
I removed the LB2120 from the equation and the static route worked right away:
IP: 192.168.100.0
Mask: 255.255.255.0
Gateway: The IP assigned to the Orbi by the ISP
Metric: 2
15 Replies
Replies have been turned off for this discussion
- schumakuGuru - Experienced User
I would assume the Orbi Pro router would simply direct the traffic for that "other" subnet where the Dishy Web UI is located (confirm the mask is small there like 192.168.100.x/24 255.255.255.0) towards the Internet is (and so the Dishy admin address) ... no router required IMHO.
A simple traceroute or tracert to the 192.168.100.1 should show it goes out to the router on 192.168.1.1 to the WAN/Internet interface where the dishy is.
This should work just like the 192.168.5.1 to acess the LB2120 admin UI.
- LlamaLarryLuminary
This is what I see when I run traceroute fro my Mac to my LB2120:
traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 16.040 ms 2.043 ms 2.423 ms
2 192.168.2.1 (192.168.2.1) 4.517 ms 3.755 ms 3.133 msTrying to hit 192.168.100.1:
traceroute to 192.168.100.1 (192.168.100.1), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 5.806 ms 2.361 ms 2.448 ms
2 100.64.0.1 (100.64.0.1) 4.270 ms 7.671 ms 3.637 ms
3 * * *...
64 * * *
- schumakuGuru - Experienced User
Looks like the traffic goes into the ISP (the satellite one?) 100.64.0.1 - which is a carrier grade NAT (CGN) address (not a problem). Possibly the device does act different for a direct connected computer - I guess that's the only choice to access the dish box.
Related Content
- Apr 20, 2021Retired_Member
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!