I saw this problem back in 2013 on Bird 1.3.6 and 3.6+ kernels..
(Re: Strange MD5 Auth problem in BIRD 1.3.8)
AFAIK it was related to kernel socket option memory (or lack there of)
and I can only surmise it was related to some sort of memory leak.
Ondrej Zajicek seemed to think this was an issue
I have a machine running BIRD 1.4.5, and I'm seeing a lot of these
messages when I start it up:
2015-08-24 15:54:26 : Socket error: TCP_MD5SIG: Cannot
allocate memory
2015-08-24 15:54:26 : Socket error: TCP_MD5SIG: Cannot
allocate memory
It also seems like the sessions that report
On Mon, Aug 24, 2015 at 01:30:14PM +0100, Israel G. Lugo wrote:
> Hi,
>
> Sorry for the delay in responding. I was away on vacations.
>
> I will try the patch. Would you still like me to gather debug output
> first, with the current version?
Hi
If the patch works then it is unnecessary.
--
El
Hi,
Sorry for the delay in responding. I was away on vacations.
I will try the patch. Would you still like me to gather debug output
first, with the current version?
Regards,
--
Israel G. Lugo
Núcleo de Redes e Comunicações
Direção de Serviços de Informática
Instituto Superior Técnico
On 19-08
