I have tried the version in wheezy with the same results as with squeeze,
now, I am trying to reproduce the crash with the 0.14.3 downloaded from the
site.
So far it hasn't crashed, but so far there's only minimal traffic via this
router.
I'll be back with more info...
2013/7/6 Karl O. Pinc
BTW, just found in the changelog for 0.14.1 this:
! fix, net_aggr.c: defining a networks_file configuration directive in
conjunction with --enable-ipv6 was causing a SEGVs. This is now solved.
That could be the cause for my issue (unless debian backported the fixes)
2013/7/8 Joan
I think I reported that bug, and it was crashing instantly on start, not
within minutes. Also, I think that never ended up in a release afair, it
was just in trunk.
On 8 Jul 2013 13:30, Joan aseq...@gmail.com wrote:
BTW, just found in the changelog for 0.14.1 this:
! fix, net_aggr.c: defining
The wheezy defautl was crashing for me a bit after loading the
networks_file (that take about a couple of minutes to load) I was trying to
isolate this to open a bug in debian, so at least others are warned.
After unsetting the --enable-ipv6 flag and recompile again with debian
settings/patches,
@george, the issue is not the one you reported (that was against 0.14.3cvs)
but with an older version.
revision 1.16
date: 2012-04-12 14:44:30 +0200; author: paolo; state: Exp; lines: +3 -3;
* nfacctd: etype primitive can now be populated from IP_PROTOCOL_VERSION,
ie. Field Type #60, in
Fair enough. It did sound similar so I assumed it was that. Sorry
On 8 Jul 2013 14:41, Joan aseq...@gmail.com wrote:
@george, the issue is not the one you reported (that was against
0.14.3cvs) but with an older version.
revision 1.16
date: 2012-04-12 14:44:30 +0200; author: paolo; state:
On 07/08/2013 05:30:36 AM, Joan wrote:
BTW, just found in the changelog for 0.14.1 this:
! fix, net_aggr.c: defining a networks_file configuration directive
in
conjunction with --enable-ipv6 was causing a SEGVs. This is now
solved.
That could be the cause for my issue (unless debian
