From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot: __eth_install_handler?
Date: Mon, 22 Jan 2001 14:51:00 -0000 [thread overview]
Message-ID: <XFMail.20010122155113.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <20010122161351.A26689@visi.com>
On 22-Jan-2001 Grant Edwards wrote:
> On Mon, Jan 22, 2001 at 02:57:41PM -0600, Grant Edwards wrote:
>>
>> > > In RedBoot's net.h file, there's a declaration for
>> > > __eth_install_handler(), which would seem from the declaration to
>> > > do exactly what I want to do: set a call-back to handle packets
>> > > with Ethernet protocol type <whatever>.
>> > >
>> > > That functionality hasn't been implemented, so I'm about to
>> > > implement it.
>
> It doesn't look like the packet handler routines verify that
> the length of a received Ethernet frame is long enough to
> contain the amount of data expected. For example, the IP
> handler doesn't check to make sure that the number of bytes in
> the Ethernet frame was was large enough to hold the amount of
> data claimed in the IP header.
>
> The only way for that to happen would be for another host to
> intentionally send a short Ethernet frame (AFAIK). Even if that
> happens it should be caught by the checksum verification,
> right?
>
That would certainly be true - the checksum routines will try
and access the advertised length of data. I see no way that the
computed value would match if the actual data was too short.
next prev parent reply other threads:[~2001-01-22 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 11:54 Grant Edwards
2001-01-22 12:04 ` Gary Thomas
2001-01-22 12:53 ` Grant Edwards
2001-01-22 14:09 ` Grant Edwards
2001-01-22 14:51 ` Gary Thomas [this message]
2001-01-23 0:13 ` Andrew Lunn
2001-01-22 14:51 ` Grant Edwards
2001-01-22 15:56 ` Grant Edwards
2001-01-31 4:25 ` Gary Thomas
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=XFMail.20010122155113.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).