Ethernet Bridge development
 help / color / mirror / Atom feed
From: Cameron Schaus <cam@schaus.ca>
To: wade.guthrie@mindspeed.com, bridge@lists.linux-foundation.org
Subject: Re: [Bridge] I want to RTFM -- so where's the FM?
Date: Thu, 22 Mar 2007 12:06:19 -0600	[thread overview]
Message-ID: <4602C59B.7080301@schaus.ca> (raw)
In-Reply-To: <4602BB71.2010002@mindspeed.com>

Wade Guthrie wrote:
> Is there any documentation on 
> the internals of the bridging software or do I have to paw through the 
> source?
>   
In a previous list post 
(http://lists.linux-foundation.org/pipermail/bridge/2006-December/001593.html) 
I recommended the "Understanding Linux Network Internals" book published 
by O'Reilly publishing. This book has several chapters that explain in 
detail the linux bridge and STP implementation, as well as a chapter 
that explains STP in detail.

Cam




  reply	other threads:[~2007-03-22 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 17:22 [Bridge] I want to RTFM -- so where's the FM? Wade Guthrie
2007-03-22 18:06 ` Cameron Schaus [this message]
2007-03-22 18:27 ` Stephen Hemminger

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=4602C59B.7080301@schaus.ca \
    --to=cam@schaus.ca \
    --cc=bridge@lists.linux-foundation.org \
    --cc=wade.guthrie@mindspeed.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