QuWAN's Multi-WAN and IPv6 Support

Feature Request
1

Dear QNAP Network Team,

I would like to request the following feature improvements for QuWAN to better suit my deployment needs:

  1. IPv6 site-to-site support
    My network has already enabled IPv6, but the QuWAN documentation does not clearly state whether IPv6 is natively supported as the transport protocol for site‑to‑site VPN.
    Request: Please confirm whether the current version supports IPv6‑based QuWAN connectivity. If not, kindly consider adding this in a future release.

  2. Hub mode restriction under NAT
    My device has 4 WAN ports. One of the WAN connections is behind NAT, but that specific line is optimised by the ISP and I need to set the device as the Hub to fully utilise that line. Currently, QuWAN forces the device to be an Edge node if any WAN is under NAT, and does not allow manual assignment of the Hub role.
    Request: Please relax this restriction. Allow users to manually designate a specific NAT‑connected WAN as Hub in multi‑WAN scenarios, or provide a more flexible role assignment policy.

  3. Bulk import of IP subnets for policy‑based routing
    Currently, policy‑based routing only supports adding IP subnets one by one. When managing dozens or even hundreds of rules, this is extremely inefficient and error‑prone.
    Request: Support bulk import via CSV/TXT files, or allow pasting multiple subnets (separated by line breaks) at once.

  4. IPv6 policy‑based routing and load balancing
    Currently, the device only supports a single IPv6 WAN as the outbound interface. While QuRouter 2.5 introduced policy‑based routing and WAN load balancing for IPv4, these features do not appear to be available for IPv6 traffic.
    Request: Please confirm when IPv6 policy‑based routing and WAN load balancing will be supported, so that IPv6 traffic can also be distributed across multiple WAN connections based on custom rules and weight settings.

Device: QHora‑301w
Firmware / QuWAN version: 2.7.2 build 20260803

Please kindly confirm whether these limitations are due to hardware constraints or purely firmware/UI design choices.

Thank you for your consideration. I look forward to your reply.