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

FTP traffic sometimes may not match the NSX-T FTP DFW rule (76130)

Last Updated: 12/30/2019Categories: InformationalTotal Views: 6727Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The following conditions are met

NSX-T environments running versions earlier than NSX-T Data Center 2.5.0

A DFW FTP rule has been created to allow FTP Traffic

FTP traffic is seen to match the default rule or another rule below the configured FTP rule. If this is a drop rule, FTP traffic will be dropped

The FTP application is using Extended Passive Mode when sharing the dynamic FTP port with the Client, as can be seen in this sample packet capture

11:40:13.693223 00:50:56:a6:7a:13 > 00:50:56:ad:f2:12, ethertype IPv4 (0x0800), length 114: 192.168.10.12 > 192.168.10.50.43982: Flags [P.], seq 271:319, ack 143, win 114, options [nop,nop,TS val 1193338955 ecr 2358453075], length 48: FTP: 229 Entering Extended Passive Mode (|||48561|)

Cause

FTP protocol uses an architecture with two channels of communication. First a control connection is established on port 21.
Then depending on the mode, Client and Server exchange a dynamic port which they use for a parallel data channel.
In Passive mode, the FTP server sends the Client both the server's IP address and dynamic port on which it is listening.
In Extended Passive Mode (EPSV), the FTP server sends only the dynamic port number, as seen in the sample packet capture above.
Due to this software issue when Extended Passive Mode is used, the ALG rule will match the control connection but may fail to learn the the dynamic port and so will not match the data channel traffic.

Resolution

This issue is resolved in NSX-T Data Center 2.5.0

Workaround

Configure the FTP application to use standard Passive mode instead of Extended Passive Mode
or
Add another DFW allow rule to allow the high port dynamic traffic between FTP Client and Server

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)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant