From: Francois G. <fga...@in...> - 2012-01-27 20:47:29
|
Hi Andi, > but that is because I don't actually have internet access on the dev network, but that is something I'm working on. If your Internet is not working, the automatic redirection won't work. By default, we are pulling a 1px image from our website. If it fails, you have no internet, if it works, it means the internet is working and we redirect the user. > One odd thing I just noticed while looking through the logs is old SoH violations still occurring, even though the laptop has since been fully updated with everything the windows 7 action centre requires. The SoH part of the radius log shows that it has passed all SoH tests, but the packetfence.log shows the following: > > Jan 27 16:01:06 pf::WebAPI(2956) INFO: 6037 grace remaining on violation 4000001 (trigger soh::2) for node 00:24:54:42:86:04. Not adding violation. (pf::violation::violation_trigger) > Jan 27 16:01:06 pf::WebAPI(2956) INFO: MAC 00:24:54:42:86:04 matched filter NoAntivirus (pf::soh::evaluate) > > Once the grace period is over the violation gets flagged again, despite being remedied. I've installed Microsoft antivirus and spyware, windows firewall enabled and all security updates are installed. You should remove the isolation subnet from the trigger.range in your pf.conf, and restart PF. It should do the trick. -- Francois Gaudreault, ing. jr fga...@in... :: +1.514.447.4918 (x130) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) |