Skip to main content

Best practices for SonicWall VPN Tunnel configuration

There are some factors that we need to consider when we setup Site to Site VPN Tunnel with SonicWall Firewall.
If we forgot to conside these factors, we will encounter frequent connection drop on your Tunnel. (e.g. RDP connection timeout)
Below are those we should consider when we setup VPN Tunnels with SonicWall.

1) TCP Timeout
TCP Connection Inactivity Timeout value of SonicWall and other Firewalls are 15 minutes by Default.
In real world, this value can make your RDP connection drop frequently.
So, Firewall Tech Support are recommended to set the TCP Timeout Value from 30minutes to 60minutes.
Higher TCP Timeout Value are inviting some unnecessary security threats and that's why we should only allow for specific connection in your Policy-Based VPN Tunnels or Route-Based VPN Tunnels.

2) Packet Fragmentation
As RDS is a streaming protocol, packet fragmentation should be avoided.
Almost all Firewall including SonicWall has Fragmented Packet Handling and Ignore DF (Don't Fragment) Bit options.
Tech Support are recommended to enable Fragmented Packet Handling option and disable Ignore DF (Don't Fragment) Bit option.

3) Path Maximum Transmission Unit (Path MTU or PMTU)
As described above, fragmentation of the RDP streaming protocol is undesirable and should be avoided.  The most common cause of such fragmentation is incorrect Maximum Transmission Unit (MTU) values for the traffic's path.
Default MTU value of SonicWall is 1500 Bytes. But we cannot use 1500 Bytes fully as 56 Bytes for Cyptographic overhead and size of used protocols header too. For example, we need to subtract 28 Bytes if we are using IP+ICMP. So, MTU Size will be (1500-56-28=1416 Bytes)
If you want to know how to find MTU settings of your host, pleas read this Article as I am lazy to write. :D
If you want to know how to change MTU settings on your host, please read this Article.

4) Bandwidth Management
Limitation of Bandwidth on Internet connection also is common cause of streaming protocol performance problems.
So, it is recommend to configure Real Time Bandwidth Management Rule for your end to end host connection.

5) Security Services
Security services including Gateway Anti-Virus (GAV), Anti-Spyware (AS) and Intrusion Prevention Service (IPS) are scan specific traffic types (e.g. SMTP, FTP, etc.) or the whole TCP stream for threats.  Whilst they are very efficient in terms of scanning speed, they do introduce some additional latency (typically at least 1ms) and cause dropped RDS connections when applied to the whole TCP stream.
Assuming that the end-points are sufficiently trusted, it is worth considering disabling the firewall's scanning services (at least AS and IPS) to obtain best RDS performance and connection reliability.
But we have to tighten end point security in our host as Firewall Security Services are bypass for these host.

Well. The above are things that we need to consider when we setup VPN Tunnels with SonicWall.
These facts are also usefule to reference for setting up VPN Tunnels on other Firewalls although I write for SonicWall.

Have a good day.
(Be knowledgeable, pass it on then)

Comments

  1. I am truly impressed by the details that you have provided regarding Firewall Security It is an interesting blog for me as well as for others. Thanks for sharing such a blog here.

    ReplyDelete
  2. You can also check this one and can share your opinions on IT consultant London

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...