From: Gavin D Holland <gholland@cs...> - 1999-12-06 16:20:15
It looks like either the driver or tcpdump is getting confused between
RFC 1042 and RFC 894 encapsulation. The frame type field in 894 is the
length field in 1024. Assuming 0024 is hex, then that would be the
length of an ARP request/reply minus padding (3 byte LLC, 5 byte SNAP,
28 byte data). It's still an illegal frame w/o the padding (according
to 1024), but it's the best guess I can make based on your description.
> I have tried to trace some strange behaviour when working at 2 Mbps and
>interoperate between a Wavelan netcard and an Aironet AP. It looks like the
>Wavelan driver provided by Lucent is not sending the ARP requests correctly by
>means of sending a somewhat weird protocol id (0024 or something like
>that)...traced by tcpdump..
>Of course the Aironet card works fine...(both upgraded to 3.10 (PC) and 7.66
>(AP)... I am thinking of switching to Andrew's Wavelan driver...anyone any
>positive experiences with it in terms of interoperability?
>This is all under linux 6.0 (2.2.5) however..
Get latest updates about Open Source Projects, Conferences and News.