QuRouter firewall IPv6 does not support suffix matching

Feature Request
1

The QNAP 301w router currently does not support suffix matching in its IPv6 firewall. I hope this feature can be added in future versions, because the IPv6 prefix provided by the ISP keeps changing. By using EUI64 to fix the suffix, you can match the corresponding IPv6 address through the suffix. For example:
::1204:c3ff:fe07:8db4/::ffff:ffff:ffff:ffff matches IPv6 addresses with the suffix 1204:c3ff:fe07:8db4.

This method is supported by ip6tables. After connecting via SSH, the following command works:

ip6tables -I USER_FIREWALL 1 -p tcp -d ::1204:c3ff:fe07:8db4/::ffff:ffff:ffff:ffff --dport 20080 -j ACCEPT

However, currently, entering this format directly on the web page does not work.

22ac8007cb29a9f5de0efc8eb8a606c5
22ac8007cb29a9f5de0efc8eb8a606c51988×774 81.2 KB

591815b3caefe1db51105e29667e1d33
591815b3caefe1db51105e29667e1d331434×1738 113 KB

2

Hello, thank you for your reply. The team will take it into consideration and proceed with further planning.

3

@Ruby Hi, any updates on this?

4

@Ruby I noticed that the latest Beta version’s frontend now supports this input, but when I click apply, it throws an error. It seems the backend hasn’t implemented compatibility yet:

bde44be34f638ad9111e8a26ef26526d
bde44be34f638ad9111e8a26ef26526d1468×838 38.1 KB

5

Hello, we are already working on fixing this bug internally. The IPv6 firewall suffix matching feature is currently expected to be released in version 2.7.3. If you need it urgently, please report it to QNAP support and we will assist you further. Thank you!