Mike E

12:54 strongSwan Bug #2315: FreeBSD server stops routing new connections after 16k connects/disconnects: I'm looking at implementing some code to re-use freed reqids. Are there any known pitfalls that need to be considered...

10:41 strongSwan Bug #2315: FreeBSD server stops routing new connections after 16k connects/disconnects: Nothing at all was logged by the kernel.
09:19 strongSwan Bug #2315: FreeBSD server stops routing new connections after 16k connects/disconnects: This is what it looks like when a failed connection is up:...

23:55 strongSwan Bug #2315 (Closed): FreeBSD server stops routing new connections after 16k connects/disconnects: After cycling through 16k 'ipsec up' and 'ipsec down' commands from the client, the server will stop establishing com...
23:29 strongSwan Bug #2313: 5.5.2 client fails to connect after 256 connections using freebsd 11: Works great, thanks!

17:05 strongSwan Bug #2313: 5.5.2 client fails to connect after 256 connections using freebsd 11: Hi Tobias,
The freebsd tun driver has the ability to return the lowest unused tun device by opening "/dev/tun" (s...
14:04 strongSwan Bug #2313 (Closed): 5.5.2 client fails to connect after 256 connections using freebsd 11: FreeBSD Strongswan client fails to connect after 256 ipsec up/ipsec down commands.
Using latest version from port...

14:39 strongSwan Issue #2303: reload of letsencrypt certs causing connection issues: I've confirmed that was the issue (private key not existing for the cert). Running @ipsec rereadsecrets@ after the re...
13:43 strongSwan Issue #2303: reload of letsencrypt certs causing connection issues: Ok, that makes sense. I'll test to make sure that works. I wonder if that could explain why the old cert doesn't get ...
13:24 strongSwan Issue #2303: reload of letsencrypt certs causing connection issues: The way I'm doing is is replacing the old file (leftcert and its key) and then issuing a reload without touching ipse...

Also available in: Atom

strongSwan