This might have been resolved in today’s Route10 firmware release, version 1.3x:
From what I see I now have the expected IP source in the redirect rule.
This might have been resolved in today’s Route10 firmware release, version 1.3x:
From what I see I now have the expected IP source in the redirect rule.