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
koheed_51878's avatar
koheed_51878
Icon for Nimbostratus rankNimbostratus
Sep 03, 2018

I had the same issue which I resolved by setting the destination to 0.0.0.0/0.

 

I initially didn't have the mask set which unfortunately the System still accepted.

 

ie. 0.0.0.0 = fail 0.0.0.0/0 = win

 

koheed_51878's avatar
koheed_51878
Icon for Nimbostratus rankNimbostratus
Sep 03, 2018

From a cli interface the difference is the "mask" setting. Not sure why the F5's will accept 0.0.0.0/32 but there it is: ltm virtual wildcard-forwarding {

 

destination 0.0.0.0:any

 

ip-forward

 

ip-protocol tcp

 

mask 255.255.255.255

 

partition GEN

 

}

 

ltm virtual wildcard-forwarding {

 

destination 0.0.0.0:any

 

ip-forward

 

ip-protocol tcp

 

mask any

 

partition GEN

 

}