On Thu, 9 Sep 1999, Michael [iso-8859-1] Tro� wrote:
> I know of ethernet MAC controllers
> which are capable of strippin the pad bytes automatically from incoming
> frames.
>
I've seen too short packets when sent by my 3com vortex ethernet
controller and by a virtual AMD PCNet controller coupled with a Linux s
ystem (2.0.35 and 2.2.10) thanks to VMWare . But I can see the padding
bytes when the virtual machine runs Windows.
So, the answer could be that if the driver padds, we can see these bytes,
and if it doesn't (the driver is specific to the hardware and knows if it
is worth padding or not, in these case, it is not) the hardware padds and
is able to unpadd hardware padded packets.
But it does not satisfy me.
For me, there is an ethernet layer, which is for example responsible for
ARP requests when given a IP packet, and whose job is to make a correct
ethernet packet for IP (DST MAC + SRC MAC + TYPE + data given by the IP
layer + necessary padding bytes). It gives its packet to the driver layer
which transmit it "as-it" to the hardware which adds crc and transmition
negotiations.
Am I wrong?
(I expect it is more complex because of other layers than IP..)
I wish I had a Linux at work to check this!
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
