Bug Fixes
- Fixed the issue where the web interfaces are vulnerable to SQL injection, HTTP header injection, and Cross-Site Scripting.
- Fixed the issue where the logs are not displayed properly in the GUI and on Syslog server.
- Fixed the issue where the GUI does not display the L2TP active users.
- Fixed DHCP relay issues.
- Fixed the issue where the IPsec VPN is disconnecting from the client even when the IPsec VPN tunnel shows as established with the Fortigate Firewall.
- Fixed the issue where the Firewall Rules do not work when MAC Filtering is enabled and a MAC address is added.
- Fixed the issue when a schedule is set to "Daily or Weekly", and the time to 12:00 AM, it always switched back to 1:00 PM.
- Fixed an issue for client to gateway VPN, in changing WAN IP as Local Identifier in IPsec settings.
- Fixed the issue where the firewall logs contain incomplete logs messages.
- Fixed the issue where the device is vulnerable to CVE-2012-5958 and CVE-2012-5959.
- Fixed the issue when using wizard configuring, remote IP has .0 in fourth octet which is not allowed.
Known Issues and limitations:
- [CLI]Device is accepting start IP address is larger than end IP address in IPv6 Address pool table.
- Device is not accepting mode config pool IPs for a specific range of addresses through CLI.
- Not able to change to IPv4/IPv6 dual mode through CLI.
- Unable to login to the device GUI after configuring custom portal as default.
- Device is not showing prefix length for IPv6 WAN address in router status and WAN setup page.
- Sometimes TELNET session to the device is not accessible.
- List of services of server group are not displaying in CLI show command.
- Device is not showing proper error message while performing ping and trace route when the
selected local gateway WAN is down. - Device is showing error "IP subnet conflicting with WAN1" while adding multi-homing IP address
when WAN ISP type is PPPoE/PPTP. - Opened ports are getting closed when we make changes to other rules in Port Triggering page.
- Device WAN not able to connect with the Windows PPTP server.
- Not able to establish IPv6 SSL-VPN tunnel from java based browsers with java 8 update 20 version.
- Unable to run the FTP traffic from Filezilla client over SSL Port forwarding tunnel in the Windows7 64 bit host.
- Unable to establish Port forwarding tunnel from Windows7 64 bit IE9 browser.
- [SSL VPN] tunnels establishment failed for Windows 8.1 64 bit IE11 browser.
- Link detection processes are seen for WAN3 and WAN4 also but device is having only WAN1 and WAN2.
- Observed critical error when we click on trace route option, if ping though VPN tunnel is selected.
Note:
- Supports 50 VoIP phone calls.
- Supported characters: `~!#$&*()-+|\;:' " < > and space. Restricted these characters in password fields due to security reasons [to avoid the SQL attacks etc.,].
Installation Instructions:
- Using the Download Link below, download and extract the new firmware to a convenient place such as your desktop.
Download Link: http://www.downloads.netgear.com/files/GDC/FVS318GV2/FVS318Gv2_V4.3.4-1.zip
Note: Reboot the firewall before beginning the update process. - Select Administration > Settings Backup and Firmware Upgrade from the main/submenu.
- In the Router Upgrade section, click Browse.
- Locate the downloaded file and click Upload.
This will start the software upgrade to your VPN firewall. This may take some time. Do not interrupt the upgrade process.
At the conclusion of the upgrade, your firewall will reboot.
Last Updated:10/17/2025
|
Article ID: 31022