When using Web Filtering in standard mode, I see a difference in UTM behavior in selecting the outbound source IP address for the IPv4 and IPv6 world. We are running version 9.413-4.
In the IPv4 world the UTM selects the primary IPv4 address defined on the WAN interface which is the expected behavior. This is true regardless if you define additional IPv4 addresses with a /32 subnetmask or the same subnetmask as the WAN interface.
In the IPv6 world the UTM selects the *latest* IPv6 address defined on the WAN interface, not the primary IPv6 address. This seems to be true regardless if you define additional IPv6 addresses with a /128 prefix or the same prefix as the WAN interface.
I believe this is not the behavior you would expect. So, is this a bug or a feature?
BTW --- what is the best practices for additional IP addresses: /32 (IPv4) & /128 (IPv6) or the same subnet/prefix as the WAN interface?
Regards,
Stefaan
This thread was automatically locked due to age.
