The selector on both sides is the other sides dynamic domain name.
Noel Kuntze skrev
>What's the selector for the PSK?
>
>On 27.06.2017 00:25, Dusan Ilic wrote:
>> Yep, the hostname are resolving to the right IP. Obviously Fortigate
>> implementation has no problems reconnecting, tho
What's the selector for the PSK?
On 27.06.2017 00:25, Dusan Ilic wrote:
> Yep, the hostname are resolving to the right IP. Obviously Fortigate
> implementation has no problems reconnecting, though Strongswan has.
>
>
> Den 2017-06-27 kl. 00:10, skrev Noel Kuntze:
>> "Strongswan won't connect ev
Yep, the hostname are resolving to the right IP. Obviously Fortigate
implementation has no problems reconnecting, though Strongswan has.
Den 2017-06-27 kl. 00:10, skrev Noel Kuntze:
"Strongswan won't connect even manually." What does that mean?
No secret found? Is the IP correct?
On 27.06.201
"Strongswan won't connect even manually." What does that mean?
No secret found? Is the IP correct?
On 27.06.2017 00:05, Dusan Ilic wrote:
>
> Anyone...?
> I had to reboot the remote Strongswan gateway a couple of hours later, then
> it came back up again.
>
>
> Den 2017-06-19 kl. 08:51, skrev Dus
Anyone...?
I had to reboot the remote Strongswan gateway a couple of hours later,
then it came back up again.
Den 2017-06-19 kl. 08:51, skrev Dusan Ilic:
Yet again, the fortigate router reconnected to Strongswan on it's own
without manual intervention 12 minutes after the other sides public
Yet again, the fortigate router reconnected to Strongswan on it's own
without manual intervention 12 minutes after the other sides public IP
changed... Strongswan won't connect even manually.
Den 2017-06-19 kl. 08:47, skrev Dusan Ilic:
Okey, today it happened again, new IP on one end of tunn
Okey, today it happened again, new IP on one end of tunnel and updated
in DNS. Pinging the new IP from both sides shows it resolves correctly,
restarting Strongswan on both sides and the same issue as before. (last
time it started to work on the evening same day)
generating IKE_SA_INIT request
Hi,
I have a S2S IPsec tunnel setup that have problems now when one side of
the tunnel have been assigned a new public IP. The hostname used have
been immediately updated by way od dynamic DNS, and the TTL have expired
two hours ago. When trying to up the tunnel on the side with the changed
I
