All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, bns_robson@hotmail.com
Subject: Re: [patch 5/5] IPv6 to Intel EtherExpress 16 fails - multicast problems
Date: Tue, 06 May 2008 12:23:11 -0400	[thread overview]
Message-ID: <482085EF.1040005@garzik.org> (raw)
In-Reply-To: <200805022040.m42KesxY013686@imap1.linux-foundation.org>

akpm@linux-foundation.org wrote:
> From: Bruce Robson <bns_robson@hotmail.com>
> 
> Taken from http://bugzilla.kernel.org/show_bug.cgi?id=10577
> 
> I was unable to access a computer containing an Intel EtherExpress 16 network
> card using IPv6.
> 
> I traced this to failure of neighbour discovery.  When I used an "ip -6 neigh
> add" command, on the computer attempting access, to insert a binding between
> the IPv6 address of the computer with the Intel EtherExpress 16 network card
> and the card's ethernet address, I was able to access that computer using
> IPv6.
> 
> Neighbour discovery requires working multicast.  The driver sources file
> eexpress.c contains an approximately 30 line function eexp_setup_filter used
> when loading multicast addresses.
> 
> I found 3 problems in this function
> 
> 1) It wrote the number of multicast addresses to the card instead of the
>     number of bytes in the multicast addresses.
> 
> 2) When loading multiple multicast addresses it loaded the first one
>     provided multiple times instead of loading each one once.
> 
> 3) The setting of pointer 'data' from 'dmi->dmi_addr' occured before the
>     test for the error situation of 'dmi' being NULL.
> 
> Correcting these problems allows the computer with the Intel EtherExpress 16
> network card to found by IPv6 neighbour discovery.
> 
> p.s. There is some information on the Intel EtherExpress 16 at
> http://www.intel.com/support/etherexpress/vintage/sb/cs-013500.htm
> Datasheet for the Intel 82586 ethernet controller used by the card
> http://www.datasheetcatalog.com/datasheets_pdf/8/2/5/8/82586.shtml
> 
> Signed-off-by: Bruce Robson <bns_robson@hotmail.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  drivers/net/eexpress.c |   11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)

applied



      reply	other threads:[~2008-05-06 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 20:40 [patch 5/5] IPv6 to Intel EtherExpress 16 fails - multicast problems akpm
2008-05-06 16:23 ` Jeff Garzik [this message]

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=482085EF.1040005@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=bns_robson@hotmail.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.