From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] configuring ipv6
Date: Thu, 5 Oct 2006 14:22:45 -0400 [thread overview]
Message-ID: <685e1933f230a2063fd5530110190886@plan9.bell-labs.com> (raw)
In-Reply-To: <20061005110918.F80884@orthanc.ca>
I'm not even sure that there's much of an efficiency difference any
more. In a modern wired Ethernet, with each machine on its own switch
port, you should only see unicast traffic destined for you, multicast
traffic and broadcast traffic. Perhaps on wireless networks there
would be a non-trivial difference.
prev parent reply other threads:[~2006-10-05 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 23:22 Lyndon Nerenberg
2006-10-04 23:28 ` geoff
2006-10-05 2:32 ` Lyndon Nerenberg
2006-10-05 15:57 ` geoff
2006-10-05 18:13 ` Lyndon Nerenberg
2006-10-05 18:22 ` geoff [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=685e1933f230a2063fd5530110190886@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.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).