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!