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.

Implementing SSL Orchestrator - Network Insertion Use Cases

General Topology Considerations SSL Orchestrator is deployed as an inline device on the network and supports both single devices and HA clusters using device groups. Deployment topology can be ...
Published Jan 22, 2020
Version 1.0
BIG-IP
deployment
network insertion
security
series-big-ip-ssl-orchestrator
SSL Orchestrator
KevinGallaugher's avatar
Icon for Employee rankEmployee
Technical Marketing Engineer for SSL Orchestrator. I have over 25 years experience in Cybersecurity, with over 15 years spent as a Technical Marketing Engineer. Prior to F5 I worked at Blue Coat, Gigamon and Fortinet.
View Profile
KevinGallaugher's avatar
Icon for Employee rankEmployee
Technical Marketing Engineer for SSL Orchestrator. I have over 25 years experience in Cybersecurity, with over 15 years spent as a Technical Marketing Engineer. Prior to F5 I worked at Blue Coat, Gigamon and Fortinet.
View Profile
Romain's avatar
Romain
Icon for Employee rankEmployee
Feb 05, 2020

Piotr,

The picture used for this article to illustrate the L2 topologies are confusing. As you mention, it is a simplification. For the L2 topologies, the MAC information is what is really significant.

For IP forwarding to take place between networks, you would need the routers to be in the same network on either side of the SSLO device.

Thank you for catching that. Hopefully this comment will bring some clarity. We'll work to modify these two diagrams in the article to make them clearer.

Romain