Don't accept invalid beacon interval values (such as 0), neither
locally (for AP VAPs) nor from remote (in scanning results). The value
is used as divisor, which might cause an oops due to "division by zero"
and other unwanted behaviour. Closes #1270.
Thanks to Md Sohail Ahmad from AirTight Networks Inc., who reported
this issue and provided a first patch.