NETGEAR FVX538 ProSafe VPN Firewall Firmware 7 description

Operating System:Windows 98SE/ME/2000/XP , 7.06 Mb
NETGEAR FVX538 ProSafe VPN Firewall Firmware 2.1.0-7 Windows 98SE/ME/2000/XP.
Bug Fixes:
DHCP IP Assignment doesnt change from low to highLogs need to be emailed if they become fullDisable QoS priority option if block always action is chosenRIP MD5 password need to allow shorter than 16 char RFC2453WAN health/failure detection in Load Balancing - options to select Ping, DNS or None, and also retry count and interval.If we need to support FQDN in Load balancing mode, we need DynDNS support for both WAN interfaceFQDN name containing dash will fail to add the VPN policyHttps inbound rule and remote management are not allowed at same time.Fail to add a service name with 16 charWAN fails to connect to PPPoE lineLoad Balancing mode can not work for same subnetLog PPPoE, PPPTP, and dial-up idle timeout events when WAN status logging is enabled.Need to be able to create overnight schedulesWhen login after idle timeout previous IP address is displayed.VPN client can not establish tunnel if inbound rule UDP port 500 is configured. A warning message will be issued.GUI does not display correct image if restore a config file.System up time is incorrect during high volume of traffic.ActiveX not blocked if Cookie blocking is enabledSpaces not allowed in user names in local user database (for Xauth)pfkey message is lost due to too many SAsneed to turn off logging of NetBIOS broadcastsRemote Management failsTest period and failover after should be grayed out if WAN health/fail detection is noneProblems with port forwarding when wan mode is set to load balancingRemove Trend Micro LinkWAN port is not responding after upgrade to version 2.x Prior to upgrade, same configuration works fine.option to enable/disable logging of broadcastsBeta site reported that there are no notes in the help window for the new VPN auto roll over featureNeed to add help text for load-balancing health detection and new logging options in firewall logs.New 2007 Daylight Saving Time (DST) implementation.WAN IP can be set to IP:192.168.2.0 MASK:255.255.255.0 (host portion is ZERO, NETGEAR FVX538 ProSafe VPN Firewall Firmware 2.1.0 7 Windows 98SE ME 2000 XP should be an invalid address)LAN IP can be set to IP:192.168.1.0 MASK:255.255.255.0 (host portion is ZERO, NETGEAR FVX538 ProSafe VPN Firewall Firmware 2.1.0 7 Windows 98SE ME 2000 XP should be an invalid address), this cause lost control to DUTPinging from PC1 to PC2 but there is no reply. (Static Routes)Once login name has errors such as space, user cannot log in anymore until a reboot is issued to recover. A space in user name is now reported as an error.After restoring a config file, can not switch from WAN1 only to Load Balancing mode. Get an error invalid configuration. This has been addressed by disabling the Load Balancing option to disallow the user to enter invalid configuration when either WAN1 or WAN2 is configured with idle-timeout option.The numbers of auto roll-over tests do not work precisely, addressed by preventing user from entering invalid config.PPPoE LED stays ON when the PPPoE idle time reaches. This happens not often. Most time, LED displays correct behavior.System Uptime is mismatched between SNMP and web GUIUnknown error message in DHCP Logs.Need restarting WAN log messageSNMP timeoutCopyright is displayed incorrectly in Chinese.New documentation web link due to TrendMicro removal.VPN between FVS114 and FVX538 initially works fine, but once FVS114 is rebooted and acquired a new IP address, tunnel status is up, but traffic cannot go through.Earlier firmware allows only 8 users to be added in User DatabaseFVX538v2 - DYNDNS will not be updated after 30 daysSwitch between static IP and DHCP would cause require ISP loginOccasionally the old firmware crashes at boot up.VPN doesn’t work on WAN2problems with port forwarding when wan mode is set to load balancingLPD protocol on TCP port 9100 and RDP protocol on TCP port 3389 work poorly through VPNsBroadband connection repeatedly drops the WAN interface after dialup backup has been initiated.Customer reported VPN policy loss if there are special characters in VPN preshare key.SSL performance was poor.Account name field inactive.The dial-up connection takes several minutes to establish the ISP connection vs. less than a minute in v1.xDial-up default timeout is 30 seconds.Fixed some MTU handling issues.TCP session timeout is changed to 20 minutes; and UDP changed to 3 minutes.
1. Download NETGEAR FVX538 ProSafe VPN Firewall Firmware 2.1.0 7 Windows 98SE ME 2000 XP and save it to PC hard disk.
2. Run NETGEAR FVX538 ProSafe VPN Firewall Firmware 7 2.1.0 and it will install automatic.
3. Reboot your computer to finish your NETGEAR FVX538 ProSafe VPN Firewall Firmware 7 installation.