Actions
Bug #8437
closedinvalid outbound nat rules written when using ipv6 rules on interfaces that also have ipv4 adresses..
Start date:
04/05/2018
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:
All
Description
Rules like below can be generated with the outbound-nat settings:
nat on $LANI proto icmp from fd:1:2:3::/64 to any -> 192.168.133.1/32 port 1024:65535
nat on $1WANDESCRIPTIONFORINT proto icmp from 1:2:3:4::/64 to any -> FE80::2/32 port 1024:65535
However the ipv4 ip is wrong, and also the /32 subnet on the interface ip should not happen:
Actions