> bye bye features. No 11n for you. We can't go back (need to many of
> the features), instead we are pressuring Cisco to fix the bugs. In
> their defence, they are engaging with us and working hard to resolve
> the issues.
Quite, we don't have any 'n at present; and I'd swap features for
stability at the minute then look again at 6 when it's not beta/ED.
If it fixes the problem that is, as at the minute it's pretty miserable.
> Yes, we noticed there appeared to be an element of load involved.
> Another idea which was being investigated was that some clients with
> duff drivers are sending out broadcast packets which are causing the
> problem.
Yes, there's a whole host of unknowns out there.
There's lots of Intel with duff drivers in TKIP land causing MIC
errors/countermeasures; though we're slowly tracking those down.
Another thought is that these devices might be causing the problem above
somehow.
Cisco <= Microsoft...
|