9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] ipv6 setting
Date: Mon, 14 Oct 2019 18:42:12 +0200	[thread overview]
Message-ID: <0140C07E906BEF0CBCC4815EC4759F89@felloff.net> (raw)
In-Reply-To: BC6C12E211F45C8DEADD1303C4690524@hera.eonet.ne.jp

ipv6 is a wide topic...

the nora6= environment variable just disables ipv6 autoconfiguration
on bootup. see /rc/bin/^(termrc cpurc) and /sys/src/9/boot/net.rc.

we handle ipv6 autoconfiguration like dhcp in ndb... that is, if
your machine has a ndb entry, but no ip addresses specified, we'll
try dhcp and slaac (unless disabled with nora6=) to get an address.

for static ipv6 address its the same as ipv4... you just specify
an ipv6 address using the ip= attribute.

for autoconfiguration to work, you need to have actual ipv6 router
on your network that sends router advertisements for the network
prefix. plan9 can do this with ip/ipconfig ra6 sendra 1 ...

note, that we do not have a dhcpv6 *CLIENT* in 9front yet. tho
we have a server (ip/dhcp6d) that can provide information like
dns and bootp server for foreign clients (uefi/windows).

i'm not quite convinced that the 12 second wait time is due to
ipv6 tho... it might be that we try to connect to the secstore
server and icmp being filtered in the network?

--
cinap


             reply	other threads:[~2019-10-14 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 16:42 cinap_lenrek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-15  4:08 kokamoto
2019-10-13 23:04 kokamoto
2019-10-13 18:32 umbraticus
2019-10-13 10:42 vp
2019-10-13  7:03 umbraticus

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=0140C07E906BEF0CBCC4815EC4759F89@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /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).