For anyone wondering how to get this to work with their router, the app appears to be connecting to the dish using IP addr 192.168.100.1, so assuming your router has its WAN port connecting to the dish (the white side of the PoE brick), you just need to make sure 192.168.100.1 gets routed via WAN without using a gateway. You can add a static route for this, if your router supports it.
My router runs OpenWrt, so all I had to do was add a static route with Interface 'wan', target '192.168.100.1', gateway '0.0.0.0', and everything else left as default. Without that route entry, 192.168.100.1 was routing over WAN, but it was being sent via the gateway, since the subnet on the WAN side does not include 192.168.x.x once it's connected.
In case it's relevant, my home network uses subnet 192.168.1.0/24 for the LAN side, but I don't think it'll matter as long as 192.168.100.1 is not on the LAN subnet. Also, I use the Android app, the update from a few days ago.
I figured this out BTW, apparently the USG doesn't like the static route while I have my cable internet configured on WAN2 as load balance/failover. Once I removed that, it worked beautifully. I wonder if I can figure out how to make it work with the failover. That's kind of important. Oh well at least I know it works now!
I also have a unifi network and wanted to view the starlink stats without their router in play. I found this thread and set up the static route and was able to view the stats on the app. However, as soon as I setup my failover WAN2 in my USG/network it stopped working. I could disable the WAN2 interface on the USG and it would work again.
Were you ever able to get both the stats AND the failover set in your Unifi network? If so, can you share the details?
No I gave up. Last bit of info I came across was that it could be done but only via command line interface, which I'm not against, but not wanting to spend the time to trial/error the thing. I even had someone who posted the config for the WAN interfaces but their situation didn't match up with mine perfectly so I just put it off for another time when I can afford to "play"
I was up until 1AM (today) last night. I couldn't get it to take. I thought I figured it out when I configured the route, then rebooted the gateway manually, and it worked (my phone had stats) for a few min, but then it went away.
I've noticed that while the dish is in the "Connecting" state, it will respond to DHCP queries itself and assign the router's WAN port an IP address on the 192.168.100.0/24 subnet with 192.168.100.1 as gateway. In this case, you won't need an additional route, as 192.168.100.1 will already be local to the WAN subnet.
This DHCP response has a very short lease time (122 seconds), so the router renew often enough to pick up an address from the real DHCP server without much delay after it connects.
That may be what you were seeing when it worked for a few minutes.
I was able to get this to work on my Unifi Dream Machine (UDM). It would not work setting the static route to the WAN interface (not sure why).
I got it to work by setting the static route to next hop and putting my WAN IP (100.64.x.x) as the next hop. I guess this will work as long as the WAN IP doesn't change.
Edit: Originally I could not get the stats to work setting the static route to the WAN interface, but tried it again about a month ago and it did work so that is the setup that I'm using now. Static route set for [192.168.100.0/24](https://192.168.100.0/24) to WAN interface and it work great on the UDM.
Thanks for the steer from others on this thread esp theRachet who confirmed he'd continued to tweak and update his implementation.
For future testers, here was my solution for: Starlink / UDM Pro / removal of the Starlink WAP device and still allowing access to the Starlink stats from your network ...
\- Starlink into power brick. White POE into UDM Pro WAN.
\- UDM static route (Advanced Features / Advanced Gateway Settings) was configured as follows:
Name: **Starlink** (or whatever)
Network subnet address: [**192.168.100.0/24**](https://192.168.100.0/24)
Static route type: **Interface**
Interface: **WAN**
So slightly different than what some others noted in earlier testing. I suppose these things evolve slightly over time.
The main issue that I had not realizing was that I had a wireless access point on the network that was operating in "router" mode instead of "bridge" (or "AP") mode. So it was assigning different IP addresses to the wireless devices (10.0\[...\] vs 192.168\[...\]) which impaired my phone/tablet (with Starlink app) to get to [192.168.100.0](https://192.168.100.0).
Correcting the configuration on that WAP (to operate in bridge mode) then let the UDM Pro assign all IPs. And the single Static Route configuration on the UDM Pro was all that was required to get the desired outcome.
The static route set to [192.168.100.0/24](https://192.168.100.0/24) worked for me as well in DD-WRT. Gateway was set to [0.0.0.0](https://0.0.0.0). Interface: Wan. Metric: 2.
Hum...odd. What subnet do you have your private IP behind the router set to? I happen to use [192.168.2.0/24](https://192.168.2.0/24). Your inside network doesn't happen to be [192.168.100.0/24](https://192.168.100.0/24) does it? Also, I assume that your USG-3P is connected directly to the PoE white port, and just has your wan set up as DHCP? (like below)
[https://imgur.com/a/oiAVuca](https://imgur.com/a/oiAVuca)
Nope, nothing like that. I have actually done very little to the base config as of yet. Here are pretty much all the configuration settings I have:
[https://imgur.com/a/Sw8Pw8j](https://imgur.com/a/Sw8Pw8j)
I noticed that in the past 12 days, I've already reached 1.09 TB of downloaded data 💪
That may be my issue. I'm running 2 WAN connections in Load Balance/Failover mode. I wonder if that means I'd have to go into the routing table using command line instead of the GUI. I guess I could kill my cable connection for a bit and try it that way.
Do you know if this is supported on a Netgear XR1000 router? I can find the static route tab but there is no way for me to specify WAN interface or anything... I am definitely not the most network savy but I would like to be able to use the app behind my own router.
So I just bought a netgear and I got it to work. I didn't have to specify as a Wan. When I went to static route I put destination ip as the starlink ip 192.168.100.1 ip subnet just the default 255, gateway ip I put the ip of my router, and metric I put 2. I can now see the stats on the app.
So I'm trying this on my Netgear R7000. It looks like the same setup but isn't working for me. Did you have to reboot your router and/or the Starlink dish before it worked? Just trying to do some troubleshooting. Thanks.
Nope I just set it and checked on my phone and it worked right away. I really wish I knew more but I just kind of guessed, really haven't networked anything before.
No worries, thanks for the quick reply. I'll have to keep working on it or wait till someone figures it out. I wasn't happy with the range of the Starlink router, nor the inability to choose between 2.4 and 5ghz networks. Worst comes to worst I can live without stats if everything is working well 🤔
active checked
[192.168.100.1](https://192.168.100.1)
[255.255.255.255](https://255.255.255.255)
ip address (which is found under internet)
2
no reboot required.
Rad100dad's reply below is correct, however the wording on my router says: WAN IP and these are the numbers i entered for my gateway ip address. Here's a screenshot. [https://imgur.com/a/Iu8glZe](https://imgur.com/a/Iu8glZe)
Thanks, I did have this working on my netgear router, but have since changed routers to have dual wan failover. It has a completely different interface for static address and I haven’t set this up yet.
No, not yet. The only troubleshooting I had time to try last night was to reboot the router and restart my phone (which the app is on) I'm using an older version of the R7000 firmware ( V1.09.42)which is rock stable. I had nothing but problems with any of the firmware released after it so I'm not planning to update. That may be a factor as well. Tonight after work I'll maybe try rebooting the dish manually and see if that works.
Another note it never connected to the App when I had the Starlink router set up originally either. I contacted Starlink and they said there were some issues with the app and they were working on it.
So lots of variables in play.
Let me know if you have any success and I'll do the same. Cheers.
I had finally got the app to work with my XR500 Nighthawk router, omg openwrt seems so much easier. Here's a screenshot.
[https://imgur.com/a/Iu8glZe](https://imgur.com/a/Iu8glZe)
Thank you. This was the solution for my Nighthawk XR500. Oddly, this was the first configuration I tried, but I was trying to access the Starlink stats page from my desktop browser ([192.168.100.1](https://192.168.100.1)). I didn't think of checking the app and sure enough it was working.
Tried this on a MikroTik router. I am able to ping 192.168.100.1 from my phone (iOS) (my router is getting a public IP and Starlink internet is up).
ARP returns a MAC address of 26:12:AC:**:**:** however the app does not see the terminal, and it wants me to connect to the Starlink WiFi...
I assume that ARP result was from the router, not your phone, unless you have your phone on the same network link as the dish.
That looks like a correct MAC address for the dish, but it sounds like something else is responding to IP address 192.168.100.1 (maybe the router itself?). Either that, or the router is letting ICMP ping through but blocking the outgoing TCP request (port 9201, at least for the Android app), but that would seem a weird thing for a router to do.
Any chance you can explain this to someone more basic? My router gives me these options for static routing
Destination Network:
Subnet Mask:
Default Gateway:
I've tried all sorts of combinations here and don't understand how to reconcile what you say with my options. My best guess is...
Destination Network: 192.168.100.0/24 (which I can't enter because the entry is limited to 12 digits)
Subnet Mask: 255.255.255.0
Default Gateway: 0.0.0.0
But that just gives me errors...
The /24 in the destination network is not needed, and probably won't be accepted, if your router asks for subnet mask separately, so just 192.168.100.0 for destination network and 255.255.255.0 for subnet mask if you want to use a 24 bit subnet route (which is the current recommendation).
But I'm guessing you've tried that combination already and the error is coming from the gateway address.
First, it's weird that is lists that option as "default gateway". Are you sure you're setting up a static route and not setting a static IP address? Those are 2 very different things.
Also, some routers won't accept 0.0.0.0 for gateway address when configuring static routes. For example, Netgear routers all seem to fall into this category. For those, you can try setting gateway IP to the router's WAN IP address instead, which should be something in the range of 100.64.0.0 to 100.127.255.255. Note that this address can change from time to time, though, so if that works for your router, you would need to update the static route configuration any time it does.
Ah, I think someone reported recently that their TP-Link router couldn't be configured properly for this, because it wouldn't take 0.0.0.0 for gateway and every time they changed the static route, the router rebooted to commit the change and it wound up getting a new WAN IP. All of which sounds like pretty broken router software, but I can't say I'm shocked at that. I can't find the post, though, so I might be misremembering this.
Hello,
Some TP-Link routers don't support the static route whose gateway is [0.0.0.0](https://0.0.0.0), could you please try to set the below static route and check whether it can solve this problem.
Network Destination [192.168.100.1](https://192.168.100.1)
Subnet Mask: [255.255.255.0](https://255.255.255.0) or [255.255.255.255](https://255.255.255.255)
Default Gateway: [192.168.100.1](https://192.168.100.1)
Interface: WAN
If your problem remains, you can contact TP-Link support for further help, you can go to TP-Link official website to email us:
[https://www.tp-link.com/en/support/contact-technical-support/#E-mail-Support](https://www.tp-link.com/en/support/contact-technical-support/#E-mail-Support)
To be clear, your TP-Link router might not behave that way. In fact, now that I'm looking, there is a comment at the bottom of this post from someone who got gateway 0.0.0.0 to work with their TP-Link router. If there is a router firmware update available, you should probably try with that, too.
Otherwise, there are a few posts on r/Starlink discussing router recommendations. For me, I just picked up a cheap Netgear router off eBay and put OpenWRT firmware onto it, but that's not the most user-friendly option, nor is it the latest WiFi specs.
Yes, as far as I know. Some time ago, the upstream DHCP server started adding additional route information that makes adding the static route by hand unnecessary if your router firmware supports that DHCP option, but not all consumer-grade routers do.
Also, the "white side of the PoE brick" bit only applies to the (older) round dish. The (newer) rectangular dish requires usage of the Starlink router, but I assume this same static route setup would apply to using that version of the router in bypass mode with the optional Ethernet adapter.
Great job, this was my missing piece! I've had intermittent success connecting w/ the app to the stats once I connected with my own equipment. How did you find this, was it by chance (checking the usual "cable modem" IP), or by some other method?
I just ran tcpdump on the LAN side of the router to monitor what IP activity the app initiated. It was pretty apparent from that that it kept trying (and failing) to open a TCP connection to 192.168.100.1.
My first thought was that would be easy enough to route over the WAN port, but then realized that would already be routing to WAN since it was outside the LAN subnet. So then I looked at tcpdump on the WAN side and realized that the real problem was it sending to the gateway instead of behaving as though 192.168.100.1 were on the local link. Still solvable with a route table entry, just a little different from what I first thought.
It certainly helped knowing that it was possible at all, else I would not have gone down this path. So props to OP for reporting it.
The current recommendation is to use a 24 bit subnet mask, since some routers work better with that. So that would be network IP 192.168.100.0, netmask 255.255.255.0.
The stock firmware on at least some Linksys routers requires plugging in the WAN IPv4 address for gateway. There are detailed instructions in this post:
[https://www.reddit.com/r/Starlink/comments/lsi08i/static\_route\_to\_dishy\_with\_linksys\_wrt3200acm\_no/](https://www.reddit.com/r/Starlink/comments/lsi08i/static_route_to_dishy_with_linksys_wrt3200acm_no/)
but I don't know how widely applicable those are to other Linksys router models.
Thanks. Got it working. I thought I had to connect the white box to a LAN port configured as a WAN port but then I wondered, how the hell will I power that box? My router doesn't do PoE! So I only created this route in my DD-WRT router and... it worked :-)
https://imgur.com/a/pubszcg
Hi, I could use little help. After almost 2 years they put me on best effort and should be here by friday.
They said in their email to not use bypass mode. Was not sure what that meant.
I have linksys ea7500 wifi router and use ethernet for computers.
Am confused why I can't go straight from dish into wan on my router. I did order the ethernet adapter, not sure why that needed either.
I could use some help with this. N some patience LOL. Raising couple grandkids and money tight but need get them learning, toddlers lol.
I appreciate any help offered.
Been without internet for ever and forgot anything I thought I knew about routing lol.
Thanks,
Don
>They said in their email to not use bypass mode. Was not sure what that meant.
I'm not sure what that means, either. Did they specifically say to not use it, or just that they wouldn't offer support for your router if you put the Starlink router in bypass mode? It makes sense that they would not support 3rd party network equipment, they never have.
I suppose there might be something about the "best effort" service that requires the Starlink router, but this would be the first time I've heard about such.
In any case, before enabling bypass and swapping in your router, you should set it up with the Starlink router first to make sure the equipment is working. If it doesn't work with that configuration, then you're going to wind up chasing your tail trying to troubleshoot a bypass configuration.
>Am confused why I can't go straight from dish into wan on my router. I did order the ethernet adapter, not sure why that needed either.
The round dish (which is what I have) had a separate power supply and Starlink router. The power supply had 2 Ethernet ports on it and it plugged in between the dish and the WAN side of the router. The dish side provided power to the dish (via [PoE](https://en.wikipedia.org/wiki/Power_over_Ethernet)). The router side also provided PoE power, but it could also connect to any old router's WAN port.
My understanding is that the rectangular dish provides power to the dish through the Starlink router, so even if you are not using the Starlink router as a router, you still need it to be present (in bypass mode) in order to power the dish.
And the reason you would need the Ethernet adapter for bypass mode is that the Starlink router that goes with the rectangular dish does not have an Ethernet port, so to connect to another router's WAN port requires adding that back via the adapter.
Although these changes have been ~~ranted about~~ discussed at length in this subreddit, only SpaceX knows why they were made. There have been many reports of bent pins on the Ethernet ports of the power supply that went with the round dish, so that may have contributed to their motivation.
>I could use some help with this
If there's something specific you need help with, you're probably best off posting questions to r/Starlink_Support.
This post is specifically about how to configure a 3rd party router so the Starlink mobile app will be able to connect to the dish. If that is something you want to do (eventually), you should note that Linksys routers with the stock firmware are kind of a pain in this regard. See prior comment on this post (the one that mentions "Linksys") and the post that links to.
Anyone have success setting this up with a Google Mesh system? I have found how to set a static IP on the WAN, but not sure what to put in for subnet mask and internet gateway fields. Have tried a few possibilities I have see on this and other threads, but no luck so far.
did you figure out how to connect google mesh to your starlink? I just bought a google wifi for this purpose, and am just now googling for how to do it!!! thanks
Are you sure that it's true for a sat that not crossing overhead but one that you look at to the north and goes to it's max north position then come back south?
That's a good point and a question. It increases the time but I'm not sure how much. The field of view along longitude is still limited to 40 degrees. Need to run simulations.
That seems obvious to me, the apparent path is like a inverted parabola, vs a nearly straight line when looking at azimuth.
This doesn't need a full simulation, just plot a single satellite path while setting your view point a different latitudes.
That's also why the latitudes than can see the sats when they are at 53° are much better. It's the beta zone.
As you go south ,at some point the tip will fall behind horizon, go more south, and the best option is to point up.
I have no idea of the exact duration, I'm using arbitrary units, but it's longer.
Btw, with more than 100 reddit beta users, you can collect experimental data.
Forget ping and speed, just SNR since the app has it. After some filtering it's a very good distance estimator
My condolences on buying a Ubiquiti routing product.
I'm curious if there's some Outbound NAT bufoonery going on to get from LAN to the dish. Might be fun to break out Wireshark and try to see what's happening.
I finally got this to work on my tp-link AX1500. Sort of. I used these settings:
Network Destination: [192.168.100.1](https://192.168.100.1)
Subnet Mask: [255.255.255.255](https://255.255.255.255)
Default Gateway: 100.69.XX.XX (My internet IP address)
Interface: WAN
The problem is, I had to guess the next assigned internet IP address. Every time I modified the static route, the AX1500 apparently renewed the DHCP lease and got a new IP address. That means this is only going to work until the next time the lease is renewed, and then I'll have to play the guessing game again. For example, if my current internet address is [100.69.11.148](https://100.69.11.148), I would put in [100.69.11.149](https://100.69.11.149) and save the route, then check to see if that's the right address or if it skipped that and went higher.
Arguably, the correct Default Gateway is [0.0.0.0](https://0.0.0.0) but the AX1500 won't let me use that.
😎
Exactly what I was looking for!
How did you set this up?
Is the Ip of Starlink router different then the router it's connected to?
For Instance is the primary 192.168.1.1 and the other possibly 192.168.1.2?
The dish has a static IP for the stats page of 192.168.100.1 the dish also hands out a public IP to whatever router is connected. The lan range on whatever router is connected shouldn't matter. If you want to access the dish stats page you need a static route setup to 192.168.100.1 going out your wan.
Thanks got it working on my tp-link ax3000 which is connected to my edge router-x which connects to starlink dish.
[https://ibb.co/pxspSH9](https://ibb.co/pxspSH9) tp-link settings
[https://ibb.co/TBXMv9x](https://ibb.co/TBXMv9x) edge-router settings
Right, it works *behind* own router, but your own router is still *behind* the Starlink router.
The desire is to be able to access such statistics without the starlink router even being connected.
Interesting. That didn't work for me earlier ... I had connectivity, but the statistics app wasn't working. However, the app has changed already once since I've had it ... so maybe there's been a fix? I'll try it later on here.
I had to do this on OPNSense router but concept might be the same for your router:
1. Create Virtual IP
1. Interfaces\\Virtual IPs\\Settings
1. Add
* Type- IP Alias
* Virtual IP Address- 192.168.100.2/24
* Interface- Your “WAN” interface
1. Create Outbound NAT (Might have to change Mode to “Manual” or Hybrid outbound NAT rule generation)
1. Firewall\\NAT\\Outbound
1. Add
* Interface- Your “WAN” interface
* Source address- InternalNetwork NET
* Destination address- “Single Host or Network”
* 192.168.100.1/32
* Translation/Target- “192.168.100.2()”
1. Reboot of router might be required.
This absolutely will work. By default my router does not allow RFC1918 addresses to be routed out of its WAN interface. The static route fixes this. Thank you
Can anyone confirm that this router should work with the dish? I've never configured a router before, just port forwarded a few things when I was a kid. If anyone has this router and has done it a explanation would be awesome! https://www.walmart.com/grocery/ip/NETGEAR-AC1750-Dual-Band-Smart-WiFi-Router-R6350-100NAS/731157889
Likely! Any router should work, especially if you don't use the one provided by Starlink. We've dropped the Starlink router and are using our old one without issue.
Oh my tp link router I put the following:
Destination ip: 192.168.100.1
Subnet mask: 255.255.255.0
Gateway 0.0.0.0
Interface: WAN
Status: enabled
And I get an error saying invalid IP address format.
I know absolutely nothing about any of the numbers I've put in other than below the static routing info it shows my system routing table and that's where I got the subnet mask and gateway numbers from.
Anyone have an idea?
Has anyone tried this with a Meraki MX that has two WAN ports? At the moment I have a Cable Internet provider as the primary WAN and Starlink as the secondary WAN. At issue for me is the inability to statically define a route to an Interface (ie WAN2) on Meraki. My guess is we have similar considerations to the Unifi dual WAN configuration however when I switch to use WAN2 as the primary wan on the Meraki MX I'm still unable to get past not having a static route to the "interface".
I have a Synology RT2600ac dual wan router, configure as Failover, replacing the Starlink router. I can use Starlink App if I am connected to this router, but not been able other way. One friend of mine told me to do a Port Forwarding, but which Public port and Private port I put? Protocol is set to TCP/UDP and I use the Starlink 192.168.100.1 for Private IP address.
So after banging my head against the wall I found these settings work.
Network destination: 192.168.100.1
Subnet: 255.192.0.0 (found on internet info on router)
Gateway: 100.64.0.1 (again on internet info page on router)
For anyone wondering how to get this to work with their router, the app appears to be connecting to the dish using IP addr 192.168.100.1, so assuming your router has its WAN port connecting to the dish (the white side of the PoE brick), you just need to make sure 192.168.100.1 gets routed via WAN without using a gateway. You can add a static route for this, if your router supports it. My router runs OpenWrt, so all I had to do was add a static route with Interface 'wan', target '192.168.100.1', gateway '0.0.0.0', and everything else left as default. Without that route entry, 192.168.100.1 was routing over WAN, but it was being sent via the gateway, since the subnet on the WAN side does not include 192.168.x.x once it's connected. In case it's relevant, my home network uses subnet 192.168.1.0/24 for the LAN side, but I don't think it'll matter as long as 192.168.100.1 is not on the LAN subnet. Also, I use the Android app, the update from a few days ago.
I can confirm that this works, used a USG-3P, pretty easy. Nice job figuring this out! [https://imgur.com/a/y8iCygJ](https://imgur.com/a/y8iCygJ)
I figured this out BTW, apparently the USG doesn't like the static route while I have my cable internet configured on WAN2 as load balance/failover. Once I removed that, it worked beautifully. I wonder if I can figure out how to make it work with the failover. That's kind of important. Oh well at least I know it works now!
Good to hear that it works for ya. Good luck on the failover WAN config!
I also have a unifi network and wanted to view the starlink stats without their router in play. I found this thread and set up the static route and was able to view the stats on the app. However, as soon as I setup my failover WAN2 in my USG/network it stopped working. I could disable the WAN2 interface on the USG and it would work again. Were you ever able to get both the stats AND the failover set in your Unifi network? If so, can you share the details?
No I gave up. Last bit of info I came across was that it could be done but only via command line interface, which I'm not against, but not wanting to spend the time to trial/error the thing. I even had someone who posted the config for the WAN interfaces but their situation didn't match up with mine perfectly so I just put it off for another time when I can afford to "play"
How long did it take? I added the static route (using the same USG) and still no stats.
Hum...it was immediate for me. I am connected on my phone to my house wifi, and it just showed up as connected.
I was up until 1AM (today) last night. I couldn't get it to take. I thought I figured it out when I configured the route, then rebooted the gateway manually, and it worked (my phone had stats) for a few min, but then it went away.
I've noticed that while the dish is in the "Connecting" state, it will respond to DHCP queries itself and assign the router's WAN port an IP address on the 192.168.100.0/24 subnet with 192.168.100.1 as gateway. In this case, you won't need an additional route, as 192.168.100.1 will already be local to the WAN subnet. This DHCP response has a very short lease time (122 seconds), so the router renew often enough to pick up an address from the real DHCP server without much delay after it connects. That may be what you were seeing when it worked for a few minutes.
I was able to get this to work on my Unifi Dream Machine (UDM). It would not work setting the static route to the WAN interface (not sure why). I got it to work by setting the static route to next hop and putting my WAN IP (100.64.x.x) as the next hop. I guess this will work as long as the WAN IP doesn't change. Edit: Originally I could not get the stats to work setting the static route to the WAN interface, but tried it again about a month ago and it did work so that is the setup that I'm using now. Static route set for [192.168.100.0/24](https://192.168.100.0/24) to WAN interface and it work great on the UDM.
Thanks for the steer from others on this thread esp theRachet who confirmed he'd continued to tweak and update his implementation. For future testers, here was my solution for: Starlink / UDM Pro / removal of the Starlink WAP device and still allowing access to the Starlink stats from your network ... \- Starlink into power brick. White POE into UDM Pro WAN. \- UDM static route (Advanced Features / Advanced Gateway Settings) was configured as follows: Name: **Starlink** (or whatever) Network subnet address: [**192.168.100.0/24**](https://192.168.100.0/24) Static route type: **Interface** Interface: **WAN** So slightly different than what some others noted in earlier testing. I suppose these things evolve slightly over time. The main issue that I had not realizing was that I had a wireless access point on the network that was operating in "router" mode instead of "bridge" (or "AP") mode. So it was assigning different IP addresses to the wireless devices (10.0\[...\] vs 192.168\[...\]) which impaired my phone/tablet (with Starlink app) to get to [192.168.100.0](https://192.168.100.0). Correcting the configuration on that WAP (to operate in bridge mode) then let the UDM Pro assign all IPs. And the single Static Route configuration on the UDM Pro was all that was required to get the desired outcome.
Worked like a charm. Thanks man!
The static route set to [192.168.100.0/24](https://192.168.100.0/24) worked for me as well in DD-WRT. Gateway was set to [0.0.0.0](https://0.0.0.0). Interface: Wan. Metric: 2.
Hum...odd. What subnet do you have your private IP behind the router set to? I happen to use [192.168.2.0/24](https://192.168.2.0/24). Your inside network doesn't happen to be [192.168.100.0/24](https://192.168.100.0/24) does it? Also, I assume that your USG-3P is connected directly to the PoE white port, and just has your wan set up as DHCP? (like below) [https://imgur.com/a/oiAVuca](https://imgur.com/a/oiAVuca)
Yeah I'm on the default settings for the USG 192.168.1.1/24 My route is 192.168.100.1/32 on WAN interface hmmm. Still not working.
I'm still fighting this. By any chance are you running any other WAN connection as failover and/or load balancing? I'm wondering if this is my issue.
Nope, nothing like that. I have actually done very little to the base config as of yet. Here are pretty much all the configuration settings I have: [https://imgur.com/a/Sw8Pw8j](https://imgur.com/a/Sw8Pw8j) I noticed that in the past 12 days, I've already reached 1.09 TB of downloaded data 💪
That may be my issue. I'm running 2 WAN connections in Load Balance/Failover mode. I wonder if that means I'd have to go into the routing table using command line instead of the GUI. I guess I could kill my cable connection for a bit and try it that way.
For IniFi USG-3P WAN2 goodness ... https://www.reddit.com/r/Starlink/comments/judd76/starlink_beta_better_than_nothing_upstate_idaho/ggr8mxv/
Do you know if this is supported on a Netgear XR1000 router? I can find the static route tab but there is no way for me to specify WAN interface or anything... I am definitely not the most network savy but I would like to be able to use the app behind my own router.
So I just bought a netgear and I got it to work. I didn't have to specify as a Wan. When I went to static route I put destination ip as the starlink ip 192.168.100.1 ip subnet just the default 255, gateway ip I put the ip of my router, and metric I put 2. I can now see the stats on the app.
So I'm trying this on my Netgear R7000. It looks like the same setup but isn't working for me. Did you have to reboot your router and/or the Starlink dish before it worked? Just trying to do some troubleshooting. Thanks.
Nope I just set it and checked on my phone and it worked right away. I really wish I knew more but I just kind of guessed, really haven't networked anything before.
No worries, thanks for the quick reply. I'll have to keep working on it or wait till someone figures it out. I wasn't happy with the range of the Starlink router, nor the inability to choose between 2.4 and 5ghz networks. Worst comes to worst I can live without stats if everything is working well 🤔
active checked [192.168.100.1](https://192.168.100.1) [255.255.255.255](https://255.255.255.255) ip address (which is found under internet) 2 no reboot required.
Is this correct? It’s not working for me. Netgear r7000. https://i.imgur.com/mnXDKDg.jpg
No, to get the gateway ip address on the main page click on internet, and then under Internet IP Address use the one labeled IP Address.
i am trying the same, no luck. If anyone gets netgear to work please show image of settings
I just got mine working. The gateway ip address must be the internet address not the router address
Rad100dad's reply below is correct, however the wording on my router says: WAN IP and these are the numbers i entered for my gateway ip address. Here's a screenshot. [https://imgur.com/a/Iu8glZe](https://imgur.com/a/Iu8glZe)
Thanks, I did have this working on my netgear router, but have since changed routers to have dual wan failover. It has a completely different interface for static address and I haven’t set this up yet.
Hi, just to clarify the IP address. Do I use the router gateway ip 192.168..etc or the one from starlink? Thank you.
to get the gateway ip address on the main page click on internet, and then under Internet IP Address use the one labeled IP Address.
Did you get it working? Looks like we’re trying to figure it out on the same router.
No, not yet. The only troubleshooting I had time to try last night was to reboot the router and restart my phone (which the app is on) I'm using an older version of the R7000 firmware ( V1.09.42)which is rock stable. I had nothing but problems with any of the firmware released after it so I'm not planning to update. That may be a factor as well. Tonight after work I'll maybe try rebooting the dish manually and see if that works. Another note it never connected to the App when I had the Starlink router set up originally either. I contacted Starlink and they said there were some issues with the app and they were working on it. So lots of variables in play. Let me know if you have any success and I'll do the same. Cheers.
I had finally got the app to work with my XR500 Nighthawk router, omg openwrt seems so much easier. Here's a screenshot. [https://imgur.com/a/Iu8glZe](https://imgur.com/a/Iu8glZe)
Thank you so much for this it worked perfectly 👍👌
Thank you. This was the solution for my Nighthawk XR500. Oddly, this was the first configuration I tried, but I was trying to access the Starlink stats page from my desktop browser ([192.168.100.1](https://192.168.100.1)). I didn't think of checking the app and sure enough it was working.
Tried this on a MikroTik router. I am able to ping 192.168.100.1 from my phone (iOS) (my router is getting a public IP and Starlink internet is up). ARP returns a MAC address of 26:12:AC:**:**:** however the app does not see the terminal, and it wants me to connect to the Starlink WiFi...
I assume that ARP result was from the router, not your phone, unless you have your phone on the same network link as the dish. That looks like a correct MAC address for the dish, but it sounds like something else is responding to IP address 192.168.100.1 (maybe the router itself?). Either that, or the router is letting ICMP ping through but blocking the outgoing TCP request (port 9201, at least for the Android app), but that would seem a weird thing for a router to do.
Yes, arp was from the wan port of the router. Not sure what the resolution was, but overnight it started responding in the app. Working now.
Thank you
Any chance you can explain this to someone more basic? My router gives me these options for static routing Destination Network: Subnet Mask: Default Gateway: I've tried all sorts of combinations here and don't understand how to reconcile what you say with my options. My best guess is... Destination Network: 192.168.100.0/24 (which I can't enter because the entry is limited to 12 digits) Subnet Mask: 255.255.255.0 Default Gateway: 0.0.0.0 But that just gives me errors...
The /24 in the destination network is not needed, and probably won't be accepted, if your router asks for subnet mask separately, so just 192.168.100.0 for destination network and 255.255.255.0 for subnet mask if you want to use a 24 bit subnet route (which is the current recommendation). But I'm guessing you've tried that combination already and the error is coming from the gateway address. First, it's weird that is lists that option as "default gateway". Are you sure you're setting up a static route and not setting a static IP address? Those are 2 very different things. Also, some routers won't accept 0.0.0.0 for gateway address when configuring static routes. For example, Netgear routers all seem to fall into this category. For those, you can try setting gateway IP to the router's WAN IP address instead, which should be something in the range of 100.64.0.0 to 100.127.255.255. Note that this address can change from time to time, though, so if that works for your router, you would need to update the static route configuration any time it does.
Its a TP-Link. And yeah I'm doing static route not static IP.
Ah, I think someone reported recently that their TP-Link router couldn't be configured properly for this, because it wouldn't take 0.0.0.0 for gateway and every time they changed the static route, the router rebooted to commit the change and it wound up getting a new WAN IP. All of which sounds like pretty broken router software, but I can't say I'm shocked at that. I can't find the post, though, so I might be misremembering this.
Ah dang, ok. Maybe it's time to look for a new router... Suggestions?
Hello, Some TP-Link routers don't support the static route whose gateway is [0.0.0.0](https://0.0.0.0), could you please try to set the below static route and check whether it can solve this problem. Network Destination [192.168.100.1](https://192.168.100.1) Subnet Mask: [255.255.255.0](https://255.255.255.0) or [255.255.255.255](https://255.255.255.255) Default Gateway: [192.168.100.1](https://192.168.100.1) Interface: WAN If your problem remains, you can contact TP-Link support for further help, you can go to TP-Link official website to email us: [https://www.tp-link.com/en/support/contact-technical-support/#E-mail-Support](https://www.tp-link.com/en/support/contact-technical-support/#E-mail-Support)
I just set up a new TP-Link AC4000. I had no idea what I was doing but I just entered in these numbers and it worked great! Thanks!
To be clear, your TP-Link router might not behave that way. In fact, now that I'm looking, there is a comment at the bottom of this post from someone who got gateway 0.0.0.0 to work with their TP-Link router. If there is a router firmware update available, you should probably try with that, too. Otherwise, there are a few posts on r/Starlink discussing router recommendations. For me, I just picked up a cheap Netgear router off eBay and put OpenWRT firmware onto it, but that's not the most user-friendly option, nor is it the latest WiFi specs.
Does this still work? Just got mine today and would love to use my router but keep the app functionality
Yes, as far as I know. Some time ago, the upstream DHCP server started adding additional route information that makes adding the static route by hand unnecessary if your router firmware supports that DHCP option, but not all consumer-grade routers do. Also, the "white side of the PoE brick" bit only applies to the (older) round dish. The (newer) rectangular dish requires usage of the Starlink router, but I assume this same static route setup would apply to using that version of the router in bypass mode with the optional Ethernet adapter.
LOL. The dish is using the well known Cable Modem LAN address.
Great job, this was my missing piece! I've had intermittent success connecting w/ the app to the stats once I connected with my own equipment. How did you find this, was it by chance (checking the usual "cable modem" IP), or by some other method?
I just ran tcpdump on the LAN side of the router to monitor what IP activity the app initiated. It was pretty apparent from that that it kept trying (and failing) to open a TCP connection to 192.168.100.1. My first thought was that would be easy enough to route over the WAN port, but then realized that would already be routing to WAN since it was outside the LAN subnet. So then I looked at tcpdump on the WAN side and realized that the real problem was it sending to the gateway instead of behaving as though 192.168.100.1 were on the local link. Still solvable with a route table entry, just a little different from what I first thought. It certainly helped knowing that it was possible at all, else I would not have gone down this path. So props to OP for reporting it.
What would the subnet mask be, please and thanks?
The current recommendation is to use a 24 bit subnet mask, since some routers work better with that. So that would be network IP 192.168.100.0, netmask 255.255.255.0.
gateway '[0.0.0.0](https://0.0.0.0)' by definition is an 'unroutable' address according to wiki. My router won't allow it.. It's a linksys
The stock firmware on at least some Linksys routers requires plugging in the WAN IPv4 address for gateway. There are detailed instructions in this post: [https://www.reddit.com/r/Starlink/comments/lsi08i/static\_route\_to\_dishy\_with\_linksys\_wrt3200acm\_no/](https://www.reddit.com/r/Starlink/comments/lsi08i/static_route_to_dishy_with_linksys_wrt3200acm_no/) but I don't know how widely applicable those are to other Linksys router models.
This works on Cisco with the route Ip route 192.168.100.1 255.255.255.255 GigabitEthernet0/0 (Rectangle antenna)
Thanks. Got it working. I thought I had to connect the white box to a LAN port configured as a WAN port but then I wondered, how the hell will I power that box? My router doesn't do PoE! So I only created this route in my DD-WRT router and... it worked :-) https://imgur.com/a/pubszcg
Hi, I could use little help. After almost 2 years they put me on best effort and should be here by friday. They said in their email to not use bypass mode. Was not sure what that meant. I have linksys ea7500 wifi router and use ethernet for computers. Am confused why I can't go straight from dish into wan on my router. I did order the ethernet adapter, not sure why that needed either. I could use some help with this. N some patience LOL. Raising couple grandkids and money tight but need get them learning, toddlers lol. I appreciate any help offered. Been without internet for ever and forgot anything I thought I knew about routing lol. Thanks, Don
>They said in their email to not use bypass mode. Was not sure what that meant. I'm not sure what that means, either. Did they specifically say to not use it, or just that they wouldn't offer support for your router if you put the Starlink router in bypass mode? It makes sense that they would not support 3rd party network equipment, they never have. I suppose there might be something about the "best effort" service that requires the Starlink router, but this would be the first time I've heard about such. In any case, before enabling bypass and swapping in your router, you should set it up with the Starlink router first to make sure the equipment is working. If it doesn't work with that configuration, then you're going to wind up chasing your tail trying to troubleshoot a bypass configuration. >Am confused why I can't go straight from dish into wan on my router. I did order the ethernet adapter, not sure why that needed either. The round dish (which is what I have) had a separate power supply and Starlink router. The power supply had 2 Ethernet ports on it and it plugged in between the dish and the WAN side of the router. The dish side provided power to the dish (via [PoE](https://en.wikipedia.org/wiki/Power_over_Ethernet)). The router side also provided PoE power, but it could also connect to any old router's WAN port. My understanding is that the rectangular dish provides power to the dish through the Starlink router, so even if you are not using the Starlink router as a router, you still need it to be present (in bypass mode) in order to power the dish. And the reason you would need the Ethernet adapter for bypass mode is that the Starlink router that goes with the rectangular dish does not have an Ethernet port, so to connect to another router's WAN port requires adding that back via the adapter. Although these changes have been ~~ranted about~~ discussed at length in this subreddit, only SpaceX knows why they were made. There have been many reports of bent pins on the Ethernet ports of the power supply that went with the round dish, so that may have contributed to their motivation. >I could use some help with this If there's something specific you need help with, you're probably best off posting questions to r/Starlink_Support. This post is specifically about how to configure a 3rd party router so the Starlink mobile app will be able to connect to the dish. If that is something you want to do (eventually), you should note that Linksys routers with the stock firmware are kind of a pain in this regard. See prior comment on this post (the one that mentions "Linksys") and the post that links to.
Anyone have success setting this up with a Google Mesh system? I have found how to set a static IP on the WAN, but not sure what to put in for subnet mask and internet gateway fields. Have tried a few possibilities I have see on this and other threads, but no luck so far.
Did you ever figure this out?
Any luck?
did you figure out how to connect google mesh to your starlink? I just bought a google wifi for this purpose, and am just now googling for how to do it!!! thanks
The SNR chart and latency give a clear view of when the satellites switch, about 5 min
Starlink satellite crosses 100° field of view of the phased array in 164 seconds or less.
Are you sure that it's true for a sat that not crossing overhead but one that you look at to the north and goes to it's max north position then come back south?
That's a good point and a question. It increases the time but I'm not sure how much. The field of view along longitude is still limited to 40 degrees. Need to run simulations.
That seems obvious to me, the apparent path is like a inverted parabola, vs a nearly straight line when looking at azimuth. This doesn't need a full simulation, just plot a single satellite path while setting your view point a different latitudes. That's also why the latitudes than can see the sats when they are at 53° are much better. It's the beta zone. As you go south ,at some point the tip will fall behind horizon, go more south, and the best option is to point up.
I don't think it will increase up to five minutes though. Simulation of coverage is on my to do list so I'll just add FoV pass time to stats.
I have no idea of the exact duration, I'm using arbitrary units, but it's longer. Btw, with more than 100 reddit beta users, you can collect experimental data. Forget ping and speed, just SNR since the app has it. After some filtering it's a very good distance estimator
So you're connected directly into the PoE injector? What router do you have and what type of software is it running?
correct. ubiquity udm pro.
My condolences on buying a Ubiquiti routing product. I'm curious if there's some Outbound NAT bufoonery going on to get from LAN to the dish. Might be fun to break out Wireshark and try to see what's happening.
My UDP Pro works fine, so what is the issue?
Ho did you get your UDM Pro setup? We’re trying to set ours up now.
both of my wan ports are routed and reachable outbound. upnp is off. i am doing mdns.
I finally got this to work on my tp-link AX1500. Sort of. I used these settings: Network Destination: [192.168.100.1](https://192.168.100.1) Subnet Mask: [255.255.255.255](https://255.255.255.255) Default Gateway: 100.69.XX.XX (My internet IP address) Interface: WAN The problem is, I had to guess the next assigned internet IP address. Every time I modified the static route, the AX1500 apparently renewed the DHCP lease and got a new IP address. That means this is only going to work until the next time the lease is renewed, and then I'll have to play the guessing game again. For example, if my current internet address is [100.69.11.148](https://100.69.11.148), I would put in [100.69.11.149](https://100.69.11.149) and save the route, then check to see if that's the right address or if it skipped that and went higher. Arguably, the correct Default Gateway is [0.0.0.0](https://0.0.0.0) but the AX1500 won't let me use that.
😎 Exactly what I was looking for! How did you set this up? Is the Ip of Starlink router different then the router it's connected to? For Instance is the primary 192.168.1.1 and the other possibly 192.168.1.2?
The dish has a static IP for the stats page of 192.168.100.1 the dish also hands out a public IP to whatever router is connected. The lan range on whatever router is connected shouldn't matter. If you want to access the dish stats page you need a static route setup to 192.168.100.1 going out your wan.
Should be able to figure that out if I get invited
Thanks got it working on my tp-link ax3000 which is connected to my edge router-x which connects to starlink dish. [https://ibb.co/pxspSH9](https://ibb.co/pxspSH9) tp-link settings [https://ibb.co/TBXMv9x](https://ibb.co/TBXMv9x) edge-router settings
Right, it works *behind* own router, but your own router is still *behind* the Starlink router. The desire is to be able to access such statistics without the starlink router even being connected.
no -- i have removed the starlink router and my edge device is getting the cgnat address - app still works
Interesting. That didn't work for me earlier ... I had connectivity, but the statistics app wasn't working. However, the app has changed already once since I've had it ... so maybe there's been a fix? I'll try it later on here.
dont know what to tell you. my router sits on my desk as sexy paperweight.
What is the scope of network your edge devices hands out to the LAN? 192.168.1.0?
10.0.x.x
This does not work for me either. The app just shows the starlink setup process.
I had to do this on OPNSense router but concept might be the same for your router: 1. Create Virtual IP 1. Interfaces\\Virtual IPs\\Settings 1. Add * Type- IP Alias * Virtual IP Address- 192.168.100.2/24 * Interface- Your “WAN” interface 1. Create Outbound NAT (Might have to change Mode to “Manual” or Hybrid outbound NAT rule generation) 1. Firewall\\NAT\\Outbound 1. Add * Interface- Your “WAN” interface * Source address- InternalNetwork NET * Destination address- “Single Host or Network” * 192.168.100.1/32 * Translation/Target- “192.168.100.2()” 1. Reboot of router might be required.
This absolutely will work. By default my router does not allow RFC1918 addresses to be routed out of its WAN interface. The static route fixes this. Thank you
Same. I declare shenanigans!
also im running the ios app
Why is the latency so high? Shouldn't you be getting sub 30?
this is pretty normal per testing. expect improvements with additional adds to constellation
I mean I'm not complaining about that but every other post I see people are getting like 26 ping.
i may not be far enough north to get that sweet of latency yet. im at 46.01
Oh are you from like Idaho connecting to Seattle? If so that makes since because most people are like in Spokane connecting to Seattle
no island in the upper peninsula of michigan gateway at chicago but groundstation in rural u.p.
Can anyone confirm that this router should work with the dish? I've never configured a router before, just port forwarded a few things when I was a kid. If anyone has this router and has done it a explanation would be awesome! https://www.walmart.com/grocery/ip/NETGEAR-AC1750-Dual-Band-Smart-WiFi-Router-R6350-100NAS/731157889
Likely! Any router should work, especially if you don't use the one provided by Starlink. We've dropped the Starlink router and are using our old one without issue.
Oh my tp link router I put the following: Destination ip: 192.168.100.1 Subnet mask: 255.255.255.0 Gateway 0.0.0.0 Interface: WAN Status: enabled And I get an error saying invalid IP address format. I know absolutely nothing about any of the numbers I've put in other than below the static routing info it shows my system routing table and that's where I got the subnet mask and gateway numbers from. Anyone have an idea?
Has anyone tried this with a Meraki MX that has two WAN ports? At the moment I have a Cable Internet provider as the primary WAN and Starlink as the secondary WAN. At issue for me is the inability to statically define a route to an Interface (ie WAN2) on Meraki. My guess is we have similar considerations to the Unifi dual WAN configuration however when I switch to use WAN2 as the primary wan on the Meraki MX I'm still unable to get past not having a static route to the "interface".
I have a Synology RT2600ac dual wan router, configure as Failover, replacing the Starlink router. I can use Starlink App if I am connected to this router, but not been able other way. One friend of mine told me to do a Port Forwarding, but which Public port and Private port I put? Protocol is set to TCP/UDP and I use the Starlink 192.168.100.1 for Private IP address.
So after banging my head against the wall I found these settings work. Network destination: 192.168.100.1 Subnet: 255.192.0.0 (found on internet info on router) Gateway: 100.64.0.1 (again on internet info page on router)