Release Note for Vigor3912 Series

Firmware Information

Firmware Version: 4.4.3.5

Release Type: Important – Review release notes and upgrade if the changes affect your system stability, performance, or security

Applied Models: Vigor3912, Vigor3912S

New Features

• None.

Improvement

• Corrected: An issue with a router reboot due to the Web GUI.
• Corrected: An issue with manual time zone configuration for Athens.
• Corrected: An issue with missing Chinese interface after firmware update.
• Corrected: An issue with missing tab formatting in some CLI help menu items.
• Corrected: An issue where an IP could not be added to the DoS Flood block list.
• Corrected: Unexpected reboots caused by Slab Panic / SOCK_DYNA_BUF errors.
• Corrected: An issue where a single quote in the IP Group name broke the QoS page.
• Corrected: An issue where "Unknown WAN" was displayed in the VigorACS server.
• Corrected: A compatibility issue between the SMS Service Object and BulkSMS.com.
• Corrected: An issue where the Vigor3912 Web UI was not reachable via virtual WAN IP.
• Corrected: A reboot issue when both WCF and DNS Filters were enabled during unstable Internet connections.
• Corrected: An issue where the router became non-responsive every few days due to the anti-DoS queue being full.
• Corrected: An issue with Virtual WAN PPPoE dial-up failure when a VLAN tag overlapped with physical WAN.
• Corrected: An issue where the Remote Dial-In VPN backup configuration could not be restored from Vigor2927 to Vigor3912.
• Corrected: A router reboot issue after Web login using 2FA due to broken 2FA configuration in the previous firmware. It is necessary to regenerate the 2FA settings after upgrading to the new firmware.
• Corrected: An issue with random firmware upgrade failures occurred via VigorACS when an "Always On" OpenVPN tunnel existed.
• Corrected: An issue where the Web UI crashed when the IP Group name under Object Setting >> IP Group contained a comma.
• Corrected: An issue where LAN Access with IP Object - Range Type could not block VPN from accessing the router's management interface.
• Improved: Automatically deleted the "cpu_busy.tar" file during debug log generation if it was over one month old, to speed up log downloads.
• Corrected: An issue where the router no longer attempted to establish a VPN connection if the DNS server responded to the VPN Server's domain name with TTL=0.

Known Issue

• At present, DrayOS5 AP is not supported by Vigor3912.