On Fri, 2005-03-18 at 20:09, Andy Furniss wrote:
> jamal wrote:
> > Hi Remus,
> > I could not reproduce this one - it is also a bit odd for calloc to
> > fail. I dont have iptables 1.3.1 but i will get and retry.
> > Does this happen all the time?
> I get the same with iptables 1.3.1 and 1.3.0
> iptables: calloc failed: Cannot allocate memory
> using kernel 126.96.36.199 and tc iproute2-ss050314
> If I try an earlier iptables (tested 9, 10, 11) I get
Ok, I think i figured this one out as well - sorry dont have access to
my test hardware still to verify.
As i was suspecting this is related to iptables breaking backwards
compatibility. Starting with 1.3.0 the target structure changed ;->
(right at the top is a new field called version)
I suspect the iptables folks maybe unaware that there are other users of
iptables and assume that anyone needing to use new iptables will
recompile everything from scratch. BAD! BAD!
I am ccing the necessary evil doers (Harald and Patrick - at least they
would know who the real evildoer is).
To test the theory copy iptables.h and iptables_common.h from
iptables-1.3.1/include into iproute2/include with the latest iproute2
and recompile. Make sure m_ipt.c is recompiled - you may have to do a
make clean in iproute2/tc/
I should be able to validate all this stuff starting tommorow evening.
Also I have a feeling if you make this change, things will not work for
iptables <=1.2.9/10/11. Can you verify that?