NETGEAR FVX538 ProSafe VPN Firewall Firmware driver 2.1.0-7 is a Network driver from NETGEAR. It runs on following
operating system:
Windows 98SE/ME/2000/XP
. We recommend always using the most recent driver version available, so check for NETGEAR FVX538 ProSafe VPN Firewall Firmware driver new verison
on our site as often as possible.
Do not forget to set a system restore point before installing NETGEAR FVX538 ProSafe VPN Firewall Firmware driver 2.1.0-7 driver, to avoid problems that may occurs when you install a
wrong driver, or for other OS version etc. If a problem occur than you may restore you computer to previous time, before installing the driver.
Publisher review:
Bug Fixes:
DHCP IP Assignment doesn't change from low to high
Logs need to be emailed if they become full
Disable QoS priority option if "block always" action is chosen
RIP MD5 password need to allow shorter than 16 char RFC2453
WAN 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 interface
FQDN name containing dash will fail to add the VPN policy
Https inbound rule and remote management are not allowed at same time.
Fail to add a service name with 16 char
WAN fails to connect to PPPoE line
Load Balancing mode can not work for same subnet
Log PPPoE, PPPTP, and dial-up idle timeout events when "WAN status" logging is enabled.
Need to be able to create overnight schedules
When 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 enabled
Spaces not allowed in user names in local user database (for Xauth)
pfkey message is lost due to too many SAs
need to turn off logging of NetBIOS broadcasts
Remote Management fails
Test period and "failover after" should be grayed out if WAN health/fail detection is "none"
Problems with port forwarding when wan mode is set to load balancing
Remove Trend Micro Link
WAN port is not responding after upgrade to version 2.x Prior to upgrade, same configuration works fine.
option to enable/disable logging of broadcasts
Beta site reported that there are no notes in the help window for the new VPN auto roll over feature
Need 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, this 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, this should be an invalid address), this cause lost control to DUT
Pinging 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 GUI
Unknown error message in DHCP Logs.
Need "restarting WAN" log message
SNMP timeout
Copyright 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 Database
FVX538v2 - DYNDNS will not be updated after 30 days
Switch between static IP and DHCP would cause "require ISP login"
Occasionally the old firmware crashes at boot up.
VPN doesn’t work on WAN2
problems with port forwarding when wan mode is set to load balancing
LPD protocol on TCP port 9100 and RDP protocol on TCP port 3389 work poorly through VPNs
Broadband 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.x
Dial-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.
Samsung finally gives consumers multiple audio streaming countries promised a while. Premium Music Hub allows users access to over 19 million songs, along with other useful functions.
IPhone\'s case came online in a few pictures that confirm rumors of a larger screen. This could be the first photos of the next iPhone, but nothing is really safe to Apple announcement.
After criticism received at Metro version of Internet Explorer 10 , initially offered no support for Adobe Flash technology, Microsoft has taken measures to correct this problem by working directly with Adobe to integrate the necessary components into the
Last year began to circulate on the Internet videos where Windows 8 systems boot in 7 seconds. Unfortunately, from this performance derives some problems.
NETGEAR FVX538 ProSafe VPN Firewall Firmware driver 2.1.0-7 details 
Before you Download
