I have a TP-Link Archer XX230v v1 router updated with the latest firmware available.

It is connected to the internet via modem in bridge mode that provides IPv6 via prefix delegation (PD). The router correctly receives the delegated prefix (2804:xxx:xxxx:xxxx::/64) and displays it in the WAN interface, in addition to announcing this prefix in the LAN via RADVD and RDNSS.

However, only a few devices can use IPv6 on the LAN. Specifically, my Android phone (Samsung) gets the IPv6 address but can’t navigate, and sites like test-ipv6.com indicate absence of IPv6.

After detailed analysis, I identified that the router is not announcing the default route IPv6 (::/0) in Router Advertisements (RA). This absence of “default route” causes newer Android devices to ignore IPv6, even with the correct prefix and DNS.

I tested it with :

    Delegated prefix and Static prefix

    RADVD and DHCPv6 server

    Several Android and other devices that work

By connecting the same cell phone directly to the carrier modem (without TP-Link), IPv6 works normally.
Therefore, the problem is clearly in the way the TP-Link router generates the RA in the LAN.

I would like to know if:

    Correction for this behavior is predicted via firmware

    Or if there is any way to force IPv6 standard route announcement in ARs

The Router Lifetime field in Router Advertisements (RA) defines how long devices should trust the router as the default IPv6 gateway.

    A healthy, functional value would be 1800 seconds (30 minutes) or more.

    30 seconds is considered unreliable or suspicious — Android discards it right after connecting.

    Result: Android even sees IPv6, but completely ignores route ::/0 by considering it unstable.

Unfortunately, in TP-Link Archer XX230v v1 with standard firmware, there is no option in the interface to change the life time of the AR.

    This confirms that the firmware is limited or defective, and this behavior breaks full IPv6 support on modern Android.