The points that can be seen under the link are not available under openwrt24
I am using 4.6.2 so I probably don't see the same thing you are.
It's a shame that no one answers about the settings
0.0.0.0/0 means default gateway - all traffic which will not hit another routing rule will take this.
Mask 255.255.255.0 means /24
IPv4 gateway isn't needed, just enter the details in Gateway
I've tried to change that. Strangely enough, everything is the same as before.
What are the instructions for if everything stays the same?
Could you please explain your issue? Do you not have any connection to the internet or what is not working?
Everything is possible, whether with routine or without.
I just followed the instructions on the GL inet page that tell me you should enter it. I'm just wondering what the point is if it can be done without a routine.
So why exactly are you following the manual? I mean, what is your ultimate goal?
I don't get it. If everything works, just ignore the manual...
Even though I am using 4.6.2, here are screenshots of the static route I put in. It gets a laptop and my phone app to the Starlink Dishy. My Starlink router is in bypass mode.
I hope this helps.
2 Likes
Thank you for your illustrated explanation. Things look a little different under the 24 version:
As an example, the target must be at the back /24. But I entered it as shown in the pictures. I have no idea whether this is correct.
Why do you think it must be /24?
Just change it to any other subnet you need.
So 255.255.255.0 = /24
Or 255.255.255.255 = /32
If I don't put /24 or whatever I can't save.
Otherwise the surface will not accept it.
I have to enter "/" and some number.
Ziel is the Ziel network, so you need to enter 192.168.x.0/24 there.
But I don't really get what is the goal.
Starting today the Starlink App can no longer access my Starlink Dish with the VPN on (Confirmed with two different routers (Asus Merlin Router and GL.iNet Open-WRT). It was working fine through yesterday as it had been for a long time. Beginning today it requires the VPN to be dropped for the Starlink App to access the Starlink Dish (Through the Cloud). Not sure if this is an issue with my VPN Provider or if Starlink has possibly started preventing access from VPN providers but thought I would pass this along.
Try to enter the subnet of the Dish to the VPN exception policy. Maybe it will fix the issue.
Tried before but tried again...Nope no joy...I think there's been a change somewhere else (Nothing on my end especially since yesterday when it was working). Put the Starlink dish IP in PBR (Which was not necessary before) but still doesn't work..May be being blocked at the VPN Provider (inadvertently) or at Starlink (Which I don't doubt as they do this kind of stuff all the time...They yanked direct Web Access through the browser a while back forcing everyone to use their App). Starlink is great for people who live in remote rural areas where the only previous options were low bandwith wireless options but it does come with certain limitations (Often implemented by Starlink (Musk?).
Hmm ive zero experience with starlink, but would it be a mtu issue?, maybe you need to set a really low mtu, i know some people went even around 700-800 on mobile connections thats where i kinda base it off.
Also what @motox22a says might be true, it can be a throttle mechanism or even a block, compared with years ago around 15 years, something like this would be very slow and have high ping with satellite connection, but starlink seem to be very fast, i think one remmenant of the past might be vpns causing spikes on their systems and then they block it due to the overhead?, a lower mtu might fix that but might be too low.
Its just a theory i never used starlink so 
Well...Now the Starlink App is working again through the VPN (Surfshark)...
Either my email got through to somebody at Surfshark (unlikely)...
Or something changed at Starlink (most likely).
Either way the Starlink App is working again through the VPN. (Via the Cloud)