Hi,
I am trying to upgrade to packetfence-3.2.0 and wondered if anyone out
there has had any luck getting this working in Debian squeeze. I am getting
hung with IPTables/libiptc.pm
Can't locate IPTables/libiptc.pm in @INC (@INC contains: /usr/local/pf/lib
/etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10
/usr/local/lib/site_perl .) at /usr/local/pf/lib/IPTables/Interface.pm line
13.
It's not in any debian packages and installing from cpan errors like so:
.cpan/build/IPTables-libiptc-0.52-l70ZJ0# make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00simple.t ................ 1/2 iptables who? (do you need to insmod?)
t/00simple.t ................ Failed 2/2 subtests
t/01_chain_create.t ......... 1/2 iptables who? (do you need to insmod?)
t/01_chain_create.t ......... Dubious, test returned 1 (wstat 256, 0x100)
Failed 2/2 subtests
t/02_chain_create_commit.t .. 1/3 iptables who? (do you need to insmod?)
t/02_chain_create_commit.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
t/03_chain_exist.t .......... 1/2 iptables who? (do you need to insmod?)
t/03_chain_exist.t .......... Dubious, test returned 1 (wstat 256, 0x100)
Failed 2/2 subtests
t/04_chain_delete_commit.t .. 1/3 iptables who? (do you need to insmod?)
t/04_chain_delete_commit.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
t/05_list_rules_IPs.t ....... 1/2 iptables who? (do you need to insmod?)
t/05_list_rules_IPs.t ....... Dubious, test returned 1 (wstat 256, 0x100)
Failed 2/2 subtests
t/10_rule_create.t .......... 1/3 iptables who? (do you need to insmod?)
t/10_rule_create.t .......... Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
t/11_load_extention_tcp.t ... 1/3 iptables who? (do you need to insmod?)
t/11_load_extention_tcp.t ... Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
t/IPTables-libiptc.t ........ ok
Test Summary Report
-------------------
t/00simple.t (Wstat: 0 Tests: 1 Failed: 1)
Failed test: 1
Parse errors: Bad plan. You planned 2 tests but ran 1.
t/01_chain_create.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 2 tests but ran 1.
t/02_chain_create_commit.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 3 tests but ran 1.
t/03_chain_exist.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 2 tests but ran 1.
t/04_chain_delete_commit.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 3 tests but ran 1.
t/05_list_rules_IPs.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 2 tests but ran 1.
t/10_rule_create.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 3 tests but ran 1.
t/11_load_extention_tcp.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Parse errors: Bad plan. You planned 3 tests but ran 1.
Files=9, Tests=10, 1 wallclock secs ( 0.04 usr 0.03 sys + 0.11 cusr
0.05 csys = 0.23 CPU)
Result: FAIL
Failed 8/9 test programs. 8/10 subtests failed.
make: *** [test_dynamic] Error 255
I think iptables must be missing a module for this (it runs iptables
v1.4.8).
I will try iptables from scratch next, I just wanted to see if anyone has
any suggestions.
--
John Baker
Network Administrator
Marlboro College
Phone: 451-7551 Cell: 490-0066
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Packetfence-users mailing list
Packetfence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
