So the developers are fully aware of this issue now and it has been reported as developer bug NUTM-3439. The temporary work around until it has been patched in a future up2date is to: Dev mentioned one workaround that you could try is to configure the Local Networks as follows instead of "Any". Object1: IPv4: 128.0.0.0/1 IPv6: 8000::/1 Object2: IPv4: 64.0.0.0/2 IPv6: ::/1 Object3: IPv4: 32.0.0.0/3 Object4: IPv4: 16.0.0.0/4 Object5: IPv4: 8.0.0.0/5 Object6: IPv4: 4.0.0.0/6 Object7: IPv4: 2.0.0.0/7 Object8: IPv4: 1.0.0.0/8
↧