[Openswan Users] Shrew Soft VPN Client (freeware)

[Jacco de Leeuw]

Has anyone tried the Shrew Soft VPN Client for Windows 2000/XP?
It's freeware and has a lot of IPsec features, but for some
reason I can't get it to *not* use Mode-Cfg...

http://www.shrew.net/?page=software

Jacco

packet from 192.168.xx.yy:33738: received Vendor ID payload [Cisco-Unity]
packet from 192.168.xx.yy:33738: received Vendor ID payload 
[draft-ietf-ipsec-nat-t-ike-02_n] method set to=106
packet from 192.168.xx.yy:33738: received Vendor ID payload [RFC 3947] method 
set to=110
packet from 192.168.xx.yy:33738: ignoring unknown Vendor ID payload 
FRAGMENTATION 80000000]
packet from 192.168.xx.yy:33738: received Vendor ID payload [Dead Peer Detection]
"L2TP-PSK"[1] 192.168.xx.yy #2: responding to Main Mode from unknown peer 
192.168.xx.yy
"L2TP-PSK"[1] 192.168.xx.yy #2: transition from state STATE_MAIN_R0 to state 
STATE_MAIN_R1
"L2TP-PSK"[1] 192.168.xx.yy #2: STATE_MAIN_R1: sent MR1, expecting MI2 
                                 "L2TP-PSK"[1] 192.168.xx.yy #2: 
NAT-Traversal: Result using 3: peer is NATed 
"L2TP-PSK"[1] 192.168.xx.yy #2: transition from state STATE_MAIN_R1 to state 
STATE_MAIN_R2
"L2TP-PSK"[1] 192.168.xx.yy #2: STATE_MAIN_R2: sent MR2, expecting MI3 
                                 "L2TP-PSK"[1] 192.168.xx.yy #2: Main mode 
peer ID is ID_IPV4_ADDR: '192.168.aa.bbb'
"L2TP-PSK"[1] 192.168.xx.yy #2: switched from "L2TP-PSK" to "L2TP-PSK" 
                                 "L2TP-PSK"[2] 192.168.xx.yy #2: deleting 
connection "L2TP-PSK" instance with peer 192.168.xx.yy {isakmp=#0/ipsec=#0} 
 
                         "L2TP-PSK"[2] 192.168.xx.yy #2: I did not send a 
certificate because I do not have one.
"L2TP-PSK"[2] 192.168.xx.yy #2: transition from state STATE_MAIN_R2 to state 
STATE_MAIN_R3                    | NAT-T: new mapping 
192.168.xx.yy:33738/33739) 
            "L2TP-PSK"[2] 192.168.xx.yy #2: STATE_MAIN_R3: sent MR3, ISAKMP SA 
established {auth=OAKLEY_PRESHARED_KEY cipher=aes_128 prf=oakley_sha 
group=modp2048} 
       "L2TP-PSK"[2] 192.168.xx.yy #2: ignoring informational payload, type 
IPSEC_INITIAL_CONTACT
"L2TP-PSK"[2] 192.168.xx.yy #2: received and ignored informational message 
                                 "L2TP-PSK"[2] 192.168.xx.yy #2: received 
MODECFG message when in state STATE_MAIN_R3, and we aren't xauth client 
 
                         "L2TP-PSK"[2] 192.168.xx.yy #2: received MODECFG 
message when in state STATE_MAIN_R3, and we aren't xauth client 
 
                 "L2TP-PSK"[2] 192.168.xx.yy #2: received Delete SA payload: 
deleting ISAKMP State #2
"L2TP-PSK"[2] 192.168.xx.yy: deleting connection "L2TP-PSK" instance with peer 
192.168.xx.yy {isakmp=#0/ipsec=#0} 
                                                                packet from 
192.168.xx.yy:33739: received and ignored informational message

-- 
Jacco de Leeuw                         mailto:jacco2 at dds.nl
Zaandam, The Netherlands           http://www.jacco2.dds.nl