That’s an “advantage” of IPv6; your local IP addresses now belong to the ISP, so the router can’t do anything like policy based routing. If your device is using a Starlink IPv6 address, the only route to it is Starlink. If both ISPs are giving you a delegation, your devices need to get IPs on both networks and then it’s up to each device/OS to implement any policy you want, not the router.
This is, of course, a massive pain in the arse. It breaks VPNs, policy based routing, and high-availability/failover, unless you do address translation at the router - but in that case, you might as well just use IPv4, since address translation is the great bear you’re using IPv6 to avoid. All for the highly dubious benefit of exposing all your internal infra directly to the Internet.
IPv6 is great for public traffic, but way more trouble than it’s worth for internal networks.
My SMB router doesn’t support ipv6 for many functions including policy routing between isps
Imagine my surprise to see my ipv4 through T-Mobile and my ipv6 through Starlink.
That’s an “advantage” of IPv6; your local IP addresses now belong to the ISP, so the router can’t do anything like policy based routing. If your device is using a Starlink IPv6 address, the only route to it is Starlink. If both ISPs are giving you a delegation, your devices need to get IPs on both networks and then it’s up to each device/OS to implement any policy you want, not the router.
This is, of course, a massive pain in the arse. It breaks VPNs, policy based routing, and high-availability/failover, unless you do address translation at the router - but in that case, you might as well just use IPv4, since address translation is the great bear you’re using IPv6 to avoid. All for the highly dubious benefit of exposing all your internal infra directly to the Internet.
IPv6 is great for public traffic, but way more trouble than it’s worth for internal networks.