On Fri, May 31, 2013 at 12:57:45PM +0200, Piotr Janusz wrote:
[...]
> 
> That looks like the same problem you pointed out a year ago on
> linux-netdev mailing list:
> http://marc.info/?l=linux-netdev&m=134105805817153&w=2
[...]

I don't remember the outcome of this particular case,
but the problem has been solved multiple times.
(It's also quite common that people report issues which in
because of not using it properly.)

The same issue surfaces again and again, because of constant
API/ABI breaks on the iptables side. Hopefully the future
will be better because now libxtables has been split out
to it's own package in Debian with a proper package name
including a the .so version. Now we can just hope that
(upstream) properly updates the so version when breaking
the API/ABI in the future (but allow me to doubt).

I'm not a user of the tc ipt/xt module myself, so I rely
on actual users testing the module and reporting when and
what something needs to change to get it working again.
(Also, since I'm not using this myself I'm not an expert
on detecting when people use it incorrectly.)
Unfortunately those few users usually just show
up right *after* a stable release has already happened.

Hopefully I've provided you with some guidance on
what usually is the issue. I'm hoping you can dig furter
and when you find a solution update this bug report with
the information, to share it with other users.....

-- 
Andreas Henriksson


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to