Comment # 7
on bug 11205
from [email protected]
> Doug seems to say you're already doing that:
>> Aruba could compute an FCS for the copy but that would eat up CPU cycles and >> it wouldn't represent what was transmitted anyway. So they pad four null
>> bytes to occupy the FCS space.
At this moment, for TX frames there is no FCS and no padding. The lack of FCS
is likely an oversight rather than a deliberate ploy to avoid CPU.
> So, *if* that's what you're doing, we could check the FCS if it's non-zero
> but not if it's zero. That wouldn't require a preference.
It's not the current state of affairs, but I am going to angle for it to be the
solution.
I should note that inserting a fake or padded FCS is what I would like R&D to
do - but what I can get them to do, and what I end up with may be two different
things.... raising a bug on it internally today.
You are receiving this mail because:
- You are watching all bug changes.
