From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 bridging
Date: Tue, 19 Jun 2007 07:42:52 -0400 [thread overview]
Message-ID: <d295ea7675917a51619adc3bd5875b56@coraid.com> (raw)
In-Reply-To: <1055b16f0706182034t581f9effr3bfd126fd5b7ba62@mail.gmail.com>
> ok, i'm still not sure what you're trying to do but thought i'd
> mention that bridge(3) is not something that implements an "Ethernet
> bridge" as in ANSI/IEEE 802.1d
i don't have the 802.1d standard. i can imagine the mss business isn't
standard and it seems a real bridge needs to participate in spanning-tree
stuff. is there anything else a bridge must do?
i just want to be able to keep traffic counters &c between two hosts connected
back-to-back. i think bridge(3) provides more than i need, but i might be
missing something.
- erik
prev parent reply other threads:[~2007-06-19 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 20:38 erik quanstrom
2007-06-18 20:46 ` geoff
2007-06-18 21:04 ` erik quanstrom
2007-06-18 22:10 ` Artem Letko
2007-06-18 22:43 ` erik quanstrom
2007-06-19 3:34 ` Artem Letko
2007-06-19 11:42 ` erik quanstrom [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=d295ea7675917a51619adc3bd5875b56@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).