Forum Discussion
Routing issue in forwarding traffic to next hop
Hi all
We have configured forwarding traffic for internal and external vlan.
We are getting some disconnection after some time.and no traffic will is forwarding after this.
My default route is pointing to a pool which is external routers where we are load balancing link.specific routes to internal
Below is the tcpdump output when there is an issue'
7.170109 IP 2.50.140.130.4978 > 83.111.53.84.https: S 2693203564:2693203564(0) win 65535 11:05:49.906556 IP 2.50.140.130.4979 > 83.111.53.84.https: S 1660167582:1660167582(0) win 65535 11:05:52.859309 IP 2.50.140.130.4976 > 83.111.53.84.https: S 3269291410:3269291410(0) win 65535 11:05:52.875755 IP 2.50.140.130.4979 > 83.111.53.84.https: S 1660167582:1660167582(0) win 65535
Can anybody advice how to check this.
Thanks
3 Replies
- Cory_50405
Noctilucent
The IP addresses in this tcpdump correspond to what exactly? I see SYN packets being sent but no response. The causes for this could be numerous. Was this capture taken on your BIG-IP appliance?
- Mathew_58740
Nimbostratus
The problem i am facing is if we give self IP address as the next hop in the router its working fine and if we set floating ip address as next hop its not working.
Thanks
- Cory_50405
Noctilucent
Check the port lockdown setting on your floating IP.
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