Ethernet Bridge development
 help / color / mirror / Atom feed
From: Paul Schulz <pschulz@foursticks.com>
To: bridge@lists.osdl.org
Cc: sjolly@foursticks.com
Subject: [Bridge] Bridging on broken Broadcom hardware.
Date: Thu, 19 Feb 2004 09:56:56 +1030	[thread overview]
Message-ID: <1077146815.3779.14.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

Greetings (first post to the list)...

The following patch is required to allow bridging to occur on an
IBM x305 (1RU server).  (It has been posted to the kernel-developers
mailing list previously.)

Background:
  - The Dual Broadcom NICs in the IBM x305 have a broken checksum
    routine which wants to calculate the checksum the ethernet
    packet where the 'source' IP address is the IP address 
    of the sending interface.
    This breaks bridging! (Upstream hosts see an invalid checksum 
    and drop the packet.)

  - I have heard of other issues with Broadcom NICs not
    working with IPv6 and broadcast/multicast which could be 
    related.
    
I would like to get these results and the fix verified, as it will
effect any hosts using this chipset. Does anyone have any pointers?

Paul Schulz <pschulz@foursticks.com>


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-02-18 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 23:26 Paul Schulz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-18 23:29 [Bridge] Bridging on broken Broadcom hardware Paul Schulz

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=1077146815.3779.14.camel@localhost \
    --to=pschulz@foursticks.com \
    --cc=bridge@lists.osdl.org \
    --cc=sjolly@foursticks.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