ting so we know.
>
> The second is to contribute configs and the like to the netperf repo
>
> https://github.com/gvnn3/netperf
>
> We take pull requests :-)
>
> Best,
> George
>
> On 3 Aug 2015, at 23:20, Sydney Meyer wrote:
>
>> Besides strongswan (act
> On 04 Aug 2015, at 02:18, John-Mark Gurney wrote:
>
> Sydney Meyer wrote this message on Mon, Aug 03, 2015 at 01:15 +0200:
>> the revision i built included gnn's patches to setkey already.
>>
>> I have tried to setup a tunnel using strongswan with gcm
testing a fix that
> should
> address this issue.
>
> Best,
> George
>
>
> On 3 Aug 2015, at 0:15, Sydney Meyer wrote:
>
>> Hi John-Mark,
>>
>> the revision i built included gnn's patches to setkey already.
>>
>> I have tried to setup a
om racoon to strongswan as their ike-daemon,
iirc mainly because of strongswans ikev2 daemon and their GCM support. I'm
going to try and have a look what changes pfsense may have made to strongswan
to support GCM on FreeBSD, although i should probably mention, i am not very
experienced at this
Hi John-Mark,
i have tried your patches from your ipsecgcm branch. The build completes, boots
fine and indeed, dmesg shows "aesni0: on
motherboard".
I'm going to try out the new cipher modes tomorrow and will get back..
> On 01 Aug 2015, at 22:01, John-Mark Gurney wrote:
Same here, fixed running r286015. Thanks a bunch.
> On 29 Jul 2015, at 14:56, Alexandr Krivulya wrote:
>
> 29.07.2015 10:17, John-Mark Gurney пишет:
>> Alexandr Krivulya wrote this message on Thu, Jul 23, 2015 at 10:38 +0300:
>>
>> [...]
>>
>>> Wi
Hello,
I'm having the same problem with IPSec, running -current with r285794.
Don't know if this helps, but "netstat -s -p esp" shows packets dropped; bad
ilen.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
