From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem with ipsec tool from Marcus Mueller
Date: Thu, 27 Mar 2003 19:35:48 +0000 [thread overview]
Message-ID: <marc-lartc-104879382405763@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104879333605092@msgid-missing>
David,
Sorry, wrong list! Please try the FreeS/WAN list.
http://www.freeswan.org/freeswan_trees/freeswan-1.5/doc/mail.html
-Martin
: I am trying to connect road-warriors (running on WinXP) to my home network
: via FreeS/WAN but it does not work.
: I am using version 1.99 with "plutodebug=all" set in the config but it does
: not give any output when I try to connect.
:
: The client is behind a router in network 192.168.20.0/24, the server is on
: "my-servers-dns-name" with the internal network 192.168.11.0/24
:
: When I did "ping 192.168.11.1", it said "IP Sicherheit wird verhandelt"
: which means "Negotiating IP security" but the packet logger which was
: running on the client's router did not log any traffic from/to the server so
: it seems that WinXP did not attempt to contact the server. The syslog on the
: server of course also did not show anything about connection attempts.
: Do you have any idea why this happens?
:
: Here are the configs:
:
: - Config on the client:
:
: conn roadwarrior
: left=%any
: right=my-servers-dns-name
: rightca="C=AT, S=xx, L=xx, O=xx, CN=xx"
: network=auto
: auto=start
: pfs=yes
:
: conn roadwarrior-net
: left=%any
: right=my-servers-dns-name
: rightsubnet\x192.168.10.0/24
: rightca="C=AT, S=xx, L=xx, O=xx, CN=xx"
: network=auto
: auto=start
: pfs=yes
: ---------------------
:
: - Log on the client
: No RAS connections found.
: IPSec Version 2.1.4 (c) 2001,2002 Marcus Mueller
: Getting running Config ...
: Microsoft's Windows XP identified
: Host name is: pc1
: LAN IP address: 192.168.20.1
: Setting up IPSec ...
:
: Deactivating old policy...
: Removing old policy...
:
: Connection roadwarrior:
: MyTunnel : 192.168.20.1
: MyNet : 192.168.20.1/255.255.255.255
: PartnerTunnel: my-servers-dns-name
: PartnerNet : my-servers-dns-name/255.255.255.255
: CA (ID) : C=AT, S=xx, L=xx, O=xx, CN...
: PFS : y
: Auto : start
: Auth.Mode : MD5
: Rekeying : 3600S/50000K
: Activating policy...
:
: Connection roadwarrior-net:
: MyTunnel : 192.168.20.1
: MyNet : 192.168.20.1/255.255.255.255
: PartnerTunnel: my-servers-dns-name
: PartnerNet : 192.168.11.0/255.255.255.0
: CA (ID) : C=AT, S=xx, L=xx, O=xx, CN...
: PFS : y
: Auto : start
: Auth.Mode : MD5
: Rekeying : 3600S/50000K
: Activating policy...
: ---------------------------
:
: - Config on the server:
:
: config setup
: interfaces=%defaultroute
: klipsdebug=none
: plutodebug=all
: plutoload=%search
: plutostart=%search
: uniqueids=yes
:
: conn %default
: keyingtries=1
: compress=yes
: disablearrivalcheck=no
: authby=rsasig
: leftrsasigkey=%cert
: rightrsasigkey=%cert
:
: conn roadwarrior-net
: leftsubnet\x192.168.11.0/24
: also=roadwarrior
:
: conn roadwarrior
: right=%any
: left=%defaultroute
: leftcert=gatewayKey.pem
: autod
: pfs=yes
:
: ------------
:
: I hope that you can help me
: Regards,
: David
:
: PS: I don't want to connect both routers, I want that only the single client
: has access.
:
: _______________________________________________
: LARTC mailing list / LARTC@mailman.ds9a.nl
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-27 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 19:27 [LARTC] Problem with ipsec tool from Marcus Mueller David Hellekalek
2003-03-27 19:35 ` Martin A. Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-104879382405763@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.