Content migration in progress, completing by midnight IST on 17 November 2026.
Home
Routing
Use the SMC Client to configure static or dynamic routing, and use a Multi-Link configuration
to manage and distribute inbound and outbound connections.
Configuring routing and antispoofing
Routing defines through which next hop router the Security Engine forwards traffic from a source address to a destination address. Antispoofing
defines which addresses are considered valid source addresses for the networks connected
to each interface.
About this Help
This online help was created for Forcepoint Network Security Platform , version 7.5.0 .
Introduction to the Forcepoint Network Security Platform solution
Before setting up Forcepoint Network Security Platform , it is useful to know what the different components do and what engine roles are
available.
Deployment
Before you can set up the system and start configuring elements, you must consider
how the different SMC components should be positioned and deployed.
Setting up
After deploying the SMC components, you are ready to start using the SMC Client and carrying out some
of the first configuration tasks.
Monitoring
You can use the SMC to monitor system components and third-party devices. You can also view and filter
logs, and create Reports from them.
Controlling Security Engine s
You can command and set options for engines through the SMC Client or on the engine
command line. You can also stop traffic manually.
SMC configuration
SMC Manager configuration allows you to customize how the SMC components work.
Security Engine configuration
You can create and modify Engines, IPS engines, Layer 2 Engines, Master Engines and
Virtual Security Engine s. You can configure the Security Engine properties, activate optional features, and configure advanced Security Engine settings.
Routing
Use the SMC Client to configure static or dynamic routing, and use a Multi-Link configuration
to manage and distribute inbound and outbound connections.
Configuring routing and antispoofing
Routing defines through which next hop router the Security Engine forwards traffic from a source address to a destination address. Antispoofing
defines which addresses are considered valid source addresses for the networks connected
to each interface.
Getting started with routing
To understand how the Security Engine reads routing definitions, look at the network interfaces in the routing or antispoofing
configurations.
Routing configuration overview
Routing configuration involves adding a default route, adding routes to networks
that are not directly connected, and adding routes to networks that can be reached
through route-based VPNs.
Add routers
A Router element represents a next-hop gateway’s IP address in routing configurations.
Add or view the default route
You can check which route is currently set as the default route for traffic leaving
the Security Engine and set a new default route.
Add static routes
You can add a static route to a network in the routing configuration.
Using metrics or ECMP on multiple routes to the same destination
You can configure multiple routes through different next hop gateways to the same
destination.
Configure Forced Next Hop routing
The Forced Next Hop option can be used to force forward traffic to a specific tunnel,
or next hop IP address overriding normal routing.
Configure policy routing
Policy routing allows you to route traffic based on both source and destination IP
address. Policy routing is useful when you want to configure a different route for
a destination based on the source address.
Configuring multicast routing
The Security Engine supports static multicast, IGMP-based multicast forwarding (IGMP proxying), and multicast
routing using protocol-independent multicast (PIM). You can also configure dynamic
multicast routing using the Free Range Routing (FRR) Suite on the command line.
Configure DHCP message routing
The engine can relay DHCP messages. If DHCP messages are routed through the engine
(from a network segment to some other, isolated segment), you must enable DHCP relay
on the engine interface properties for the interface where the DHCP requests are originating
from (client’s network).
Check routes using the Route Query tool
The Route Query tool allows you to check where packets with a certain IP address
are routed according to the current definitions. You can check that the routing is
correct and quickly find a particular branch in the Routing tree.
Remove static routes
New networks are automatically added to routing when you change the properties of
an interface. However, the Networks are not automatically removed, so you must check
the routing configuration for obsolete entries and remove them manually.
Modifying antispoofing
IP address spoofing is an attack where the source IP address in a packet is changed
to gain unauthorized access or to cause a denial-of-service. Such attacks can be prevented
with antispoofing rules.
Examples of routing configuration
The SMC provides features that allow you to configure many routing scenarios.
Configuring dynamic routing
With dynamic routing, Security Engine s automatically change their routing when the network topology changes. The Security Engine s can also exchange information about appropriate routing paths.
Outbound traffic management
You can use Multi-Link to distribute outbound traffic between multiple network connections
and to provide high availability and load balancing for outbound traffic.
Inbound traffic management
Inbound traffic management ensures that services remain available even when one or
more servers or NetLinks fail, and balances the load of incoming traffic
more efficiently between a group of servers. Inbound traffic management is not supported
on Layer 2 Engines or on layer 2 physical interfaces on Engines.
Dynamic link selection
When you use Multi-Link for outbound traffic management or Multi-Link VPNs, Forcepoint Network Security Platform in the Engine/VPN role can dynamically select the NetLink or VPN link that best
matches the quality requirements of traffic.
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic
and inspecting the content of traffic.
Users and authentication
User accounts are stored in internal databases or external directory servers. You
can use Forcepoint Network Security Platform in the Engine/VPN role or external authentication servers to authenticate users.
Virtual private networks
Forcepoint Network Security Platform supports both policy-based and Route-based Tunnels between VPN gateways. For full
remote access, Forcepoint Network Security Platform supports both IPsec and SSL VPN tunnels for VPN clients.
Maintenance and upgrades
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting
Troubleshooting helps you resolve common problems in the Forcepoint Network Security Platform and SMC .
Appendices
Configuring routing and antispoofing
Routing defines through which next hop router the Security Engine forwards traffic from a source address to a destination address. Antispoofing
defines which addresses are considered valid source addresses for the networks connected to each interface.
Getting started with routing
To understand how the Security Engine reads routing definitions, look at the network interfaces in the routing or antispoofing configurations.
Routing configuration overview
Routing configuration involves adding a default route, adding routes to networks that are not directly connected, and adding routes to networks that can be reached through route-based VPNs.
Add routers
A Router element represents a next-hop gateway’s IP address in routing configurations.
Add or view the default route
You can check which route is currently set as the default route for traffic leaving the Security Engine and set a new default route.
Add static routes
You can add a static route to a network in the routing configuration.
Using metrics or ECMP on multiple routes to the same destination
You can configure multiple routes through different next hop gateways to the same destination.
Configure Forced Next Hop routing
The Forced Next Hop option can be used to force forward traffic to a specific tunnel, or next hop IP address overriding normal routing.
Configure policy routing
Policy routing allows you to route traffic based on both source and destination IP address. Policy routing is useful when you want to configure a different route for a destination based on the source address.
Configuring multicast routing
The Security Engine supports static multicast, IGMP-based multicast forwarding (IGMP proxying), and multicast routing using protocol-independent multicast (PIM). You can also configure dynamic multicast routing using the Free Range Routing (FRR) Suite on the command line.
Configure DHCP message routing
The engine can relay DHCP messages. If DHCP messages are routed through the engine (from a network segment to some other, isolated segment), you must enable DHCP relay on the engine interface properties for the interface where the DHCP requests are originating from (client’s network).
Check routes using the Route Query tool
The Route Query tool allows you to check where packets with a certain IP address are routed according to the current definitions. You can check that the routing is correct and quickly find a particular branch in the Routing tree.
Remove static routes
New networks are automatically added to routing when you change the properties of an interface. However, the Networks are not automatically removed, so you must check the routing configuration for obsolete entries and remove them manually.
Modifying antispoofing
IP address spoofing is an attack where the source IP address in a packet is changed to gain unauthorized access or to cause a denial-of-service. Such attacks can be prevented with antispoofing rules.
Examples of routing configuration
The SMC provides features that allow you to configure many routing scenarios.