port-override – generate policies and force policy to use any port (old behavior)
port-strict – use ports from peer’s proposal, which should match peer’s policy
Can someone explain me the difference ? What means ports from peers proposal ? can i pin the communication to a networkport ?
what means “old behavior” ? Changed in mikrotik or change in standard ?
for a Windows 10 Client i can only user port-override in my tests.
port override is an old RouteOS behavior when there was only option to enable or disable “generate-policy”.
Port-strict is preferred since policy is mapped not just to ip address but also to port