We are currently running 3.5.1, with an upgrade planned for this summer. I was curious if we were the only ones running into this or not.
It seems to mostly effect Android phones and Windows machines, but I have take no notice of age being a huge factor. ________________________________ From: David Murrell <[email protected]> Sent: Tuesday, May 26, 2015 4:07 PM To: [email protected] Subject: Re: [PacketFence-users] registered users 'stuck' in registration network I ran into a version of this for our campus, though we're only using Cisco Wism2 as a wireless provider. The thing that made it mostly work was bumping the dhcp lease time to 180 sec on the registration network - some older phones seemed to get very confused with a 30 sec lease time. Might be a contributing factor, perhaps. Cheers, David Murrell On Wednesday, May 27, 2015, Jason 'XenoPhage' Frisvold <[email protected]<mailto:[email protected]>> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/26/15 12:15 PM, Gary Ossewaarde wrote: > PF Folks, > > We have both Cisco wireless and Aerohive on our campus and are > running PacketFence doing MAC auth for guest wireless. > > On the Cisco WLC/APs, it works well. On the Aerohive APs, it > usually works well, but occasionally, and I have not yet found a > pattern and who/why, users will get 'stuck' in the registration > network. The PF console will show them as registered but in the > wrong VLAN. If these users go to an area of campus running Cisco > wireless and connect, they are in the correct network. If they come > back to an Aerohive area /after/ that, they stay in the correct > network and are 'unstuck'. > > I am pretty new with PacketFence (inherited it from an admin who > left) and could use some direction in troubleshooting and ideas on > what may be going on. What version of PF is this? I saw the same thing with Aruba wireless. First things first, make sure pfsetvlan is running. This was the underlying cause for most of the problems we saw of that nature. After that, it seemed to me that there was an issue with the aruba platform not always responding to the CoA packets, or, worse, responding but ignoring them. I never figured out what the ultimate solution was, unfortunately, and it was intermittent enough that I couldn't reliably replicate it to debug. That said, it was a pretty low number of devices that experienced this and once registered they were fine. > Thanks, > > Gary - -- - --------------------------- Jason 'XenoPhage' Frisvold [email protected] - --------------------------- "A common mistake that people make when trying to design something ompletely foolproof is to underestimate the ingenuity of complete fools. " - - The Hitchhikers Guide to the Galaxy -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlVkylwACgkQhR5xme3cl75xqwCfa4FN50Gprn6rmiWpPTaWKxee fVAAn1MrlulZ2I1KgUjq8hUlEjWsHAmO =6/eP -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
