<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META content="MSHTML 5.50.4930.1700" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=945354915-22012004><FONT face=Arial size=2>Hi
all,</FONT></SPAN></DIV>
<DIV><SPAN class=945354915-22012004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=945354915-22012004><FONT face=Arial size=2>I'm trying to verify
an assumption I have on what the wireless driver should do with the FCS of an
Ethernet frame when it receives it from eth0 when eth0 and wlan0 are bridged
together. From looking at the prism2_tx() function, it is clear that the
SRC and DST fields from the Ethernet header are copied to the txdesc.
After that, the skb->data is copied to the BAP (minus the first 14
bytes/Ethernet header). My question then is this - it does not appear as
though the code makes any effort to detect the presence of a trailing FCS and
the end of skb->data, as it would exist in the case where eth0 and wlan0 are
tied together via a bridge (br0). It was my understanding (or maybe
assumption is a better word) that the data sent over the wireless link should
not have the Ethernet FCS encapsulated within the 802.11 payload. Is this
correct, or am I misunderstanding?</FONT></SPAN></DIV>
<DIV><SPAN class=945354915-22012004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=945354915-22012004><FONT face=Arial size=2>Thanks for the
clarification!<BR>Adam</FONT></SPAN></DIV></BODY></HTML>