Item | Description | Bug ID |
|---|---|---|
1. | The exporter port 46000 was accessible through the Management IP address, and as a result it appeared in the vulnerability scan. | DE66269 DE66270 |
2. | An Internal out-of-sync configuration was detected. | DE68007 DE68008 |
3. | In an HA environment, after the backup device rebooted, FTP data sessions disappeared intermittently on the backup device. | DE68025 |
4. | Config sync failed with EC certificates in the configuration. | DE68185 |
5. | After user-defined ciphers, the Application Services engine was not synchronized with the current configuration. | DE68191 DE68192 |
6. | After user-defined ciphers, the Application Services engine was not synchronized with the current configuration. | DE68220 DE68221 |
7. | When the MRST flag was set to on, it was not possible to disable a data port. | DE68251 DE68254 |
8. | A port disabled in a saved configuration needed to be toggled twice to bring it up after reboot. | DE68268 DE68271 |
9. | On an Alteon VA platform, sometimes resource allocation was not working correctly when the VA was deployed with multiple cores but with a disabled multi-queue for the image. | DE68277 DE68280 |
10. | Alteon forwarding or routing packets without SRC MAC translation led to a MAC flap issue. | DE68296 DE68297 |
11. | Using the WBM, after creating a vADC, the vADC stayed in the init state. | DE68399 DE68402 |
12. | Alteon responded to Non-RFC compliant responses for DNS requests. | DE68405 DE68406 DE68409 |
13. | When the WANlink server was operationally disabled and then re-enabled, the WANlink peak statistics were incorrect. | DE68438 DE68439 DE68442 |
14. | Using APSolute Vision, newly created vADCs were not manageable. | DE68610 DE68613 |
15. | Password Strength not available in WBM but was available in the CLI. | DE68777 DE69778 DE68781 DE68783 |
16. | After upgrading to version 32.6.5.0, vADCs could not be managed by the APSolute Vision server. | DE68791 DE68794 |
17. | On an Alteon 5424 (ODS-LS2) platform, the real server capacity in standalone and ADC-VX modes was increased in 8192. | DE68844 DE68847 |
18. | A software panic occurred followed by an AX Out-of-sync. | DE68880 DE68881 |
19. | Was not enable to sync the configuration between devices in the beta code. | DE68912 DE68914 DE68915 |
20. | Issue with FQDN servers. Logs were added to help with this issue. | DE68928 DE68931 |
21. | A panic occurred with a loss of the configuration. Fixed included not tracing empty DNS responses. | DE68944 DE68947 |
22. | The SIP INVITE went to the wrong real server. | DE68967 DE68968 DE68971 |
23. | Received the following error: Configuration Error column slbCurCfgEnhContRuleBotMProcessing not found For the fix, removed an unneeded entry that was ported by mistake. | DE69120 DE69121 DE69124 |
24. | During the tunnel handling routine, Alteon reboots with IP fragmented traffic. | DE69174 DE69177 |
25. | BM JS injection occurred when no BM was configured. | DE69197 DE69200 |
26. | While configuring CNTCLSS values, a maximum length validation failure did not display the correct error. | DE69507 |
Item | Description | Bug ID |
|---|---|---|
1. | AppWall blocked requests when Host protections (CSRF/URL Rewrite/Redirect validations) had the “Inherit” status. | DE67920 |
2. | Debug log added to link the Source Blocking scoring and the related security event. | DE66587 |
3. | Wrong IP blocked with Source Blocking. | DE68383 |
4. | Wrong host displayed in syslog security event. | DE68396 |
5. | Wrong hostname displayed in the Forensics security events when blocked by the Application Security policy. | DE68487 |
6. | In specific scenarios, AppWall restarted when the Host protector was in Inherit mode. | DE70250 |