From: Dax Kelson <dax@GuruLabs.com>
To: linux-kernel@vger.kernel.org
Subject: Is ff:00:00:00:00:00 a broadcast frame?
Date: 01 Jul 2002 17:27:11 -0600 [thread overview]
Message-ID: <1025566031.5129.179.camel@porthos> (raw)
In-Reply-To: <Pine.LNX.4.33.0206291000060.23706-100000@w-nivedita2.des.beaverton.ibm.com>
In the "earlier" 2.4 kernels (those that shipped/errata with RHL 7.1
~2.4.6), an ethernet frame destined to ff:00:00:00:00:00 were not
processed and passed up the stack.
Now, with "current" 2.4 kernels (RHL 7.2 errata, and RHL 7.3
2.4.9-2.4.18), the same frame IS processed and passed up the stack.
The hardware is identical, the NICs are 3c905C.
Is this an intentional optimization/bug?
Here is an ARP request encapsulated in a "bogus" ethernet frame (look at
the layer 2 destination). A RHL 7.3 (2.4.18) system will respond (see
Frame 2 below) to this frame, an older RHL 7.1 (2.4.6) system will not
respond.
Frame 1 (42 on wire, 42 captured)
Arrival Time: Jul 1, 2002 17:16:35.565996000
Time delta from previous packet: 1.009672000 seconds
Time relative to first packet: 1.009833000 seconds
Frame Number: 3
Packet Length: 42 bytes
Capture Length: 42 bytes
Ethernet II
Destination: ff:00:00:00:00:00 (ff:00:00:00:00:00)
Source: ff:00:00:00:00:00 (ff:00:00:00:00:00)
Type: ARP (0x0806)
Address Resolution Protocol (request)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (0x0001)
Sender MAC address: 00:01:03:de:56:a4 (00:01:03:de:56:a4)
Sender IP address: 10.100.0.8 (10.100.0.8)
Target MAC address: 00:00:00:00:00:00 (00:00:00:00:00:00)
Target IP address: 10.100.0.10 (10.100.0.10)
Frame 2 (60 on wire, 60 captured)
Arrival Time: Jul 1, 2002 17:16:35.566146000
Time delta from previous packet: 0.000150000 seconds
Time relative to first packet: 1.009983000 seconds
Frame Number: 4
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II
Destination: 00:01:03:de:56:a4 (00:01:03:de:56:a4)
Source: 00:01:03:de:57:37 (00:01:03:de:57:37)
Type: ARP (0x0806)
Trailer: 00000000000000000000000000000000...
Address Resolution Protocol (reply)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: reply (0x0002)
Sender MAC address: 00:01:03:de:57:37 (00:01:03:de:57:37)
Sender IP address: 10.100.0.10 (10.100.0.10)
Target MAC address: 00:01:03:de:56:a4 (00:01:03:de:56:a4)
Target IP address: 10.100.0.8 (10.100.0.8)
next prev parent reply other threads:[~2002-07-01 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 17:04 zero-copy networking & a performance drop Nivedita Singhvi
2002-07-01 23:27 ` Dax Kelson [this message]
2002-07-02 6:48 ` Is ff:00:00:00:00:00 a broadcast frame? Matti Aarnio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1025566031.5129.179.camel@porthos \
--to=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®