From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IPv6 router advertisements
Date: Wed, 17 Jan 2007 16:37:50 -0500 [thread overview]
Message-ID: <4aa0555a8dedb6bbf9d1be8dcc8c0e3e@plan9.bell-labs.com> (raw)
In-Reply-To: <20070117150621.B24320@SDF.LONESTAR.ORG>
IPv6 does work in Plan 9; until I moved, I was running a small home
network of Plan 9 systems, a couple of Macs and an OpenBSD firewall
that all spoke IPv4 and IPv6 (except ken's file server; I don't think
ILv6 was ever defined). I had a tunnel to one of the free IPv6 tunnel
brokers (it moved as I found out which ones couldn't sustain a
tunnel).
Having said that, we need a few more user-mode daemons to make IPv6
run smoothly. There are ipconfig6 and ping6 programs that aren't yet
on sources. ndb/cs knows how to place IPv6 calls and ndb/dns
understands IPv6 addresses, so it's possible to configure the whole
thing by hand, given ipconfig6. We don't have fancy route
advertisement daemons and the like yet.
next prev parent reply other threads:[~2007-01-17 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 20:06 Claudio Leite
2007-01-17 21:37 ` geoff [this message]
2007-01-18 13:44 ` Claudio Leite
2007-01-18 13:57 ` Russ Cox
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=4aa0555a8dedb6bbf9d1be8dcc8c0e3e@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).