Программы для ВконтактеNetgear FVX538v2 Firmware 2.1.0-7
- Размер: 7.1 MB
- ОС: Win All
- Имя файла:
FVX538v2 cannot use firmware 1.6.42 or earlier, it will render the router inoperable.
NOTE: The router will reset itself to factory defaults after upgrading to version 2.x.
Version 1.x and 2.x configurations are not compatible and cannot be used across software versions.
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.
Known Issues:
* Configuration file generated with this firmware version can't be loaded in older firmware versions.
* In Auto-failover, if primary is configured with an idle timeout, please ensure that the timeout value is greater than the WAN failure detection time, so that failover to the secondary is successful.
* If a device is configured for WAN2 Primary with Auto-Failover using an earlier firmware version, then after an upgrade, this setting will be lost and the user will have to reconfigure this setting.
* Configuring a WAN with idle timeout when WAN mode is Load Balancing is now reported as an erroneous configuration. So the customers upgrading from such a configuration should either switch WAN mode to "Dedicated Mode" or switch the WANs to "Keep Connected" to avoid loss of WAN configuration across the upgrade.
* Excessive logging could hang the system. Please disable log options that could log every packet.
* Hash (#) and Hyphen (-) character is not supported as a 1st character for user name field in admin, guest and VPN Client user.
* Colon (:) and Space ( ) characters are not supported for user name in admin/guest and VPN Client user.
* Double Quote character (") is not supported in the following fields in add/edit IKE policy page.
1. Policy Name.
2. Identifier.
3. Pre-shared key.
4. Username.
5. Password.
* Double Quote character (") is not supported in the following fields in add/edit VPN policy page. a.
1. Policy Name.
2. FQDN.
3. Key-In.
4. Key-Out.
* Double Quote (") characater is not supported in the following fields in VPN Wizard page.
1. Connection Name.
2. pre-shared key.
3. Remote WAN's IP Address or Internet Name.
4. Local WAN's IP Address or Internet Name.
* pipe (|) character is not supported as the last character in the following password fields.
1. admin password.
2. guest password.
3. VPN Client password.
4. WAN ISP password.
5. DDNS password.
* When dialup timeout is reached, connection is disconnected. However, if there is self-generated traffic such as syslog, email logs, IKE, NTP, or DNS proxy, dial-up connection will be re-established.
It is highly recommended to always use the most recent driver version available.
Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.
Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.
Примечание: Ссылка "скачать" может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.
NOTE: The router will reset itself to factory defaults after upgrading to version 2.x.
Version 1.x and 2.x configurations are not compatible and cannot be used across software versions.
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.
Known Issues:
* Configuration file generated with this firmware version can't be loaded in older firmware versions.
* In Auto-failover, if primary is configured with an idle timeout, please ensure that the timeout value is greater than the WAN failure detection time, so that failover to the secondary is successful.
* If a device is configured for WAN2 Primary with Auto-Failover using an earlier firmware version, then after an upgrade, this setting will be lost and the user will have to reconfigure this setting.
* Configuring a WAN with idle timeout when WAN mode is Load Balancing is now reported as an erroneous configuration. So the customers upgrading from such a configuration should either switch WAN mode to "Dedicated Mode" or switch the WANs to "Keep Connected" to avoid loss of WAN configuration across the upgrade.
* Excessive logging could hang the system. Please disable log options that could log every packet.
* Hash (#) and Hyphen (-) character is not supported as a 1st character for user name field in admin, guest and VPN Client user.
* Colon (:) and Space ( ) characters are not supported for user name in admin/guest and VPN Client user.
* Double Quote character (") is not supported in the following fields in add/edit IKE policy page.
1. Policy Name.
2. Identifier.
3. Pre-shared key.
4. Username.
5. Password.
* Double Quote character (") is not supported in the following fields in add/edit VPN policy page. a.
1. Policy Name.
2. FQDN.
3. Key-In.
4. Key-Out.
* Double Quote (") characater is not supported in the following fields in VPN Wizard page.
1. Connection Name.
2. pre-shared key.
3. Remote WAN's IP Address or Internet Name.
4. Local WAN's IP Address or Internet Name.
* pipe (|) character is not supported as the last character in the following password fields.
1. admin password.
2. guest password.
3. VPN Client password.
4. WAN ISP password.
5. DDNS password.
* When dialup timeout is reached, connection is disconnected. However, if there is self-generated traffic such as syslog, email logs, IKE, NTP, or DNS proxy, dial-up connection will be re-established.
It is highly recommended to always use the most recent driver version available.
Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.
Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.
Примечание: Ссылка "скачать" может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.
Идёт загрузка...