Forum Discussion
Static Route
- Aug 29, 2019
Please clarify this. Is it your topology?
if you can ping your next-hop but not the device behind it, this could be for some reasons.
First of all, capture traffic using tcpdump for being sure that your packets are being sent.
#tcpdump -nnei 0.0 'host <destination_ip>'Do you see traffic when you ping your destination ip?
Please, share also your routing table
# ip route # tmsh show net routeKR,
Dario.
Hello Oreoluwa.
Take into account that in F5 there are two types of static routes:
- TMM static route (https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-routing-administration-12-0-0/10.html)
- Management static route (https://support.f5.com/csp/article/K13284)
If you check your routing table in F5, you could see that TMM route has less metric (so it's preferred).
# ip route show table main
...
default via 10.130.40.99 dev internal
default via 192.168.102.1 dev eth0 metric 9You should also check your self-ip port lockdown configuration to be sure that you are not dropping the returned packets
REF - https://support.f5.com/csp/article/K17333
KR,
Dario.
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