cancel
Showing results for 
Search instead for 
Did you mean: 

Can the F5 SSL Orchestrator(SSLO) send traffic to a not directly attached Layer 3 device?

I was playing with the SSLO wizards/guided configurations and when I tried to configure layer3 or http service with an IP address that is not directly attached to the a Vlan/Self IP on the F5 I got the error message " This is not a valid IP address for selected selfip for 'To Service' subnet.".

 

For ICAP services there is no problem to send the traffic to a not directly attached device but I have to ask if I can do the same for HTTP/Layer 3 inline service in some way?

 

 

 

 

Nikoolayy1_0-1664889788560.png

1 ACCEPTED SOLUTION

Kevin_Stewart
F5 Employee
F5 Employee

The security device IP has to match the to-service self-IP subnet. That's why you're getting this error.

The basic premise of an "inline" device is that SSLO sends traffic to/through it, and that device sends it back. For L3 devices, SSLO routes to the device, and the device must route back on a spearate subnet. It's not generally advisable to send that (decrypted) traffic across a network, so SSLO will by default create a private network enclave for each security service.

The GUI error is to prevent sending unencrypted traffic out onto a network. But if you abssolutely need to do this, just provide a dummy IP here, disable strictness on the service after deploying, and then modify the associated pool member(s). But again, keep in mind that SSLO expects the traffic sent to an L3/HTTP device to be routed back to SSLO on a separate subnet.

View solution in original post

1 REPLY 1

Kevin_Stewart
F5 Employee
F5 Employee

The security device IP has to match the to-service self-IP subnet. That's why you're getting this error.

The basic premise of an "inline" device is that SSLO sends traffic to/through it, and that device sends it back. For L3 devices, SSLO routes to the device, and the device must route back on a spearate subnet. It's not generally advisable to send that (decrypted) traffic across a network, so SSLO will by default create a private network enclave for each security service.

The GUI error is to prevent sending unencrypted traffic out onto a network. But if you abssolutely need to do this, just provide a dummy IP here, disable strictness on the service after deploying, and then modify the associated pool member(s). But again, keep in mind that SSLO expects the traffic sent to an L3/HTTP device to be routed back to SSLO on a separate subnet.