Hello Omada Community and Development Team,

I am running the ER7412-M2 business gateway in Standalone Mode on a native Dual-Stack (IPv4 / IPv6 DHCPv6-PD) WAN connection. While configuring local network security and VLAN isolation, I uncovered a significant feature parity gap regarding IPv6 local traffic management.

Device Details:

• Hardware Version: ER7412-M2 v1.30
• Firmware Version: 1.1.1 Build 20251112 Rel.54883

The Issue: Missing "Me" Destination Object for IPv6

In the Access Control List (ACL) menu, the built-in destination object "Me" (representing the router gateway itself) works perfectly for IPv4 rules. However, when switching the IP Type dropdown to IPv6, the "Me" option becomes greyed out.

There is currently no native system placeholder to represent the router's local gateway interfaces over IPv6. This makes it impossible to cleanly write rules to block or allow traffic destined specifically for the router itself when using IPv6.

Since many deployments rely strictly on Standalone Mode without a centralized Omada Controller, achieving full local security feature parity between IPv4 and IPv6 is critical.

Requested Solution for Standalone Firmware:

• Implement an IPv6 equivalent of the "Me" destination object in the Standalone ACL engine, matching the existing IPv4 capability.

Thank you for your consideration and continuous firmware improvements.