[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Testing racoon
On 06/13/2018 04:26 PM, Roy Marples wrote:
On 13/06/2018 17:22, Christos Zoulas wrote:
On Jun 13, 11:23am, frchuckz%gmail.com@localhost (Chuck Zmudzinski) wrote:
-- Subject: Re: Testing racoon
Thanks for all the feedback and testing!
| The problem was fixed by a reboot of the whole system, and then racoon
| started normally again.
There might be still an issue with buffer space in current, but we
bumped the limits for syslogd and kernel sockets. I am not sure what
on here and the ipsec related socket buffers got full.
Looking through our sources for racoon (and assuming racoon2 behaves
similar here), racoon will always set it's own view on how big the
receive buffer should be. See pfkey_set_buffer_size().
So the default socket buffer sizes are not guilty here.
I suspect the error Chuck is seeing was fixed last week by this commit:
It could have been fixed by that - I was testing a snapshot from a
couple of days before that commit.
I am now updated to a snapshot from yesterday and will presume it is fixed.
Main Index |
Thread Index |