Forum Discussion
F5 LTM virtual server IP address:172.20.16.225 can get TCP request from 10.11.1.4, but not return TCP ACK
We are facing some issue on the F5 LTM: we have trace the network no issue as we can ping and trace on either network, but while checking the tcpdump which I have attached here a screen captured show like 172.20.16.225(F5 LTM virtual server IP address) can get TCP request from 10.11.1.4, but not return TCP ACK. So please suggest us what can be the issue and if possible the solution.
2 Replies
- Kevin_Stewart
Employee
So you see a client at 10.11.1.4 initiate a TCP handshake to the self-IP of the F5 at 172.20.16.225, and you see the SYN packet arrive at the F5's interface, but then the F5 doesn't complete the handshake? Do you by chance have any port lockdowns applied to the self-IPs? Packet filter rules? Are you simply pinging or something else?
- Kevin_Stewart
Employee
I see. For some reason I interpreted self-IP. So you have a VIP configured on a specific IP and port 23, you see the client's SYN packet arrive at the VIP, but the VIP does not finish the handshake. Is that correct? How is your VIP configured?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com