Hello,
To create recursion between 2 tables, You need something like this:
set routing-instances A routing-options static route X.Y.Z.W next-table B.inet.0
set routing-instances B routing-options static route X.Y.Z.W next-table A.inet.0
JUNOS won't allow You to commit that.
However, You might have a legit bidir packet stream with src.IP W.Z.Y.X and dst.ip X.Y.Z.W, going between interfaces in RI A & B. Then You would need this config to let it pass:
set routing-instances A routing-options static route X.Y.Z.W next-table B.inet.0
set routing-instances B routing-options static route W.Z.Y.X next-table A.inet.0
JUNOS won't let You to commit it either.
You will need to use static in 1 direction and FBF in another, to let this legit bidir stream to pass.
BUT - on SRX., You can let this legit bidir packet stream to pass by configuring only 1 line:
set routing-instances A routing-options static route X.Y.Z.W next-table B.inet.0
On SRX, the reverse flow is taken care of automatically during 1st session establishment, and You can't influence asymmetric reverse flow routing on SRX in flow-mode. By saying "asymmetric" I mean that:
- forward flow passes RI A->RI B
- reverse flow is meant to pass RI B-> RI C
HTH
Thanks
Alex