Netgear FVS336G Firmware 2.2.0-59

• 
• Download Netgear FVS336G Firmware 2.2.0-59

Netgear FVS336G Firmware 2.2.0-59 description

OSSupport:Windows Size:13.4 MB
NETGEAR has been a worldwide provider of technologically advanced, branded networking products since 1996. Our mission is to be the preferred customer-driven provider of innovative networking solutions for small businesses and homes.Overview: Initial Release FirmwareKnown Issues : 1. Dropped packets are not logged thought Netgear FVS336G Firmware 2.2.0-59 matches firewall rule with log option turns on. 2. Admin and guest login from WAN are enabled by default 3. Disabling remote management will disable SSL VPN 4. Vonage incoming call form WAN rings, but no voice 5. VPN rollover does not work if both WAN interfaces are on the same subnet (not common) 6. Inbound rule with second public address on a different subnet from WAN interface address does not work if the traffic is initiated from a host directly on Netgear FVS336G Firmware 2.2.0-59 subnet (Not common, normally there is a router inbetween and that works). 7. In Load Balancing mode, a host directly connected to WAN port can ping WAN1, not WAN2. (not a common case, normally there is a router inbetween and that works.) 8. In load balancing mode, SSL VPN user directly connected to WAN port can establish VPN tunnel to WAN1, not WAN2. (not a common case, normally there is a router inbetween and that works.) 9. Login page is not displayed properly if if admin comes in via FVX538 inbound rule to login to the WAN port of FVS336G. (Netgear FVS336G Firmware 2.2.0-59 is a common deployment case). 10. Host names in SSL port forwarding cannot mix upper and lower case letters. 11. SSL VPN denial policy does not block ping traffic unless the high port number is blank. 12. SSL VPN global policy edit button does not display Service on the edit web page (The work-around is to delete the policy and recreate Netgear FVS336G Firmware 2.2.0-59). 13. The change password option should be grayed out if SSL VPN user is authenticated via Active Directory, Radius or LDAP. It has no effect. 14. Port forwarding https port 443 via a secondary public WAN IP in inbound rule cannot reach internal web server (The work-around is to use SSL VPN to access internal web server). 15. PPPoE auto-detect displays No service detected, although it has already acquired WAN IP address and is functioning. 16. When adding a SSL VPN resource, the IP address is not part of the configuration and is only availabe from edit button. 17. Raritan KVM client through SSL Port Forwarding gets disconnected after being idle for a while (The work around is to use SSL VPN tunnel instead of Port Forwarding).

Netgear FVS336G Firmware 2.2.0-59 Tag: