D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: camattin on December 01, 2008, 11:15:49 PM
-
The company I work for uses the Jupiter Networks ssl vpn (all traffic is tunneled over https [tcp/443]). After upgrading to 1.21 it took nearly 2 minutes for the VPN to start itself and get fully connected. With 1.20 (and the MSBetaB39) I connect in just about 10-15 seconds.
There is nothing logged in the dlink's logs as to what may be happening here. I tried putting the work laptop in the DMZ, I tried with and w/o SPI firewall enabled, with and w/o traffic shaping... nothing seemed to make a difference.
Has anyone else seen this behavior??
-
Does the VPN keep a log?
One idea --
1. Turn off DNS Relay (known bug)
2. Set QOS Engine Automatic uplink speed test to manual and input an approximately correct speed (works around another known bug that complicates the first one)
3. Restart modem, wait for 60 seconds, restart VPN
If this helps, it's the DNS relay bug known in 1.21, probably trying to do reverse DNS lookups on its own host as part of its startup process. You can operate with it off permanently if you wish.