Hello Joshua, What you changed is the message that are printed in GUI. And this msgID does not means anything.
Morever, this will not fix your issue. With inline, you do not have to configure network devices. Can you ping a public IP when you get the error page? If so can you ping a domaine name? Can you look in ipset, (ipset list) if you see your IP/Mac there. regards. Loick On Mon, Feb 24, 2014 at 11:47:51AM +0100, Josh Nathan wrote: > OK, I found this entry in the file: > /usr/local/pf/html/pfappserver/lib/pfappserver/I18N/en.po > > # conf/documentation.conf (vlan.trap_limit_threshold) > msgid "" > "Maximum number of SNMP traps that a switchport can send to PacketFence > within " > "a minute without being flagged as DoS. Defaults to 100" > msgstr "" > > I changed: > msgstr "" > to: > msgstr "1000" > Can anyone confirm if that's what wanted to change? > > Thanks, > Joshua Nathan > IT Administrator > Black Forest Academy > +49 (0) 7626-916123 > > > On Mon, Feb 24, 2014 at 10:39 AM, Josh Nathan <[email protected]>wrote: > > > Hello, > > > > We're getting the "Sorry, your Internet connection will be enabled within > > a minute or two..." message. The packetfence.log file says the following: > > > > Feb 24 10:11:12 redir.cgi(0) INFO: 20:89:84:70:62:67 being redirected > > (default profile) > > (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_html_captive_2dportal_redir_2ecgi::handler) > > Feb 24 10:11:12 redir.cgi(0) INFO: MAC 20:89:84:70:62:67 shouldn't reach > > here. Calling access re-evaluation. Make sure your network device > > configuration is correct. > > (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_html_captive_2dportal_redir_2ecgi::handler) > > Feb 24 10:11:12 redir.cgi(0) INFO: re-evaluating access for node > > 20:89:84:70:62:67 (redir.cgi called) (pf::enforcement::reevaluate_access) > > > > I'm using Inline enforcement with PacketFence 4.1. The network devices > > shouldn't need to be "configured" for Inline enforcement, should they? So > > how can it be incorrect? The other odd thing is that other computers do go > > through the same switches without this problem. It seems to be that > > restarting PacketFence clears is up for a while as well. We had this > > problem is PF 3.2 if too many people tried to sign in too close together, > > but it was fixed in 3.6... I'd rather not downgrade, though. Any ideas? > > > > Thanks, > > Joshua Nathan > > IT Administrator > > Black Forest Academy > > +49 (0) 7626-916123 > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users -- [email protected] :: +1.514.447.4918 (x130) :: www.inverse.ca<http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (www.sogo.nu<http://www.sogo.nu/>) and PacketFence +(www.packetfence.org<http://www.packetfence.org/>) gtalk or skype : lpelet.inverse ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
