>> Which bug are you referring to? You are talking about the problem where >> the node is not getting a new DHCP address upon a dissociation? > > Yes, that is the bug I am referring too > >> This is fixed since 10.6.5 on the wireless, but remains unfixed for the >> wired. > > Yes, we are using wired connections. So I guess we are stuck until > Apple get a fix pushed out.
Just to remind everyone that this issue is specific to wired 802.1X and not any other access mechanism (mac-auth, port-security, link-up/link-down, etc.). If you are not doing access control on your wired network using 802.1X then this is a new issue and we would need more information. On wired access we bounce the port whenever a VLAN change is required just like Jason suggested. Maybe the port bounce is not long enough. In the configuration under [vlan] there is a bounce_duration parameter maybe you can try to increase it and see if it changes anything? Otherwise, the usual checking of logs/packetfence.log is recommended. -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
