Asus GT-AX6000 + StarLink

[Nite01]

Hi,
I recently installed Starlink, I did setup its router (gen3) in bypass mode, and connected it to my GT-AX6000 (latest stock firmware) with an ethernet cable. The connection works fine.
I have a couple questions :

1 - Following those instructions https://www.asus.com/support/faq/1047774/ , theres a point (mentioned also in the Starlink configuration steps) saying that I should setup a static route to 192.168.100.1 to be able to use the Starlink app on my phone.
Except Im currently able to use it without adding any static route, I can see statistics and everything. How does that work ?
The router is on ip 192.168.50.1 , using the dhcp ip pool 192.168.50.2-254

2 - About Qos configuration, Im not sure which I should enable.
The endgoal of the setup would be to have my main pc (which is connected directly to the router with an ethernet cable in the "priority port") to be able to utilize the full bandwidth and have priority over anything else.
With my previous internet connection (14Mbps / 2Mpbs) I had Traditional Qos, with user defined rules.
Now, the issue with Starlink is that Im not sure about the bandwidth values I should enter (when I run a speed test, it varies wildly from 150Mbps to 350Mbps download, and 10-20 upload).
Theres the "Adaptive Qos" setting, which has an "automatic setting" for bandwidth (How does that work ?). However, enabling that, running a speed test from my pc seems to be limiting its download to about 120 Mbps and upload to 4-5 Mbps. Running a speed test from the router ui (Game Acceleration/Internet Speed), gives normal values.

Thanks

 

[ColinTaylor]

1 - Following those instructions https://www.asus.com/support/faq/1047774/ , theres a point (mentioned also in the Starlink configuration steps) saying that I should setup a static route to 192.168.100.1 to be able to use the Starlink app on my phone.
Except Im currently able to use it without adding any static route, I can see statistics and everything. How does that work ?
The router is on ip 192.168.50.1 , using the dhcp ip pool 192.168.50.2-254

You would not normally need a static route for 192.168.100.1 as you have discovered. The reason being that by default all non-local traffic already goes through the "default route", which is via the WAN interface. However, it is possible that the user may have enabled the router's VPN client and routed "all clients" through the VPN interface instead. In such a situation the Starlink admin interface (192.168.100.1) would now be unreachable. So by specifying an explicit route to 192.168.100.1 you're creating a route with a higher priority between the router (and its LAN clients) and 192.168.100.1.