Technical Articles ID:
KB90960
Last Modified: 9/14/2021
Environment
McAfee Web Gateway (MWG) 8.x
Summary
Recent updates to this article
Date
Update
September 14, 2021
Added release information for 8.2.23.
August 12, 2021
Added WP-4043 and release information for 8.2.22.
June 14, 2021
Added WP-3868 and release information for 8.2.21.
May 11, 2021
Added release information for 8.2.20.
April 16, 2021
Added release information for 8.2.18 and 8.2.19.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Contents
Click to expand the section you want to view:
MWG Version
General Availability (GA)
Release Notes
8.2.23
September 14, 2021
MWG 8.2.x Release Notes NOTE: 8.2.x release notes are cumulative, so information about new releases is provided in this document.
8.2.22
August 10, 2021
8.2.21
June 14, 2021
8.2.20
May 11, 2021
8.2.19
April 15, 2021
8.2.18
March 15, 2021
8.2.17
February 16, 2021
8.2.16
January 12, 2021
8.2.15
December 18, 2020
8.2.14
December 8, 2020
8.2.13
October 13, 2020
8.2.12
September 8, 2020
8.2.11
August 19, 2020
8.2.10
August 11, 2020
8.2.9
July 14, 2020
8.2.8
June 9, 2020
8.2.7
May 12, 2020
8.2.6
April, 14, 2020
8.2.5
March 10, 2020
8.2.4
February 11, 2020
8.2.3
January 14, 2020
8.2.2
November 12, 2019
8.2.1
October 8, 2019
8.2.0
September 10, 2019
8.1.5
August 13, 2019
MWG 8.1.x Release Notes NOTE: 8.1.x release notes are cumulative, so information about new releases is provided in this document.
8.1.4
July 2, 2019
8.1.3
June 11, 2019
8.1.2
May 14, 2019
8.1.1
April 9, 2019
8.1
March 12, 2019
8.0.3
February 12, 2019
MWG 8.0.x Release Notes NOTE: 8.0.x release notes are cumulative, so information about new releases is provided in this document.
8.0.2
January 8, 2019
8.0.1
November 13, 2018
8.0.0
October 9, 2018
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
Reference Number
Related Article
Found in
MWG
Version
Resolved in
MWG
Version
Issue Description
WP-4043
8.2.22
Issue: You cannot log in to the MWG GUI by using any external managed admin account. Logging in using the local admin account still works.
The following setting is disabled: Accounts > Administrator accounts are managed externally.
If you enable the setting again and save your changes, it is disabled again after some minutes.
Workaround: Use the local admin account.
WP-3868
8.2
Issue: You disable the Enabled Openers rule set and configure the Gateway Anti-Malware Engine as Avira only.
But Avira does not detect specific or modified eicar files inside the archive.
Workaround: Open MWG Policy, under Common Rules, enable the Enable Opener Rule set.
WP-1872
8.2
8.2.1
Issue: In ProxyHA or Transparent Router mode, when a node previously marked Director is set as Scanner and the configuration is saved, the resulting node fails to become a Scanner node. The hastats tool shows this node as Redundant Director instead of Scanning node.
Workaround: When a node previously marked as Director is to be changed as Scanner.
Set the director priority to 0 and set as scanner node. Save the changes.
Log on to the MWG back-end of the corresponding node and execute the command service haproxy stop.
Configure the IP in the HTTP and FTP proxy listeners as 0.0.0.0:<port>.
For example, change 192.168.20.10:9090 to 0.0.0.0::9090.
Save changes.
Solution: Upgrade to 8.2.1.
WP-1870
8.2
8.2.1
Issue: Transparent Router Mode plus IP-spoofing Performance drops. In transparent router mode, if IP spoofing is enabled, a high response time (>250 ms) and connection error is observed.
Workaround:
Perform the following steps every time any proxy-related configuration is updated from the GUI-based manager.
Locate and open in a text editor of your choice the file /etc/haproxy/haproxy.cfg.
Search for the string frontend fwd_proxy.
Under that block, after the line bind <ip>:<port> accept-proxy transparent, enter the new line maxconn 50000.
For example: bind 192.168.20.150:80 accept-proxy transparent
maxconn 50000
Repeat this process for each instance of the stringfrontend fwd_proxy, adding the new line under the accept-proxy transparent entry.
Save and close the file.
Restart the service. Typeservice haproxy restartand press Enter.
WP-1866
8.2
8.2.1
Issue: In transparent router mode, when only the HTTP proxy is enabled and IP spoofing is enabled only for HTTP traffic, the HTTP connection fails with a 502 error. Workaround: Enable the FTP proxy. Enable the FTP port redirects and FTP listener configuration at the same time.
WP-2033
8.2
8.2.2
Issue: MWG 8.2 does not support configuring Transparent proxy in Bridge mode.
Existing customers using transparent bridge mode in older releases are advised to not upgrade to the latest version.
Solution: This feature is supported in MWG 8.2.2 and later.
WP-1813
8.2
8.2.1
Issue: In 8.2, the bandwidth throttling feature in router mode is not fully supported. Using the feature in the router mode might not throttle the traffic according to the configuration. Existing customers using this feature in transparent router mode in older releases, are advised to not upgrade to the latest version.
1265798
8.0.3
8.0.3.1
8.0.4
Issue: You see a kernel panic when you reboot MWG. During the reboot, MWG stops and displays Kernel Offset and Kernel Panic errors. Workaround: Reboot MWG again.
Issue: Unable to log on to the MWG manager (UI). Solution: See the related article.
1256856
Issue: You can't paste text when you use the Webswing user interface with the Edge browser. You press Ctrl+V, the paste fails, and you see the following error:
SCRIPT5007: Unable to get property 'getData' of undefined or null reference webswing-embed.js (145,464897)
Issue: When you update MWG from a version earlier than 7.7.2.14 or with the AV rollback flag (ud-rollbackGAM2015) enabled, MWG 8.0 can't load the old GAM2015 libraries. Instead, it downloads the new engine in the background. This process can take several minutes, depending on your download speed. Users see the error:
Cannot Load Anti-Malware Engine The Anti-Malware engine could not be loaded and your administrator doesn't allow to deliver content without being checked for viruses.
Please call your administrator with the error message below.
Solution: Do not redirect traffic to MWG before the AV engine has finished all updates. You can view the update status in the MWG dashboard.
Reference Number
Related Article
Issue Description
WP-2823
Issue: In HAProxy mode, when using the Virtual IP (VIP) address, the settings for connection timeouts configured in event enable proxy control are ignored.
The HAProxy only relates to general timeout settings.
Workaround: Increase the general timeout settings in MWG or increase the timeout on the remote site.
WP-3055
Issue: You intermittently see an antimalware engine update error: [AV] [UpdateFailed2] Error updating the Antivirus engine. Reason: 'Error starting engine 'McAfee Gateway Anti-Malware', error code: 5'."
You also see that service restarts take upwards of 40 minutes rather than the expected 5.
1256688
Issue:Spanport Automation stops receiving information from the ICAP server. You can't view log entries in access.log on the spanport proxy.
