** Package changed: strongswan (Ubuntu) => xl2tpd (Ubuntu)
** Summary changed:
- no shared key found in 22.04
+ xl2tpd "Can not find tunnel" in jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195
Thanks for the heads up, gregrwm. As Lucas and Simon said, it would be
great if you could provide:
- The configuration files for both sides (client and server), with
proper obfuscation in place. ipsec.conf and ipsec.secrets are a good
start.
- The log files for both sides, with obfuscation in p
i've gained access to the "ER-X" which receives my connection at the
colo, if you want info from it just ask.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951832
Title:
no shared key found in 22.0
For some reason, strongswan can't find the PSK to use for the connection
as hinted in:
no shared key found for '1.i.p.2'[1.i.p.2] - '2.i.p.7'[2.i.p.7]
no shared key found for 1.i.p.2 - 2.i.p.7
Can you share the strongswan-starter logs? Maybe it will explain what's
wrong with the ipsec.secrets.
I
yes. focal on HD, vs a jammy iso, connecting to the same colo
("right"). i'm less familiar with the details at the colo, other than
the focal config i have on my end works for it. with some difficulty i
could likely get more details about the colo config.
sorry the description above didn't show
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
AFAIU both, your systems running Focal and Jammy, are connection to a
VPN that you already have set up, am I right? If yes, could you please
share the config you used to set it up? In this way, we could try to
reproduc
