Ipv6 in firewall doesn't work

Installing and Using OpenWrt
1

In my /etc/config/firewall config，has the configration below:
config rule
option name 'block-tcp-v4-5355'
option src '*'
option proto 'tcp'
option dest_port '5355'
option target 'REJECT'
option family 'ipv4 ipv6'
Then, I reload firewall, the result is

image
image947×401 21.9 KB

ipv6 rules can't be recognized.
WHY?

2

Please connect to your OpenWRT device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

ubus call system board
1 Like
3

Your screenshot doesn't show what you stated.

Let's see the output of the ubus call system board command.

1 Like
4

this command can't work in my device
image
Maybe it's because we've recompiled and installed some of the source code of OpenWRT

Back to the question of ipv6, I add some log in the firewall/iptables.c. Discover that when ipv6 rules start populating, the "xext.register_match" function seems occur somthing wrong.

image
image1531×223 22.3 KB

image
image881×105 3.82 KB

Perhaps I missed some kernel module support? I can't find the reason. Thanks

5

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

2 Likes