Forum Discussion
ToonVA
Cirrus
CirrusForward traffic based on TCP Port - LTM Policy
Hi All, i try to troubleshoot a configuration i can't get working and could use some input here. So we have 5 Virtuals all on the same public IP but different ports (20, 21, 22, 990 and 0). The Vir...
Okay, i can't explain why but suddenly it works with the earlier mentioned configuration. Maybe the session was hanging in between tests resulting in a bad test but for anyone expierincing a similar issue the policy combined with local side of external interface works.
JRahm
Admin
Adminin your rules, what end of the tcp connection is it applying that port to, the remote or local? If remote, that would make sense, as your remote port is outside of the 1024-1048 range. I think there's an option in the rule to apply local/remote (don't have an instance up right now, battery is getting low and I'm remote)
Edit: I see your policy now...I'll dig in when I get home. Any reason you don't have an ftp profile applied to that virtual?
ToonVAHey JRahm,
Any reason you don't have an ftp profile applied to that virtual?
Honestly it was an existing configuration which we had to adapt a bit so never really looked for "optimization" but i will take it into account once i get this working.
It's indeed the client who picks a port in the range 1024-1048 so the logic of "local side of external interface" seems to be correct (it's not displayed in cli when i select this in the policy options only true GUI).
https://support.f5.com/csp/article/K56149721?utm_source=f5support&utm_medium=RSS