I guess some bridges take Netware Ethernet_802_3 frames, which are 802.3

frames (with a length field rather than a type field, but with no 802.2
header in the payload), and just stick the payload into an 802.11 frame.
I've seen captures that show frames of that sort.

This means we have to do the same check for Netware 802.3 - or, if you
will, "Netware 802.11" - that we do in the Ethernet dissector, i.e.
checking for 0xffff as the first four bytes of the payload and, if we
find it, treating it as an IPX frame.

svn path=/trunk/; revision=3759

0 files changed, 0 insertions, 0 deletions