Access Control Rules for Bi-Directional Connections

VPN connections typically involve forward connections, which are initiated by a user to a client/server resource. However, if you deploy SonicWall’s network tunnel clients (Connect Tunnel or OnDemand Tunnel) to your users, bi-directional connections are enabled.

With the SonicWall VPN, bi-directional connections encompass:

• Forward connections from a VPN user to a client/server resource. See Adding Access Control Rules for a Forward Connection.

• Reverse connections from a client/server resource to a VPN user. An example of a reverse connection is an SMS server that “pushes” a software update to a user’s machine. See Adding Access Control Rules for a Reverse Connection.

• Cross-connections refer specifically to VoIP (Voice over Internet Protocol) applications that enable one VPN user to telephone another VPN user. Cross-connections require a pair of access control rules: one for the forward connection and one for the reverse connection. See Adding a Pair of Access Control Rules for a Cross-Connection.

Other examples of bi-directional connections include an FTP server that downloads files to or uploads files from a VPN user, and remote Help Desk applications.