jadzy wrote:
thought i'd do a reply to my old post. firmware 3.9.7 seems to have made starlink work just fine now. dhcp no longer getting stuck. i can browse the starlink dishy stats page as and when needed.

3.9.7 solved my issues with DHCP as well. However, in the past few days Starlink updated again and now the issues have returned. I can resolve the issue by either unplugging and reinserting the WAN2 input (patch lead from Starlink eth adapter) or rebooting the router.

I’ve yet to try any CLI commands. I will try this next time (likely tomorrow). If the CLI command works. Does the router have the ability to schedule CLI commands? I don’t want to issue a reboot as my failover is VDSL and as the line is so poor, regular reboots cause the line speed to drop further.

on the router web interface, open the Web Console (icon in the top right). use this command

ip dhcpc release 2

it'll kick the dhcp client on the wan2 port and get it to get a new address instead of renewing the current one. maybe easier than you're current fixes?

Did anybody solve the issue of not being able to get to the Dishy stats page. I've tried adding manual routes, load balancing route but does not work. I'm using a 2866, with Starlink as my WAN2. WAN1 is DSL.

Frustrating to say the least as it worked fine on a MikroTik router by adding a static route to 192.168.100.1 via gateway 0.0.0.0, but the Draytek won't accept this as a gateway IP.

Dishy stats pages has worked nicely since the 2862 got the 3.9.7 firmware. Just go to 192.168.100.1 which redirects to http://dishy.starlink.com/.

i've got a....
C 192.168.100.1/ 255.255.255.255 directly connected WAN2

automagically appearing in the routing table now.

I removed all the various attempts I put in place before that firmware came.

I’ve got a 2866 so firmware is 4.3.2.1_BT. It has the route already in the routing table but does not work….

Code:

C 192.168.100.1/ 255.255.255.255 directly connected WAN2

Statistics solution for me:

Setup a Route Policy
IP Range 192.168.100.1 to 192.168.100.1
Interface: Whichever WAN your Starlink is on (my case WAN2)
Specific Gateway: 192.168.100.1
Force NAT: On
Failover: WAN2