22
submitted 4 days ago by [email protected] to c/[email protected]

09[IKE] DH group ECP_256 unacceptable, requesting ECP_256

internet-delenda-est

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 2 points 4 days ago

no, in fact I gave up on IPSec since I posted this and have started working on a wireguard setup because fuck this unmaintained pile of shit

[-] [email protected] 3 points 4 days ago

It can be easier to find help with wireguard setups. I hope you succeed.

I learned how to do IPsec by using a perfectly functional example config in one room and changing things one tiny step at a time until it got where I needed it. IPsec can be very stable and simple but you gotta have your ducks in a row first.

[-] [email protected] 2 points 4 days ago* (last edited 4 days ago)

well, the worst part is I had a functioning IPsec site-to-site setup as well as road warrior configuration, running on OpenWRT 19. but now after upgrading to OpenWRT 24, I can't get it to work again. they redid the whole config system and moved away from ipsec to swanctl and the user-layer part of the IPSec subsystem in OpenWRT appears to have been barely maintained through the upgrade path

[-] [email protected] 3 points 4 days ago

Yeah the last five years have been very bad for open source projects. If you can justify the move to pfsense it’s very worth it to get away from projects that are maybe getting too far out over their skis.

I’m in the process of doing this with a handful of tomato derivative running old edge devices that never got replaced.

this post was submitted on 30 May 2025
22 points (95.8% liked)

technology

23791 readers
288 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS