9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Antonin Vecera" <antonin.vecera@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] What is the status of IPv6?
Date: Fri, 29 Aug 2008 20:31:55 +0200	[thread overview]
Message-ID: <10b109140808291131s28ab3c83pe150b0d8f963b01c@mail.gmail.com> (raw)
In-Reply-To: <e8788b696cf62a5a047e51ea6f473fef@plan9.bell-labs.com>

On Fri, Aug 29, 2008 at 5:43 PM,  <geoff@plan9.bell-labs.com> wrote:
> IPv6 support is a little rusty, but was working.  I need to
> reestablish an IPv6 test environment here to continually exercise the
> code and figure out some remaining thorny issues.  The last time I
> tried it, I could connect to remote systems via IPv6 using 6in4(8) but
> not local systems, and it appeared that Neighbour Discovery (the v6
> equivalent of ARP, which uses multicast) was broken.
>
> Some of the thorny issues are:
>
> - how best to operate in a mixed v4 and v6 world, where some hosts are
> v4-only, some are v6-only and some (eventually a lot) are capable of
> using both v4 and v6, preferably global (non-NAT, non-private,
> non-local) addresses.  Is the ipv6 attribute of ndb actually useful,
> or should we just use the ip attribute for v4 and v6?
>
> - how to configure diskless v6-only (or almost only) machines at boot
> time?  dhcp v6 seems pointless yet complex, v6 autoconfiguration might
> suffice with changes to implement dynamic dns, or dhcp v4 might be
> able to carry the necessary data.
>
> - how best to evade v4-only IP infrastructure (routers, firewalls,
> proxies, etc.).
>
> I'd be interested in hearing from anyone currently using v6 with Plan
> 9, particularly in Japan.

Thanks for your reply.
Now I am not able to send or receive any byte via v6 ip. It matches to
your message.
I have FreeBSD server with tunnel to Hexago. If will be there some
progress in ipv6 stack I will test it.

Antonin



      reply	other threads:[~2008-08-29 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 16:15 Antonin Vecera
2008-08-28 17:58 ` erik quanstrom
2008-08-29 15:43 ` geoff
2008-08-29 18:31   ` Antonin Vecera [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=10b109140808291131s28ab3c83pe150b0d8f963b01c@mail.gmail.com \
    --to=antonin.vecera@gmail.com \
    --cc=9fans@9fans.net \
    /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).