Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

SynFloodProtection sets initial Window Size to 0 on Connections opened from Internal Devices in NSX-v (54527)

Last Updated: 7/28/2018Categories: InformationalTotal Views: 5653Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

SynFloodProtection sets initial Window Size to 0 on Connections opened from Internal Devices.

Purpose

This article provides explanation on the behavior when SynFloodProtection is enabled in the NSX Edge.

Resolution

Edge is using SYNPROXY target to implement SynFloodProtection. The workflow is:

Mark the initial SYN from the client as UNTRACKED, and direct it to the SYNPROXY target.

The SYNPROXY target responds with a SYN/ACK containing a cookie and encoded options such as window scaling factor, SACK perm, etc into the timestamp, if the timestamps are used (similar with TCP). Notice that the window size of this response is set to 0, also it is UNTRACKED sent to the client.

When the SYNPROXY target (Edge) sends a window 0 to the client, it blocks further data transferring before it validates the cookie.

In SYNPROXY target, when the final ACK from the client is received, the cookie is validated, the original options extracted and a SYN to the original destination (server) is generated. This SYN is using the advertised window size from the final ACK and the options from initial SYN.

This SYN is not sent as UNTRACKED, so that from conntrack point of view, the client instantiates a new connection to the server.

The original destination (server) responds SYN/ACK to SYNPROXY target, then a final ACK for the original destination (server) is generated.

A window update with the window size announced by the original destination (server) is sent to the client. When the validation is passed, a window update is sent to the client to open the data transferring.

From this point, the connection is handled off to conntrack as a normal process.

Note: The above behavior might cause poor applications performance on the application startup, especially if the Edge is connected to a 3rd party load balancer. The loadbalancer will interpret Window size 0 as per the TCP standard which states that a sender must pause after receiving a win size 0.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant