On 12/04/2014 04:28 PM, Ted Unangst wrote:
On Thu, Dec 04, 2014 at 12:29, Kaya Saman wrote:
On 12/03/2014 07:39 PM, Christian Weisgerber wrote:
On 2014-12-03, Josh Grosse wrote:
This could be the bug fixed in src/sbin/isakmpd/ui.c rev 1.56.
Check your system logs for "isakmpd: backwards memc
On Thu, Dec 04, 2014 at 12:29, Kaya Saman wrote:
> On 12/03/2014 07:39 PM, Christian Weisgerber wrote:
>> On 2014-12-03, Josh Grosse wrote:
>>
This could be the bug fixed in src/sbin/isakmpd/ui.c rev 1.56.
Check your system logs for "isakmpd: backwards memcpy".
>>> It may not be that cha
On 2014-12-04, Kaya Saman wrote:
> I am seeing this in the logs:
> Dec 4 09:35:33 Gamma-Ray isakmpd: backwards memcpy
> Dec 4 09:35:33 isakmpd: backwards memcpy
So your isakmpd is broken. Wait for the next snapshot or build one from
-current sources yourself.
--
Christian "naddy" Weisgerbe
On 12/03/2014 07:39 PM, Christian Weisgerber wrote:
> On 2014-12-03, Josh Grosse wrote:
>
>>> This could be the bug fixed in src/sbin/isakmpd/ui.c rev 1.56.
>>> Check your system logs for "isakmpd: backwards memcpy".
>> It may not be that change, since it was only committed two days ago.
>> I've
>
On 2014-12-03, Josh Grosse wrote:
>> This could be the bug fixed in src/sbin/isakmpd/ui.c rev 1.56.
>> Check your system logs for "isakmpd: backwards memcpy".
>
> It may not be that change, since it was only committed two days ago.
> I've
> seen the same symptoms in i386 snapshots from Nov 26 a
On 2014-12-03 13:59, Josh Grosse wrote:
On 2014-12-03 12:47, Christian Weisgerber wrote:
...
This could be the bug fixed in src/sbin/isakmpd/ui.c rev 1.56.
Check your system logs for "isakmpd: backwards memcpy".
It may not be that change, since it was only committed two days ago.
I've
seen
On 2014-12-03 12:47, Christian Weisgerber wrote:
On 2014-12-03, Zé Loff wrote:
for some reason, this seems to have been for a while now; isakmpd
will
simply quit running after initiating: ipsecctl -f /etc/ipsec.conf
I am seeing the same behaviour (apparently a clean exit, no message
whatsoe
On 2014-12-03, Zé Loff wrote:
>> for some reason, this seems to have been for a while now; isakmpd will
>> simply quit running after initiating: ipsecctl -f /etc/ipsec.conf
>
> I am seeing the same behaviour (apparently a clean exit, no message
> whatsoever nor core file) on -current, with an ip
On Wed, Dec 03, 2014 at 03:24:06PM +, Zé Loff wrote:
> On Wed, Dec 03, 2014 at 04:09:02PM +0100, Sebastian Reitenbach wrote:
> > I run this kernel from beginning of November:
> >
> > OpenBSD 5.6-current (GENERIC) #492: Fri Nov 7 10:21:36 MST 2014
> > dera...@i386.openbsd.org:/usr/src/sys/
On Wed, Dec 03, 2014 at 04:09:02PM +0100, Sebastian Reitenbach wrote:
> I run this kernel from beginning of November:
>
> OpenBSD 5.6-current (GENERIC) #492: Fri Nov 7 10:21:36 MST 2014
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Geode(TM) Integrated Processor by
I run this kernel from beginning of November:
OpenBSD 5.6-current (GENERIC) #492: Fri Nov 7 10:21:36 MST 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC"
586-class) 267 MHz
cpu0: FPU,TSC,MSR,CX8,CMOV,MM
On Wed, Dec 03, 2014 at 02:00:59PM +, Kaya Saman wrote:
> Hi,
>
> for some reason, this seems to have been for a while now; isakmpd will
> simply quit running after initiating: ipsecctl -f /etc/ipsec.conf
>
> Starting isakmpd manually with flags -Kdv doesn't give any indication as
> to what
Hi,
for some reason, this seems to have been for a while now; isakmpd will
simply quit running after initiating: ipsecctl -f /etc/ipsec.conf
Starting isakmpd manually with flags -Kdv doesn't give any indication as
to what might be causing the service to crash or segfault and nothing is
reporte
13 matches
Mail list logo
