One option can be to also add a rule indicating floating ip to any to do routing in native vrf.
Sachin
========================================================================
Hi Sachin,
In case of in-network service interface, interface has VRF assign acl entries present in it.
Rules are as below
1> Self-IP to any —Do route lookup in native VRF
2> Rest all — Do route lookup in internal VRF.
If this interface also has floating IP, then in agent we were applying this ACL after floating-ip
translation and eventually doing route lookup in internal VRF where destination route would
not be present.
Can this ACL be more precise specifying source VN and destination VN??
Or Should agent not apply interface ACL entries while doing floating IP translation??
One option can be to also add a rule indicating floating ip to any to do routing in native vrf.
Sachin
======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ==
Hi Sachin,
In case of in-network service interface, interface has VRF assign acl entries present in it.
Rules are as below
1> Self-IP to any —Do route lookup in native VRF
2> Rest all — Do route lookup in internal VRF.
If this interface also has floating IP, then in agent we were applying this ACL after floating-ip
translation and eventually doing route lookup in internal VRF where destination route would
not be present.
Can this ACL be more precise specifying source VN and destination VN??
Or Should agent not apply interface ACL entries while doing floating IP translation??
Regards
Naveen N