Скачать драйвер для Netgear FVX538v1 Firmware 3.0.2-21

Before upgrading, write down all the configuration information you changed from the defaults. You may need to reenter them later. These typically include password, security settings and ISP configuration.

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:

* Guest login view HTTP source to see ISP settings such as password.
* GRC Scan report show port as Steacth even when it is open
* PPPoE: MTU only works for default value
* DynDNS does not work: auth type is case senstive.
* VPN tunnels went down and cannot be re-esteablished even after reboot. The only way to recover is to delete and rebuild IKE and VPN policies.
* Using a script to constantly connect and disconnect PPPoE would cause box to crash.
* Send box's own email logs through VPN tunnel
* PPPoE: MTU only works for default 1492 value
* DHCP Reservation not working in v2.1.1-22
* Oray DDNS: if web service authentication failed because of wrong account name or password, FVX538/FVS338 should not
automatically reconnect.
* Provide an option to log visited web sites by DNS name and IP address.
* VPN Performance dropped significantly in version 2.1.2-7
* PPPoE line: can not configure outgoing firewall using "NAT IP = Single Address"
* Protocol Bindings Rules lost after reboot
* PPTP/PPPoE idle timeout not work
* Syslog default level.
* Disabled protocol bindings did not get saved into config. file
* Config file corrupt: v2.1.2-7 config file restore to v2.1.3-17
* Moscow Time zone issue
* Wrong SysUpTime when device is queried by ProSafe NMS via SNMP.
* Guest login can see XAUTH password in "Edit IKE Policy" page
* Provide an option to configure a DNS server to be provided through DHCP to local PCs
* Wrong SysUpTime when device is queried by ProSafe NMS via SNMP.
* VPN user name cannot contain &
* IKE Policy: preshared key does not support &
* Some of the 70 portforwarding rules works and some don't
* Click on "current IP address" on WAN2 ISP settings web page will show WAN1 status mistakenly.
* DMZ DHCP, by default the lease time is 0 hours, should be 24
* When connected by ADSL, DNS cannot resolve any internet addresses.The Routing table seems to be lacking WAN of info
* extra space chars in DNS logs which looks misaligned
* After cable unpluged, WAN State still shows as "UP"
* CSRF fix caused login issue if there is a NAT box in front to port-forward HTTPS mgmt traffic to the WAN port of FVX538.
* NAT IP should be grayed out if outbound rule is "block always".
* PPPoE line: cannot configure outgoing firewall rule using "NAT IP = Single Address" if NAT IP is not in the same subnet as WAN interface IP.
* Added details in [INVALID_PACKET] log messages.
* Changes for WAN selection dropdown box in outbound firewall rule for NAT IP.
* When "Block TCP flood" is enabled, Remote HTTPS Management does not work, this applies to 3.0.2-9 and 3.0.2-16.
* Firmware upgrade sometimes failed.


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.

Примечание: Ссылка "скачать" может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.