1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Multiple bugs with QuickVPN an bugs in the WRVS4400Nv2

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by streg, May 12, 2009.

  1. streg

    streg Guest

    Originally posted in linksys forums: this post.

    I couldn't find a bug reporting system and decided to post this also here. Maybe someone reads one of these forums :)

    I've been struggling with Client VPN on WRVS4400Nv2 (fw. V1.00.09-ETSI) and the QuickVPN 1.2.11 software.

    The problem was, that I couldn't connect to the router with QuickVPN (the classic "Remote gateway not responding" error). I found a way to debug from the command line from experts-exchange.com. So here goes...

    This is what I found:

    If I used the 123456789.dnsalias.net (number represent the lenght not the real hostname) the client didn't work, but once I changed to using the IP address it worked. The reason seem to be, that the server address in ipsec is LIMITED TO 16 CHARACTERS or it should be an IP address.

    The command string with problems when running "c:\Program Files\Linksys\Linksys VPN Client>ipsec -debug":

    NetshCommandStr = netsh advfirewall consec add rule name="IPsec_Tunnel" endpoint1= endpoint2= action=requireinrequireout description="IPsec Tunnel" mode=tunnel enable=yes profile=any type=static localtunnel= remotetunnel=123456789.dnsalirequireinrequireout auth1=computerpsk auth1psk=kNF7askq2ghhkFDbcp5h qmsecmethods=esp:md5-3des+60min+50000kb,esp:sha1-3des+60min+50000kb,esp:md5-aes128+60min+50000kb,esp:sha1-aes128+60min+50000kb qmpfs=mainmode

    As you can see the server address is truncated to just "123456789.dnsali". The generated ipsec.conf-file has the whole address. The QuickVPN FRONTEND for the console program should do it's job correctly.

    1. so that's the first bug.

    2. is that the client doesn't give ANY errors from that part of the execution, but only later when the ping doesn't work.

    Bugs with the router so far:

    1. Cant view logs from https remote admin

    2. ftp port forwarding to buffalo nas doent work with IPS off. ??? (I know ftp is not secure, but had to use it since VPN didn't work)

    3. Can't enable port forwarding settings from https remote admin, and sometimes my TCP selection magically changes to UDP or Both when I apply settings.

Share This Page