Anonymous | Login | 2024-09-01 05:16 EDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001581 | PacketFence | core | public | 2012-10-22 13:17 | 2012-10-22 16:45 | |||
Reporter | fgaudreault | |||||||
Assigned To | fdurand | |||||||
Priority | immediate | Severity | block | Reproducibility | always | |||
Status | resolved | Resolution | no change required | |||||
Platform | OS | OS Version | ||||||
Product Version | devel | |||||||
Target Version | 3.6.0 | Fixed in Version | ||||||
Summary | 0001581: Inline mode appears to be broken | |||||||
Description | Tested using the RADIUS inline, my node is registered in PF, but I still get to the portal. In fact, the ipset sessions doesn't print. I am on CentOS 6.3 Oct 22 13:16:20 redir.cgi(0) INFO: re-evaluating access for node 00:1b:b1:8b:82:13 (redir.cgi called) (pf::enforcement::reevaluate_access) Oct 22 13:16:20 redir.cgi(0) INFO: Instantiate a new iptables modification method. pf::ipset (pf::inline::get_technique) Oct 22 13:16:23 pfsetvlan(24) INFO: local (127.0.0.1) trap for switch 127.0.0.1 (main::parseTrap) Oct 22 13:16:23 pfsetvlan(7) INFO: nb of items in queue: 1; nb of threads running: 0 (main::startTrapHandlers) Oct 22 13:16:23 pfsetvlan(7) INFO: firewallRequest trap received for inline client: 00:1b:b1:8b:82:13. Modifying firewall. (main::handleTrap) Oct 22 13:16:23 pfsetvlan(7) INFO: Instantiate a new iptables modification method. pf::ipset (pf::inline::get_technique) Oct 22 13:16:23 pfsetvlan(7) INFO: MAC: 00:1b:b1:8b:82:13 stated changed, adapting firewall rules for proper enforcement (pf::inline::performInlineEnforcement) Oct 22 13:16:23 pfsetvlan(7) INFO: finished (main::cleanupAfterThread) | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
![]() |
|
(0003226) fgaudreault (viewer) 2012-10-22 16:45 |
It was a configuration issue. However, the checkup should have catch that. Will open another bug with lower priority. |
Copyright © 2000 - 2012 MantisBT Group |