Starlink

[RedNeckGeek]

Still waiting, but my patience is running a bit thin.

The way I look at it, I had no other choice other than to wait. AT&T and Verizon won't sell me a cellular hot spot because cellular data reception is marginal here. I tried T-Mobile, and it was good when it worked, but it experienced long periods of time when I got no connection at all. Worse, trying to cancel the "free" trial required so many phone calls over a six month period I lost track of just how many. In addition to HughesNet, I've tried the aptly named Exede (I always seemed to excede my data cap before the end of the month), and another one called Wildblue/Viasat, again with data caps and high latency. Apparently HughesNet has a new satellite with more capacity, but moving to it would entail a new two year contract and I'd still be dealing with unrealistically low data caps. If I had any choice other than traditional geosynchronous satellite internet service, I'd take it. Fortunately, the wait for StarLink, at least for me, has been worth it.

 

[bdhsfz6]

StarLink portability is aimed at people who have boats or RVs and who would need Internet access away from home. This is a REALLY big deal for boats.

Starlink seems to be limited to 12 miles offshore at the present time, which I think is mainly due to the need to have satellite to satellite communication. Having said that, I noticed there were dead zones in the Chesapeake in VA, one of the sounds in NC, and in one of the Great Lakes where one would expect coverage.

In some places, cell service is good enough if one is near shore, we have had cell service six or so miles off shore, and I have heard of people getting a signal farther offshore. But even along the coast, one can be without cell service and cell Internet can be expensive. Offshore Internet is exceedingly expensive, and can cost tens of thousands of dollars for the equipment and the data plans can be hundreds of dollars a month and still be data limited. I have seen plans that were $1 a megabyte.

Starlink is working on boats at the present time but not warrantied, however, this is one of the areas that Starlink wants to support so it will happen in time. Starlink is going to wipe out some of the off grid Internet providers. Paying $130 a month for unlimited bandwidth at the Starlink speeds is dirt cheap compared to the competitors.

Land based, we were paying $120 per month of an unlimited cell plan. And our DSL at 1.5 mbps was $50-75 a month. Our new cell plan, we need backup Internet access, is $20ish a month but data limited AND not working.

The Starlink dish will have to be redesigned for it to work on a boat unless tied up at a marina. When under way, the existing dish will not react to rocking motion or pivoting when at anchor due to wind & tide.

 

[KilroyJC]

Proud member of the “Waiting and Waiting List”

 

[buckeyefarmer]

Still waiting, but my patience is running a bit thin.

I’m still waiting also. At least I have LTE available.

 

[Fallon]

The Starlink dish will have to be redesigned for it to work on a boat unless tied up at a marina. When under way, the existing dish will not react to rocking motion or pivoting when at anchor due to wind & tide.

Maybe not. Some people have previously gotten them working doing 70 down the highway. A given starlink satellite orbits every 90 minutes. I don't onow offhand what that translates to precisely, but its only going to be visible for a few minutes, probably less than 10.

As such, dishy uses a phased array antenna to be able to instantly redirect the antenna without physically re-aiming it. Either to track a given bird or hop to the next one. It should be able to handle the bobbing & rolling of a boat. It may need a better gyroscope to figure out how it's rolling, but it should be able to track fine.

 

[BigBlue1]

The Starlink dish will have to be redesigned for it to work on a boat unless tied up at a marina. When under way, the existing dish will not react to rocking motion or pivoting when at anchor due to wind & tide.

Well, yes and no. I'm sure they will redesign it for in-motion use to have a lower profile and possibly be able to hold position with gyroscopic stabilizers or something. But even absent that the current dish probably does OK. It's phased array antenna system has the ability to focus in on multiple satellites at once as they are moving. It has dozens of receptors so it can lock on pretty well. I'd suspect it would do better than you think.

But 100% agree that the current 'portability' offering is intended static use in multiple locations, not in-motion use.

 

[RedNeckGeek]

@RedNeckGeek what you are trying to do is doable. My guess is that you need to change browsers on your phone, and allow cookies to login. Other folks have reported that issue. I would disconnect everything, including the Ethernet adapter until you login normally.

I downloaded and installed Firefox on the iPhone 12 ProMax. There doesn't appear to be any option for enabling/disabling cookies. There was an option to clear cookies, so I did.

I powered down the StarLink modem and disconnected the Ethernet adapter.

Then power cycled the StarLink modem four times, and when it restarted, logged in to the STARLINK WiFi network using the iPhone app, renamed it and gave it a password, then went to the Settings menu and tried to login. That brings up a new window in Firefox, where it takes the username/password I've already set and stored in my password manager. That is NOT the WiFi username/password, FWIW. There's no way I'm typing in an 18 character string of random characters, but just to be safe, I brought up the StarLink username/password in the password manager, set the password field to "reveal", and copied the password. Then back in Firefox, ensured that the username was entered correctly, and pasted in the password. The Sign In screen blinks, The INVALID CREDENTIALS error message is displayed, the username/password fields become blank, and the only option I'm given is "LOCKED OUT?" If I play the game and request a password reset, then use the new credentials, I can login to the Starlink website using either Safari or Firefox. But I still can't login from the StarLink app: It always gives the INVALID CREDENTIALS error message. And that means I can't change any of the Settings on the StarLink modem.

I deleted the StarLink app on the iPhone, downloaded a fresh copy, and it didn't make any difference. At this point I'm out of options as to how to proceed, and I still haven't gotten a response from my email to StarLink tech support.

So for now I'm going to reinstall the Ethernet adapter and get back to where the UDMP is using the StarLink WAN connection. It may be slower than it could be, but it's vastly faster and more reliable than HughesNet ever thought of being.

On your UDM Pro, you want Starlink on WAN1, port 9, and Hughes on WAN2 port 10.

I've verified that is how the two WANs are configured.

If the Starlink router is operational (I.e. not shutdown), you need to have your Hughes and your home network off 192.168.1.0/24. That belongs to Starlink. I suspect that the switch to Hughes and back is causing that issue. You don't need a static route for 192.168.100.1. Your UDM will automatically send it out the WAN port. (If you want Starlink stats when you are on Hughes, that isn't going to work, as you can't have both WAN ports active on a UDM PRO.)

The HughesNet modem is set to use 192.168.0.1 and there is no way to change it.

The UDMP is using 192.168.10.1 as the gateway address. All of the cameras and other devices are using this address.

The StarLink modem uses 192.168.100.1 as the gateway address. When the MBP laptop is connected to the StarLink WiFi, I can enter this address in the browser address field and it brings up the StarLink admin page. However, there is no option to alter Settings, and it directs me to use the iPhone app to do so.

Before I set up the static route on the UDMP to 192.168.100.1, that address was not reachable when typed into the address bar of FireFox running on a MacBook Pro laptop that was using the 192.168.10.1 gateway WiFi.

With the hardware you have, you should have no trouble hitting 150-200Mbits/s on a modern tablet/phone/PC.

That's encouraging, but so far I'm lucky to get 1/3 to 1/2 that.

Finally, I would suggest moving your antenna (Dishy) to get fewer obstructions. We see an interruption a week for two minutes tops.

The only obstruction is the pole on which the HughesNet dish is mounted. The 75' cable that came with the StarLink is too short to allow me to elevate the Dishy, so I've got an order in for a 150' one. I've never seen any complaints about obstructions in the OUTAGES log.

Thanks for the information, I really appreciate the effort that went into them. I'll provide an update if/when StarLink tech support gets back to me.

 

[ponytug]

I downloaded and installed Firefox on the iPhone 12 ProMax. There doesn't appear to be any option for enabling/disabling cookies. There was an option to clear cookies, so I did.

I powered down the StarLink modem and disconnected the Ethernet adapter.

Then power cycled the StarLink modem four times, and when it restarted, logged in to the STARLINK WiFi network using the iPhone app, renamed it and gave it a password, then went to the Settings menu and tried to login. That brings up a new window in Firefox, where it takes the username/password I've already set and stored in my password manager. That is NOT the WiFi username/password, FWIW. There's no way I'm typing in an 18 character string of random characters, but just to be safe, I brought up the StarLink username/password in the password manager, set the password field to "reveal", and copied the password. Then back in Firefox, ensured that the username was entered correctly, and pasted in the password. The Sign In screen blinks, The INVALID CREDENTIALS error message is displayed, the username/password fields become blank, and the only option I'm given is "LOCKED OUT?" If I play the game and request a password reset, then use the new credentials, I can login to the Starlink website using either Safari or Firefox. But I still can't login from the StarLink app: It always gives the INVALID CREDENTIALS error message. And that means I can't change any of the Settings on the StarLink modem.

I deleted the StarLink app on the iPhone, downloaded a fresh copy, and it didn't make any difference. At this point I'm out of options as to how to proceed, and I still haven't gotten a response from my email to StarLink tech support.

So for now I'm going to reinstall the Ethernet adapter and get back to where the UDMP is using the StarLink WAN connection. It may be slower than it could be, but it's vastly faster and more reliable than HughesNet ever thought of being.

I've verified that is how the two WANs are configured.

The HughesNet modem is set to use 192.168.0.1 and there is no way to change it.

The UDMP is using 192.168.10.1 as the gateway address. All of the cameras and other devices are using this address.

The StarLink modem uses 192.168.100.1 as the gateway address. When the MBP laptop is connected to the StarLink WiFi, I can enter this address in the browser address field and it brings up the StarLink admin page. However, there is no option to alter Settings, and it directs me to use the iPhone app to do so.

Before I set up the static route on the UDMP to 192.168.100.1, that address was not reachable when typed into the address bar of FireFox running on a MacBook Pro laptop that was using the 192.168.10.1 gateway WiFi.

That's encouraging, but so far I'm lucky to get 1/3 to 1/2 that.

The only obstruction is the pole on which the HughesNet dish is mounted. The 75' cable that came with the StarLink is too short to allow me to elevate the Dishy, so I've got an order in for a 150' one. I've never seen any complaints about obstructions in the OUTAGES log.

Thanks for the information, I really appreciate the effort that went into them. I'll provide an update if/when StarLink tech support gets back to me.

Well, that's great that the networks aren't on top of each other.

The login on the app is supposed to be the Starlink.com login credentials, so what you are experiencing is not right. FWIW: it works on Safari on my phone, but only in non-private mode. You are using the Starlink App to try to log into the Starlink router via the now renamed SSID, right? (I.e. factory reset, setup the local Starlink WiFi, change the phone to the the Starlink WiFi (the new SSID and password), and then in the app use the Starlink.com credentials, right?)

I am concerned that typing 192.168.100.1 into a MBP connected via the UDM Pro doesn't just work. Something isn't configured right. That should just work. How did you define 192.168.10.0/24? The defaults on the UDM Pro (or any router) should forward every packet not on your local network(s) (i.e. not 192.168.10.0) to WAN1. So the fact that the UDM Pro doesn't means something is amiss in the UDM Pro configuration, and the three places that I can think of are the WAN port definitions and the 192.168.10.0 network definition. Have you tried temporarily setting the DNS to point at 192.168.1.1? (It will wipeout functioning on Hughes, but just as a test, it should then pass 192.168.100.1 without a static link.) If that works, that points to a DNS or route (port/network) configuration issue. You do have WAN1 as default, and WAN2 as failover only, right?

I suspect that the DNS configuration is causing timeouts, slowing your network down, but I am just guessing.

All the best,

Peter

 

[LittleBill21]

dns has nothing to do with routing, dns is not even needed or used when browsing to an ip. this sounds more like a issue with his fail over, it might be defaulting to the hughes side, which is why a static routed is needed etc, but with the unifi only doing 65mbit. i have a feeling he's got a bunch of different issues

as was said. he needs to remove everything, and add one piece at a time, till the problem is found

 

[RedNeckGeek]

You are using the Starlink App to try to log into the Starlink router via the now renamed SSID, right? (I.e. factory reset, setup the local Starlink WiFi, change the phone to the the Starlink WiFi (the new SSID and password), and then in the app use the Starlink.com credentials, right?)

Yep, that's exactly what I did. Multiple times. And that's with the Ethernet adapter disconnected.

I am concerned that typing 192.168.100.1 into a MBP connected via the UDM Pro doesn't just work. Something isn't configured right. That should just work.

OK, I paused the static route to 192.168.100.1, and now typing 192.168.100.1 into the browser address bar does take me to the StarLink router. I got the idea for the static route from a CrossTalk Solutions YouTube video. But he's using the Gen1 StarLink, so maybe that's the reason it was needed for him.

How did you define 192.168.10.0/24?

Here are the settings for 192.168.10.0/24:
Network Name Default
Router: Office DreamMachine Pro
Gateway IP/Subnet->Host Address: 192.168.10.1
Gateway IP/Subnet->NetMask:24 (249 usable hosts)
Gateway IP: 192.168.10.1
Broadcast IP: 192.168.10.255
Usable ISPs: 249
IP Range: 192.168.10.6 - 192.168.10.254
Subnet Mask: 255.255.255.0

Advanced Configuration is stet to Manual:
Network Type: Standard
Content Filtering: None
IGMP Snooping: unchecked
Multicast DNS: unchecked

DHCP:
DHCP Mode: DHCP Server
DHCP Server Range Start: 192.168.10.6
DHSP Server Range Stop: 192.168.10.254
DHCP Guarding: unchecked

DHCP Management:
DHCP DNS Server: Enabled
DNS Server 1: 1.1.1.1
DNS Server 2: 1.0.0.1
DHCP Default Gateway: Auto
DHCP Lease Time: 14400 seconds
Domain Name: localdomain
Custom DHCP Option: None
Option 43 Application Host Address: None
DHCP NTP Server: unchecked
DHCP Network Boot: unchecked
DHCP Time Offset: unchecked
DHCP WPAD URL: None
DHCP TFTP Server: None

IPv6
IPv6 Interface Type: None

The defaults on the UDM Pro (or any router) should forward every packet not on your local network(s) (i.e. not 192.168.10.0) to WAN1. So the fact that the UDM Pro doesn't means something is amiss in the UDM Pro configuration, and the three places that I can think of are the WAN port definitions and the 192.168.10.0 network definition. Have you tried temporarily setting the DNS to point at 192.168.1.1? (It will wipeout functioning on Hughes, but just as a test, it should then pass 192.168.100.1 without a static link.) If that works, that points to a DNS or route (port/network) configuration issue.

WAN1 settings are as follows:
Name: WAN1
Host Device: Office DreamMachine Pro
Interface: Port 9 - WAN
Expected ISP Speeds: Download 100 Mbps, Upload 12 Mbps
Advanced
Set to Auto, and all the settings are grayed out. The only thing that appears to be active is DNS Server, which is set to Auto

WAN2 settings are as follows:
Name: WAN2 FailOver
Host Device: Office Dream Machine Pro
Interface: SFP+ 1 - WAN2
Expected ISP Speeds: Download 10 Mbps, Upload 1 Mbps
Advanced
Set to Manual
The only thing changed is DNS Server, where Auto is unchecked and entries for DNS Server 1: 1.1.1.1
DNS Server 2: 1.0.0.1

IPv4 Connection: DHCPv4
IPv6 Connection: Disabled

You do have WAN1 as default, and WAN2 as failover only, right?

WAN1 is the default WAN, and is where the StarLink modem is attached.
WAN2 is set to Failover Only (the only setting that the UDMP supports.

I suspect that the DNS configuration is causing timeouts, slowing your network down, but I am just guessing.

After disabling the static route and copying all that config info, I used the StarLink app to run another set of speed tests.

From the iPhone to the StarLink Router WiFi:
iPhone->Internet: Down - 167 Mbps, Up - 5 Mbps
StarLink Router->Internet: Down - 154 Mbps, Up - 7 Mbps
iPhone->StarLink Router: Down - 612 Mbps, Up - 296 Mbps

From the iPhone to the nearest Unifi Access Point WiFi:
iPhone->Internet: Down - 51 Mbps, Up - 10 Mbps
StarLink Router->Internet: Down - 130 Mbps, Up - 2 Mbps
iPhone->StarLink Router: Down - 75 Mbps, Up - 49 Mbps

Seems like the bottleneck is with the Unifi network. When I get a chance, I'll run an Ethernet cable to the MBP and see if a wired connection improves things.

Thanks again for your help, Peter!