There are times I hate Windows this is one of them.
I had a working certificate-based system on my Win10 laptop. I haven't
used it in a while, and now it won't connect. My Android phone does,
using the StrongSwan app -- it's fine.
StrongSwan (on a FreeBSD host) is getting the connection req
Hi Karl,
> StrongSwan never gets this packet. I assume the problem here is the
> length mismatch, but not certain. What is certain is that StrongSwan
> never sees it; no matter how far up I turn the logging I never see any
> evidence of it being logged.
Sounds like an IP fragmentation issue (me
On 6/26/2017 10:46, Tobias Brunner wrote:
> Hi Karl,
>
>> StrongSwan never gets this packet. I assume the problem here is the
>> length mismatch, but not certain. What is certain is that StrongSwan
>> never sees it; no matter how far up I turn the logging I never see any
>> evidence of it being
On 6/30/2017 12:09, Karl Denninger wrote:
>
>
>
> On 6/26/2017 10:46, Tobias Brunner wrote:
>> Hi Karl,
>>
>>> StrongSwan never gets this packet. I assume the problem here is the
>>> length mismatch, but not certain. What is certain is that StrongSwan
>>> never sees it; no matter how far up I tur
Hi Karl,
> But now, when that certificate is selected, StrongSwan doesn't seem to
> want to *find* the certificate, even though it *does* verify as ok
> against the CA that issued it, and it's in the "certs" directory.
No need to put it there unless you actually reference it explicitly in
you
