Untitled

config setup
        nat_traversal=yes
        charonstart=yes
        plutostart=yes
        plutodebug=all
        plutostderrlog=/tmp/pluto.log
        virtual_private=%v4:10.0.0.0/8,%v4:192.168.0.0/16,%v4:172.16.0.0/12,%v4:25/8

conn L2TP-PSK
        authby=psk
        pfs=no
        rekey=no
        keyexchange=ikev1
        compress=no
        left=%defaultroute
        leftprotoport=17/1701
        rightprotoport=17/1701
        rightsubnet=vhost:%no,%priv
        leftfirewall=yes   
        right=%any
        installpolicy=yes
        rightauth=psk
        leftauth=any 
        auto=add



|   3d 48 09 81
| peer client is 192.168.77.5
| peer client protocol/port is 17/1701
| our client is 119.x.x.x
| our client protocol/port is 17/1701
| find_client_connection starting with L2TP-PSK
|   looking for 119.x.x.x/32:17/1701 -> 192.168.77.5/32:17/1701
|   concrete checking against sr#0 192.168.2.169/32 -> 0.0.0.0/32
|   fc_try trying L2TP-PSK:119.x.x.x/32:17/1701 -> 192.168.77.5/32:17/1701 vs L2TP-PSK:192.168.2.169/32:17/1701 -> 0.0.0.0/32:17/1701
|   fc_try concluding with none [0]
|   fc_try L2TP-PSK gives none
|   checking hostpair 192.168.2.169/32 -> 0.0.0.0/32 is found
|   fc_try trying L2TP-PSK:119.x.x.x/32:17/1701 -> 192.168.77.5/32:17/1701 vs L2TP-PSK:192.168.2.169/32:17/1701 -> 0.0.0.0/32:17/1701
|   fc_try concluding with none [0]
|   fc_try_oppo trying L2TP-PSK:119.x.x.x/32 -> 192.168.77.5/32 vs L2TP-PSK:192.168.2.169/32 -> 0.0.0.0/32
|   fc_try_oppo concluding with none [0]
|   concluding with d = none
"L2TP-PSK"[2] 87.y.y.y:4500 #1: cannot respond to IPsec SA request because no connection is known for 119.x.x.x/32===192.168.2.169:4500[192.168.2.169]:17/1701...87.y.y.y:4500[192.168.77.5]:17/1701===192.168.77.5/32
"L2TP-PSK"[2] 87.y.y.y:4500 #1: sending encrypted notification INVALID_ID_INFORMATION to 87.y.y.y:4500