Dear all,
I am using strongswan-4.2.8, I have a question want to check you, does this
version have support IP range like 192.168.2.3-192.168.2.233 when set to
left|right side?
If not does any one have an idea to implement it?
Best Regards
Chester Chen�虺鲁�包
无锡研勤信息科技有限公司
Software Department 1
Hi all,
I am running StrongSwan 4.6.1 in Debian 6.0.3.
There is one IKEv1 conn and one IKEv2 conn. The IKEv1 cipher suites:
ike=aes128-md5!
esp=aes128-md5!
pfs=yes
The IKEv2 cipher suites are almost identical except IKE has dh-group:
ike=aes128-md5-modp1536!
esp=aes128-md5!
The IK
Hello all,
I have been part of this list for maybe the last 6 months or so and have learn
a few things from the on going discussions.
Finally I have my own issue, which has been an issue for my setup since I
configured it.
My GW is configured with IKEv2 PSK and I can authenticate without any
Hi,
I had a working strongswan setup (4.4.1 from debian repository).
Recently I had to upgrade the kernel version of the server because of a
tiers software.
Since this upgrade tunnels just don't work that good and randomly fail
to keep up.
Is there anything I have to do (like recomplie strongsw
Oh, I noticed that the xl2tpd.log is wrong, it shows the state of a local
connection :/
This is right:
using channel 31
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
sent [LCP ConfReq id=0x1 ]
rcvd [LCP ConfReq id=0x1
]
sent [LCP ConfRej id=0x1 ]
rcvd [LCP ConfAck id=0x1
Hi,
I need some help with StrongSwan 4.5.2 and xl2tpd 1.3.1 (the latter is from
the Debian unstable repository, but I also tried 1.2.7 and 1.3.0):
I have setup an IPsec/L2TP connection for use with Android, following
various guides throughout the internet and reading the StrongSwan wiki.
H
Hi Eric,
> However, when I specify a port value in the protoport designations (E.g.
> leftprotoport=tcp/0 + rightprotoport=tcp/3260 OR leftprotoport=6/0 +
> rightprotoport=6/3260 OR leftprotoport=tcp/any +
> rightprotoport=tcp/3260), the IKE authentication fails due to a traffic
> selector mismatc
Hi,
> When I try to add 'leftcert', I can no longer use PSK.
Well, what's the point of defining a certificate if you want to use a
pre-shared secret for authentication?
>conn %default
> ...
> leftcert=host_domain_tld.pem
> leftid=@host.domain.tld
>
> This gives me the follo
On Tue, 07 Feb 2012 16:44:41 +0200, Turbo Fredriksson wrote:
>conn %default
> ...
> leftcert=host_domain_tld.pem
>
> [...]
>
>"C=SE, O=Bayour.COM, OU=System, CN=host.domain.tld,
> E=tu...@bayour.com" %any : PSK "aNothEERseCreT"
And if I try to connect, this is what I get in th
I'm trying to setup the usage of certificates etc with strongSWAN, but
there might be something I've missed.
I have had my own CA for many years, genererating working certificates
for a bunch of services (ldaps, https, etc).
When I try to add 'leftcert', I can no longer use PSK.
conn %
10 matches
Mail list logo