Re: [Packetfence-users] on Debian WAS: installation issues

[cg <na...@gm...>]

Hello Olivier,

Version 1.9.0 has been running fine on our wired network,
authenticating against a freeRadius server.

Downloaded the new 1.9.1 version, installed and upgraded our PF
server. Thanks to the PF team for the fixes and all - it's in place
and everything, but the single item below, seems to be running well.

Upgrade to 1.9.1 : perhaps I'm experiencing the issue mentioned in the
first paragraph of the UPGRADE file - the captive portal has stopped
authenticating against radius and the error messages are listed as a
Ps. Would appreciate any comment.

I think, at this point, that PF can safely be said to be running on a
Debian system. Thanks again for your invaluable assistance with it
all. The adaptation, with the exception of the httpd script, has been
a series of relatively minor things - it really hasn't been too
bad. If you can clarify the question below I can begin rolling up the
Debian HowTo.

My last remaining significant loose end has been how to specify active
interfaces to the dhcpd daemon. I'm not a dhcp wizard but I've been
through all the man pages and looked things up on the web and, as far
as I can tell, the *only* way of specifying interfaces to dhcpd is to
put them on the end of the command that launches the daemon. Am I
missing something simple and obvious ? Therefore, since I can't find
another way to do it, I've perpetrated a classic Horrible Hack(tm) and
added my interfaces to the end of the :

$flags{'dhcp'} =

line in lib/pf/services.pm. It seems that, rightfully, the
get_dhcp_devs() function should return & append the interfaces - but
it doesn't. Can you suggest where I might specify the relevant
interfaces (eth0.102 and eth0.103) to have them added 'canonically'
(instead of being non-portably hacked it) to the end of the
command. I've tried creating the /etc/sysconfig/dhcpd file and
entering them as spec'd in the Installation doc but it didn't work.

Hope you're having a good weekend ...

Best,

Chris

Ps. The logs for the registration error :

from the error_log (repeated many times for a single registration attempt) :

[Fri Sep 24 18:28:34 2010] -e: Constant subroutine ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_cgi_2dbin_redir_2ecgi::SCAN_VID redefined at /usr/lib/perl5/ModPerl/Util.pm line 69.
[Fri Sep 24 18:28:35 2010] -e: Constant subroutine ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_cgi_2dbin_register_2ecgi::INSTALL_DIR redefined at /usr/lib/perl5/ModPerl/Util.pm line 69.

from packetfence.log :

Sep 24 18:28:34 redir.cgi(0) INFO: unknown User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100911 Iceweasel/3.5.12 (like Firefox/3.5.12) (pf::web::web_node_record_user_agent)
Sep 24 18:28:34 redir.cgi(0) INFO: aa:bb:cc:dd:ee:ff redirected to registration page (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_cgi_2dbin_redir_2ecgi::handler)
Sep 24 18:28:35 register.cgi(0) INFO: 192.168.102.10 - aa:bb:cc:dd:ee:ff (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_cgi_2dbin_register_2ecgi::handler)
Sep 24 18:28:59 register.cgi(0) INFO: 192.168.102.10 - aa:bb:cc:dd:ee:ff (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_cgi_2dbin_register_2ecgi::handler)