Hi Rich, > With MacOS 10.6 on MacBook Pro and iMac hardware, it doesn't. It appears > necessary to tell the client to cycle AirPort off/on or to wait until > DHCP lease expiration. This was the case for MAC OSx < 10.6.5. Beyond 10.6.5, it was working fine. What is the exact version of OSX you tested with?
> > I see a couple related bugs. Any update or workarounds? > > http://www.packetfence.org/bugs/view.php?id=1004 This only impacts 802.1X, not mac authentication. However, it may be related to Caching on the client side (we don't think you can disable it on OSx). > http://www.packetfence.org/bugs/view.php?id=1132 Like I said, 10.6.5 and higher should be immuned to the issue. Thanks! -- Francois Gaudreault, ing. jr [email protected] :: +1.514.447.4918 (x130) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
