Wire Mode

Overview of Wire Mode

The Wire Mode improves connectivity by allowing existing connections to fail over successfully by bypassing firewall enforcement. Traffic within a VPN community is, by definition, private and secure. In many cases, the firewall and the ruleClosed Set of traffic parameters and other conditions in a Rule Base (Security Policy) that cause specified actions to be taken for a communication session. on the firewall concerning VPN connections is unnecessary. With the Wire Mode, the firewall can be bypassed for VPN connections by defining internal interfaces and communities as "trusted".

When a packet reaches a Security GatewayClosed Dedicated Check Point server that runs Check Point software to inspect traffic and enforce Security Policies for connected network resources., the Security Gateway asks itself two questions regarding the packet(s):

Is this information coming from a "trusted" source?

Is this information going to a "trusted" destination?

If the answer to both questions is yes, and the VPN CommunityClosed A named collection of VPN domains, each protected by a VPN gateway. to which both Security Gateways belong is designated as "Wire Mode enabled," stateful inspection is not enforced and the traffic between the trusted interfaces bypasses the firewall. Since no stateful inspection takes place, no packets can be discarded. The VPN connection is no different from any other connection along a dedicated wire. This is the meaning of "Wire Mode." Since stateful inspection no longer takes place, dynamic routing protocols (which do not survive state verification in non-wire mode configuration) can now be deployed. Wire Mode thus facilitates Route-Based VPN.

Wire Mode Scenarios

Wire mode can be used to improve connectivity and performance in different infrastructures. This section describes scenarios that benefit from the implementation of wire mode.

In this scenario:

  • Security Gateway M1 and Security Gateway M2 are both wire mode enabled and have trusted internal interfaces.

  • The community where Security Gateway M1 and Security Gateway M2 reside, is wire mode enabled.

  • Host 1, residing behind Security Gateway S1 is communicating through a VPN tunnel with Host 2 residing behind Security Gateway M1 .

  • MEP is configured for Security Gateway M1 and Security Gateway M2 with Security Gateway M1 being the primary Security Gateway and Security Gateway M2 as the backup.

In this case, if Security Gateway M1 goes down, the connection fails over to Security Gateway M2. A packet leaving Host 2 will be redirected by the router behind Security Gateway M1 to Security Gateway M2 since Security Gateway M2 is designated as the backup Security Gateway. Without wire mode, stateful inspection is enforced at Security Gateway M2 and the connection is dropped. Packets that come into a Security Gateway whose session was initiated through a different Security Gateway, are considered "out-of-state" packets. Since Security Gateway M2's internal interface is "trusted," and wire mode in enabled on the community, no stateful inspection is performed and Security Gateway M2 will successfully continue the connection without losing any information.

In this scenario:

  • Wire mode is enabled on Center Security Gateway C (without an internal trusted interface specified).

  • The community is wire mode enabled.

  • Host 1 residing behind Satellite Security Gateway A wishes to open a connection through a VPN tunnel with Host 2 behind Satellite Security Gateway B.

In a satellite community, Center Security Gateways are used to route traffic between Satellite Security Gateways within the community.

In this case, traffic from the Satellite Security Gateways is only rerouted by Security Gateway C and cannot pass through Security Gateway C's firewall. Therefore, stateful inspection does not need to take place at Security Gateway C. Since wire mode is enabled on the community and on Security Gateway C, making them trusted, stateful inspection is bypassed. Stateful inspection, however, does take place on Security Gateways A and B.

In this scenario:

  • Security Gateway A belongs to Community 1.

  • Security Gateway B belongs to Community 2.

  • Security Gateway C belongs to Communities 1 and 2.

  • Wire mode is enabled on Center Security Gateway C (without an internal trusted interface specified).

  • Wire mode is enabled on both communities.

  • Host 1 residing behind Satellite Security Gateway A wishes to open a connection through a VPN tunnel with Host 2 behind Satellite Security Gateway B.

Wire mode can also be enabled for routing VPN traffic between two Security Gateways which are not members of the same community. Security Gateway C is a member of both communities and therefore recognizes both communities as trusted. When host 1 behind Security Gateway A initiates a connection to host 2 behind Security Gateway B, Security Gateway C is used to route traffic between the two communities. Since the traffic is not actually entering Security Gateway C, there is no need for stateful inspection to take place at that Security Gateway. Stateful inspection, however, does take place on Security Gateways A and B.

Special Considerations for Wire Mode

Wire Mode does not work with IPv6.

Configuring Wire Mode

Wire mode is configured in two places:

  • Community Properties (Meshed or Star)

  • Security Gateway Properties

  1. In SmartConsoleClosed Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on., click the Objects menu > Object Explorer.

  2. From the left tree, select the VPN Communities.

  3. Open the VPN Community object.

  4. From the left tree, click Wire Mode.

  5. Select Allow uninspected encrypted traffic between Wire mode interfaces of the Community members.

  6. To enable Wire Mode Routing, select Wire Mode Routing - Allow members to route uninspected encrypted traffic in VPN routing configurations.

  7. Click OK.

  8. Install the Access Control Policy.

  1. In SmartConsole, from the left navigation panel, click Gateways & Servers.

  2. Open the applicable Security Gateway object.

  3. From the left tree, click IPsec VPN > VPN Advanced.

  4. In the Wire mode section:

    1. Select Support Wire Mode (and Wire mode routing - route uninspected encrypted traffic in VPN routing configurations).

    2. Click Add.

    3. Select the interfaces to be trusted by the selected Security Gateway.

    4. Click OK.

    5. Select Log Wire mode traffic to log the Wire Mode activity.

  5. Click OK.

  6. Install the Access Control Policy.