As noted:
Perhaps it does work, but the traffic is input - no need to redirect. I was just noting that a normal Input traffic rule would also work.
but this rule is not for that purpose, ie. access DNS server, but to force dns traffic to router.
i.e. prevent work around router's dns server by specifying a different dns server on client.
1 Like
Nope, I guess that's only a visual bug in LuCI. Therefore I've already listed the correspondent uci entries with the 'any' option.
3 Likes
Correct, jow merged a fix to LuCI fw4 a couple weeks ago that lets you select address family for both port forwards and NAT rules, which includes correcting the display of those settings.
1 Like
The fix ...
... seems to be incomplete, e.g. current master:
I've quickly added some (missing?) logic in forward.js (line 41 + 42):
ipv4: ((!family && dip.length > 0 && dip.indexOf(':') == -1) || (!family && dip.length == 0) || family == 'ipv4'),
ipv6: ((!family && dip.length > 0 && dip.indexOf(':') != -1) || (!family && dip.length == 0) || family == 'ipv6'),
... and now it works like expected ... 
edit: I've opened a PR (https://github.com/openwrt/luci/pull/6331), let's see if it is accepted.
7 Likes