Skip to content

ipsec: elaborate on PSK gotcha #886

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
swhite2 merged 1 commit into from
May 28, 2026
Merged

ipsec: elaborate on PSK gotcha #886

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions source/manual/how-tos/ipsec-s2s-conn-route.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,9 +135,19 @@ Id **hostB** **hostA**

.. Note::

Secrets for both ends need to be added to ":menuselection:`VPN->IPsec->Pre-Shared Keys`", site A needs a secret
set for local identifier :code:`hostB`. Optionally one may also set a second (remote) identifier in which case the secret
belongs to these two identifiers.
A pre-shared key needs to be added to ":menuselection:`VPN->IPsec->Pre-Shared Keys`". Set :code:`hostA` for
local identifier and :code:`hostB` for remote identifier.

While the remote identifier is optional, keep in mind that not specifying it will make this PSK elligible to
be used for different connections using the same local ID as well. It is generally recommended to
be as specific as possible.


.. Tip::

If you have an ID specified in the Remote Authentication grid in a connection, then this connection
now expects the other end to identifiy itself with this ID. Make sure this reflects reality, as some
systems do not allow you to set a specific ID and can default to their local IP address instead.

.....................
Children
Expand Down