Good evening everyone,
I have a Balance 380 with 2 Starlinks connected.
The Starlinks have a non-customizable address of 192.168.100.1.
I set Health Check with ping 8.8.8.8 and 8.8.4.4 to have the real connectivity situation and use fail over to the 3th WAN.
I created 2 service VLANs to activate Starlink with related SSIDs with Outbound Policy rules that come out with WAN STARLINK 1 or 2 based on the wi-fi to which the user connects.
When I have to activate Starlink the application goes to “Starlink”.
Since Health Check failed, I can’t reach the Starlink activation site.
I tried to create an Outbound Policy rule in enforced of starlink.com domain on the WAN but it doesn’t work.
Another guy… maybe have another way to solve this for you.
I don’t have Starlink… but this is what you need to do.
Because Starlink use 192.168.100.1, you cannot manage both at same time.
Configure one starlink at time.
just connect starlink “one” at wan 1 … open the app (android/ios) and do the configurarion
disconnect it from wan 1
connect starlink " two " at wan 2 … open the app (android/ios) and do the configuration.
connect starlink " one " at wan 1.
Try… this is a simple way to help you to manage your starlink devices.
Can you change the default ip address of your Starlink?
something like 192.168.100.1 to first starlink (keep it the same)
change the second starlink to something like 192.168.101.1
This way you will make more simple to use dns lookup or ping to test your starlink links.
@MarceloBarros You can’t change the management ip of the dish at this time.
@bmtec
I’ve requested this to be transparent and it should be working in a updated 8.5 if the peplink engineers understood my requirements. I’ll update here when I’ve done some testing with a inactive starlink dish.
Marcelo, If I could change Starlink IP I would. Don’t you think?
DNS Lookup test it is not properly if you want to know if you really have internet or not. If you connect the antenna without subscription DNS Lookup NOT set the Health Check to Failed, then the system don’t go in fail over to SIM for example.
You are not asking to hit the management IP of the terminal (192.168.100.1). you want to force traffic out the terminal to Starlink’s central servers for initial activation.
I don’t have an inactive unit to test with, Because the system needs a valid DNS lookup before any other name based rules will fire you will have to disable the health check on one of the WANs. This should allow the DNS to go out, and then allow connections to their sandboxed www.starlink.com system. You should be able to activate both systems via WAN1… you don’t have to use the actual terminal to activate. You can use any method to get to the internet… LTE Wifi etc.
If you don’t want to remove a health check then we would need to do it by IP and put in one of the current www.starlink.com IP’s into local DNS Records. 151.101.129.143 works today. Then set an enforced outbound policy for that IP.
Thanks for the reply.
However, if I insert the current Starlink IP in the local DNS, the connection will be valid for the system, right? It will not be in failed.
My goal would be to have the connection in the real failed state since there is no internet connectivity, but to allow the user to access the Starlink activation page.
I would like to make it easy for the user without having to make settings
I cannot tell you that without actual testing with an unregistered terminal. Is there a reason you expect the terminal to loose its authorization while they are on the way?
I think you should test with a special SSID/VLAN that is 100% enforced via WAN#1. You will need to make the DNS for this VLAN the ones that Starlink authorizes… like 1.1.1.1 and 8.8.8.8. Then that VLAN can always be used to authorize the accounts, but shouldn’t be used for anything else.
If for some reason (example out of credit) there is no internet, I would like the system to switch to priority 2. This normally happens with “Alghorithm Priority”.
Ok the Enforced rule on WAN 1 or 2, but if there is no connectivity because “Health check” has rightly failed (before activation there is no internet), the user cannot access the Starlink page, I did some test and also with “Enforced” web page not work, also with domain rule.
I hope I was clear.
This problem also occurs without VLAN, if in a basic way you have for example a BR2 with:
WAN1 Starlink
WAN2 Starlink
SIM
If the WANs have Health Check correctly on Google 8.8.8.8, Health Check will have correctly failed. I could not activate Stralink because it does not pass the activation page. In this case I could only do it if I have a working SIM or if I modify the Health Check of the WANs.
I would like to avoid having the user do it.
I would like a rule that “Enforced” the page Starlink to WAN 1 or 2 also if Health Check is failed
the problem is that you need DNS from the BR2 to work and with both WAN links down there is no valid dns for www.starlink.com which is needed to trigger the enforced domain rule.
You can use a different rule, where a particular device will always be enforced Wan1, or a different SSID rule all enforced but you can’t have it happen magically with no user effort.