For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Neil8319's avatar
Neil8319
Icon for Nimbostratus rankNimbostratus
Apr 14, 2017

F5 as Default Gateway Routing issue

Hi All, I'm having an issue where a certain client needs to connect directly to a node behind F5 ie bypassing the F5.   The issue I have is that the node has a default Gateway of f5 and it receive...
application delivery
BIG-IP
LTM
Neil8319's avatar
Neil8319
Icon for Nimbostratus rankNimbostratus
Apr 18, 2017

For anyone who happens to read this I found that if I changed the destination to anything other than a wildcard 0.0.0.0 the routing works. In the example above I changed the destination to be 192.168.1.0/24 on my outbound forwarding ip server and the routing works.

 

It seems my version of F5 does not work with a wildcard destination of 0.0.0.0

 

Kevin_Davies_40's avatar
Kevin_Davies_40
Icon for Nacreous rankNacreous
Apr 18, 2017

I mistook your word wildcard to mean *. You are using 0.0.0.0 and that's fine. Their must be something else causing you a problem. I am glad to hear it is resolved.