<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top: 0px; margin-bottom: 0px;">Hi <span>Tobias,</span></p>
<p><br>
</p>
<p></p>
<p>Thank you for your reply.</p>
<p><br>
</p>
<p>If the case you mentioned has been fixed in 5.2.1, </p>
<p>the version <span>5.6.2</span> that I am running shoud have the fix.</p>
<p>And the symptom could be reproduced 100% even only initiate 5 tunnels.</p>
<p>What I concern about is that if there are only 5 users configured in ipsec.db,<br>
and initiate all the 5 ipsec tunnels,<br>
since the first initiator_id starts from "2", the last one with "6" stays at CONNECTING status and could not be established.</p>
<p>If further info is needed, please let me know.</p>
<p>----------------------------<br>
root@tester1:/usr/local/etc/ipsec.d# ipsec load-tester initiate 5 1000<br>
.+.+.+.+.<br>
^C<br>
root@tester1:/usr/local/etc/ipsec.d# ipsec statusall<br>
Status of IKE charon daemon (strongSwan 5.6.2, Linux 4.4.0-62-generic, x86_64):<br>
uptime: 29 seconds, since Feb 28 01:04:57 2018<br>
malloc: sbrk 1986560, mmap 0, used 731008, free 1255552<br>
worker threads: 10 of 16 idle, 6/0/0/0 working, job queue: 0/0/0/0, scheduled: 20<br>
loaded plugins: charon aes des rc2 sha2 sha1 md5 mgf1 random nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem fips-prf gmp curve25519 xcbc cmac hmac mysql sqlite attr load-tester kernel-netlink resolve socket-default
stroke vici updown eap-identity eap-sim eap-aka eap-aka-3gpp2 eap-simaka-sql eap-simaka-pseudonym eap-simaka-reauth eap-radius eap-tls eap-ttls xauth-generic counters<br>
Listening IP addresses:<br>
10.59.128.33<br>
10.64.127.253<br>
Connections:<br>
load-test: 192.168.0.6...0.0.0.0 IKEv1/2<br>
load-test: local: [strongswan.org] uses pre-shared key authentication<br>
load-test: remote: [*@strongswan.org] uses EAP_AKA authentication<br>
load-test: child: 10.65.0.0/18 === dynamic TUNNEL<br>
Security Associations (4 up, 1 connecting):<br>
load-test[5]: <span style="background-color: rgb(255, 255, 0);">CONNECTING</span>, 10.64.0.5[tester<span style="background-color: rgb(255, 255, 0);">6</span>@strongswan.org]...192.168.0.6[strongswan.org]<br>
load-test[5]: IKEv2 SPIs: 8b95a5331211a1c0_i* 9166956082d58c9a_r<br>
load-test[5]: IKE proposal: AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024<br>
load-test[5]: Tasks active: IKE_AUTH IKE_CERT_POST IKE_CONFIG CHILD_CREATE IKE_AUTH_LIFETIME<br>
load-test[4]: ESTABLISHED 17 seconds ago, 10.64.0.4[tester5@strongswan.org]...192.168.0.6[strongswan.org]<br>
load-test[4]: IKEv2 SPIs: 2c2989876540c256_i* 35538b752a34fd1b_r, rekeying in 6 hours<br>
load-test[4]: IKE proposal: AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024<br>
load-test{4}: INSTALLED, TUNNEL, reqid 4, ESP SPIs: c6338cd9_i 00176075_o<br>
load-test{4}: AES_CBC_128/HMAC_SHA1_96, 0 bytes_i, 0 bytes_o, rekeying in 7 hours<br>
load-test{4}: 10.254.32.5/32 === 10.65.0.0/18<br>
load-test[3]: ESTABLISHED 18 seconds ago, 10.64.0.3[tester4@strongswan.org]...192.168.0.6[strongswan.org]<br>
load-test[3]: IKEv2 SPIs: ba3fcb0ca5895aa2_i* a7d05578351da7e6_r, rekeying in 6 hours<br>
load-test[3]: IKE proposal: AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024<br>
load-test{3}: INSTALLED, TUNNEL, reqid 3, ESP SPIs: c25cd2d0_i 00118964_o<br>
load-test{3}: AES_CBC_128/HMAC_SHA1_96, 0 bytes_i, 0 bytes_o, rekeying in 7 hours<br>
load-test{3}: 10.254.32.4/32 === 10.65.0.0/18<br>
load-test[2]: ESTABLISHED 19 seconds ago, 10.64.0.2[tester3@strongswan.org]...192.168.0.6[strongswan.org]<br>
load-test[2]: IKEv2 SPIs: 94ee11eb3b5ca229_i* b0033ae63eff015c_r, rekeying in 6 hours<br>
load-test[2]: IKE proposal: AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024<br>
load-test{2}: INSTALLED, TUNNEL, reqid 2, ESP SPIs: cca6d612_i 00156d18_o<br>
load-test{2}: AES_CBC_128/HMAC_SHA1_96, 0 bytes_i, 0 bytes_o, rekeying in 7 hours<br>
load-test{2}: 10.254.32.3/32 === 10.65.0.0/18<br>
load-test[1]: ESTABLISHED 20 seconds ago, 10.64.0.1[tester<span style="background-color: rgb(255, 255, 0);">2</span>@strongswan.org]...192.168.0.6[strongswan.org]<br>
load-test[1]: IKEv2 SPIs: 8321948a132ef4d6_i* f476c99ea121d1b7_r, rekeying in 6 hours<br>
load-test[1]: IKE proposal: AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024<br>
load-test{1}: INSTALLED, TUNNEL, reqid 1, ESP SPIs: c113aae6_i 0013db54_o<br>
load-test{1}: AES_CBC_128/HMAC_SHA1_96, 0 bytes_i, 0 bytes_o, rekeying in 7 hours<br>
load-test{1}: 10.254.32.2/32 === 10.65.0.0/18<br>
root@tester1:/usr/local/etc/ipsec.d#<br>
------------------------</p>
<p>Regards,<br>
Li</p>
<p></p>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="width: 98%; display: inline-block;">
<div id="divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size: 11pt;"><b>发件人:</b> Tobias Brunner <tobias@strongswan.org><br>
<b>发送时间:</b> 2018年2月27日 9:35<br>
<b>收件人:</b> 李 冠群; users@lists.strongswan.org<br>
<b>抄送:</b> guanqun.li.ext@nokia.com<br>
<b>主题:</b> Re: [strongSwan] "%d" of initiator_id of load-tester does not start from 1 but 2.</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size: 11pt;">
<div class="PlainText">Hi,<br>
<br>
> I am facing a problem of load-tester that "%d" of initiator_id didnot<br>
> start from 1, but from 2.<br>
<br>
Yes, that's the case since 5.2.0 (since [1] to be exact). I pushed a<br>
fix to the load-tester-id branch. Is that really a problem, though?<br>
<br>
Regards,<br>
Tobias<br>
<br>
[1] <a id="LPlnk108779" href="https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=2cbaa632" previewremoved="true">
https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=2cbaa632</a><br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>