NOTE: Reported in Salesforce. Ticket number 00535866 (now at 2 weeks waiting for Microchip WILC team response.)
When sending packets between 2 WILC devices (AP+STA), the rx'ed packet ethertype field will always be 0x0000, unless it was sent with ethertytpe= IP, IP6, ARP, or VLAN. WILC should pass ethertype field untouched.
This was found when testing B.A.T.M.A.N Advanced protocol which is a different L2 protocol to those listed above. I am testing this protocol because WILC does not support WDS ( 4addr mode ) to allow AP to STA bridging, or 802.11s meshing or basically any other sensible way of interconnecting a WILC modules in a mesh or tree topology. This is compounded by the limit of 8 connected STA to any WILC AP. (actually, I can only get 7 working)
NOTE: Reported in Salesforce. Ticket number 00535866 (now at 2 weeks waiting for Microchip WILC team response.)
When sending packets between 2 WILC devices (AP+STA), the rx'ed packet ethertype field will always be 0x0000, unless it was sent with ethertytpe= IP, IP6, ARP, or VLAN. WILC should pass ethertype field untouched.
This was found when testing B.A.T.M.A.N Advanced protocol which is a different L2 protocol to those listed above. I am testing this protocol because WILC does not support WDS ( 4addr mode ) to allow AP to STA bridging, or 802.11s meshing or basically any other sensible way of interconnecting a WILC modules in a mesh or tree topology. This is compounded by the limit of 8 connected STA to any WILC AP. (actually, I can only get 7 working)