From: Sergey M. <sm...@sm...> - 2015-02-06 18:30:38
|
Hello, Marco. Yes, all files in iptables directory. A lot of code in these files was copied from corresponding files of iptables project, so you may try to compare sources of two iptables versions to understand what was changed, and then move changed pieces of code to ipac-ng. Sergey Merzlikin 06.02.2015 13:35, Marco Gaiarin пишет: > Mandi! Sergey Merzlikin > In chel di` si favelave... > >> Firstly, fetcipac must be recompiled (with correct iptables headers) >> every time iptables version change because it depends on iptables libraries. > > You put me in doubt, so i've recompiled ipac-ng, but nothing changed. > > configure seems to me do the right job... > > ./configure --prefix=/usr \ > --mandir=/usr/share/man \ > --datadir=/var/lib/ipac \ > --enable-default-storage=plain-file \ > --with-postgresql-inc=/usr/include/postgresql > [...] > checking xtables.h usability... yes > checking xtables.h presence... yes > checking for xtables.h... yes > checking libiptc/libiptc.h usability... yes > checking libiptc/libiptc.h presence... yes > checking for libiptc/libiptc.h... yes > checking for library containing xtables_init... -lxtables > checking for library containing iptc_init... -lip4tc > checking for default database name... ipac (default) > checking for default database port... (default) > configure: creating ./config.status > [...] > > >> Secondly, current version of ipac-ng was tested with iptables up to >> 1.4.12-1. I'm not sure whether ipac-ng will work or not with newer >> versions of iptables. >> So, try to recompile. If it will not help, try to downgrade iptables. > > Downgrading iptables is really a no-options. > > There's something where i can look into to try to make a patch? Seems > to me into agents/iptables/iptables.c, but i'm seeking feedback. > > > Thanks. > |