Forum Discussion

ebrc's avatar
ebrc
Icon for Nimbostratus rankNimbostratus
Feb 20, 2017

Issue with OCSP and CRLDP protocol with default route in Partition

I have a problem with our F5 to configure the CRL check for client certificates. We have an F5 that we share for many clients infrastructure. Each client has his own partition and route domain.   ...
BIG-IP Access Policy Manager (APM)
cloud
LTM
security
ebrc's avatar
ebrc
Icon for Nimbostratus rankNimbostratus
Mar 06, 2017

No, as I tried to explain (sorry for my english), the management route are on totally different network/infrastructure than the default route of the partition. That's why I get trouble to contact CRLDP / OCSP server.

 

For example, the management interface is on 172.20.10.0/24 and the default route of the partition is on 192.168.146.0/24 (Of course with self and floating ip on this network). Both network are nothing to do together. In this case, I configure the CRLDP / OCSP server which has 192.168.147.10 as ip. So the traffic should go through the default gateway 192.168.146.1 and then be router to 192.168.147.0/24 by the next hop. But, in this case, the traffic is sent to the default gateway in 172.20.10.0/24 and then lost because there is no route on this infrastructure. I found no way to force the traffic to use the default gateway of the partition.