On Aug 19, 2011, at 6:17 PM, Ludovic Marcotte wrote: > Not really, you have some workarounds that others are using: > • use a very small DHCP lease (say, 20 seconds) in your registration > and quarantine VLANs > • brand the captive portal for Mac OS X-based devices to: > • inform them that they could reboot to finish the registration > process > • inform them that it will take a few minutes (2-3) before they > gain proper network access (which will be detected automatically with some > JavaScript kungfu PacketFence has)
I'm a bit new to Packetfence, and we're really just in the beginning phases of looking at Packetfence as a replacement for Cisco NAC. But this "bug" seems awfully familiar to me. Is the problem here that after associating and being put into the proper VLAN, the computer isn't receiving a new DHCP address for the new VLAN? If so, the exact same thing plagues the Cisco NAC platform as well. The "fix" for it was to bounce the port the user is connected to. It seems the same could be done here as well. > Thanks, > -- > Ludovic Marcotte --------------------------- Jason 'XenoPhage' Frisvold [email protected] --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - Niven's Inverse of Clarke's Third Law ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
