On 01/09/15 13:31, Alan DeKok wrote:
Yeah. The client sends a DHCP discover, and the switch ignores it... because it's waiting for EAP!
My suspicion is that most switch vendors hire engineers who know nothing about networks, and who don't use the equipment they're building.
The weird thing about this is that equipment varies dramatically in how it handles this. For example, the now-ancient 3Com 4400s handled this very well indeed; they treated non-EAP traffic as macauth, until the first EAP packet from a given source MAC, at which point they toggled a soft-state bit, making that MAC/port combo "EAP required", and clearing the state at link-down. Worked very well. Juniper handle this poorly - if you force macauth-only they macauth straight away, otherwise you wait NxM (N=configurable, M=EAP timeout) which is almost always longer than you want to wait for DHCP to complete on a non-EAP device :o/