pfSense

Seems something broke in latest 2.5.0 dev. Configuring ipsec p1 using aes-128-gcm and xcbc leads to this:

Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 09[CFG] added vici connection: bypass
Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 09[CFG] installing 'bypass'
Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 15[CFG] vici client 25 requests: load-conn
Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 15[CFG] conn con1000:
Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 15[CFG] algorithm 'aes128gcm' not recognized
Dec 22 16:49:10 fra-pfSense charon⁹⁶⁹⁸³: 09[CFG] vici client 25 disconnected

and this:

[2.5.0-DEVELOPMENT][root@fra-pfSense]/usr/local/etc/swanctl/conf.d: swanctl --list-conns
bypass: IKEv1/2, no reauthentication, rekeying every 14400s
local: %any
remote: 127.0.0.1
local unspecified authentication:
remote unspecified authentication:
bypass: PASS, no rekeying
local: 10.9.0.34/32|/0
remote: 10.9.0.34/32|/0

Switching to aes seems to fix it:

[2.5.0-DEVELOPMENT][root@fra-pfSense]/usr/local/etc/swanctl/conf.d: swanctl --list-conns
bypass: IKEv1/2, no reauthentication, rekeying every 14400s
local: %any
remote: 127.0.0.1
local unspecified authentication:
remote unspecified authentication:
bypass: PASS, no rekeying
local: 10.9.0.34/32|/0
remote: 10.9.0.34/32|/0
con1000: IKEv2, no reauthentication, no rekeying
local: [redacted]
remote: [redacted]
local public key authentication:
id: [redacted]
certs: CN=[redacted]
remote public key authentication:
cacerts: CN=ipsec-ca
con1000: TUNNEL, rekeying every 3600s
local: 0.0.0.0/0|/0
remote: 0.0.0.0/0|/0

There is also a duplicate p1 proposal (see attachment) and neither allows selection of a key strength (so you're stuck to 128 bits).