NETGEAR FVS318N Firewall Firmware

Fixes:

- Not able to browse the web pages if traffic meter disabled when switching connection between FVS318N AP and FVS318N LAN interface connected APs.
- WAN second IP can't work normally in firewall rule.
- After adding a customer SSID profile about Default VLAN, LAN host PC can't get IPv6 address by RADVD.
- WAN is not getting up after upgrade from 4.3.0.19.img to 4.3.1-22.img in classical routing mode.
- Outbound traffic is not following the configured bandwidth limit.
- Wireless radio page is showing wrong transmit power values when transmit power settings is Full/Half/Quarter/Eighth/Minimum for all regions.
- Fixed SSL VPN ActiveX certificate expired.

Known Issues and Limitations:

- Unable to add IP address or network in by source IP address page.
- Observed inconsistent behavior with voice traffic when server is lying in LAN and DMZ side.
- Device showing blank certificate when subject name is having successive comma.
- For the port speeds 10Base T FULL_Duplex and 100Base T FULL_Duplex, the duplex setting is showing as half.
- [CLI]Able to add 2 mode config records with same pool start IP and end IP.
- Device is accepting same Local and Remote LAN IP in manual tunnel.
- When "Disable Ping Reply on LAN Ports" is enabled the WAN IP of router is not reachable from the LAN host.
- No NAT translation of SIP headers during REGISTER, outbound call and SDP.
- There is no validation for SIIT Address field.
- IPv6 IPSec client tunnel is not getting establish in main mode.
- Device is not accepting the static route for the network 0.0.0.0 on LAN or VLAN interface.
- [IPv6]Unable to run IPERF-UDP and FTP traffic from LAN to WAN on SIIT tunnel.
- Stun packets are getting drop in SIP module.
- Device IPv6 WAN is not getting RADvD IP address when Router's MAC Address is configured for "Use this computer's MAC Address" or "Use this MAC Address".
- [CLI]There are no proper validations for the domain name in CLI.
- [CLI]schedules are not getting edited properly from CLI.
- Able to see wireless logs with "local wireless" tag and with "kernal kernal" tag.
- After Successful connection through WPS PIN method, status message is not correct.