9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] IPV6
Date: Sat,  1 Apr 2017 20:51:30 +1100	[thread overview]
Message-ID: <CAJQxxw=0s9F6vGmTV_fACLRfL8_UJe0UXkvTow8D+TQPGT4Gyw@mail.gmail.com> (raw)
In-Reply-To: <20170401094653.GC54181@oneeye>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

It doesn't work if I ignore it. ip(2) doesn't mention '%'

Regards,

brucee

On 1 April 2017 at 20:46, Ori Bernstein <ori@eigenstate.org> wrote:

> On Sat, Apr 01, 2017 at 08:36:55PM +1100, Bruce Ellis wrote:
> > Does anyone know what IPV6 addresses like fec0:0:0:ffff%1 mean and how to
> > make a real (plan9) IPV6 address from them.
> >
> > Regards.
> >
> > brucee
>
> The portion before the '%' is a plain old (link local) ipv6 address. The
> part after the '%' is a zone id. It's safe to ignore.
>
> Because link local addresses share prefixes, they may need to be told
> what interface to come out of. They can be ignored safely enough, or if
> you want you use an arbitrary string like 'fe80::%/net.alt' as the zone.
>
>
>

[-- Attachment #2: Type: text/html, Size: 1230 bytes --]

  reply	other threads:[~2017-04-01  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  9:36 Bruce Ellis
2017-04-01  9:46 ` Ori Bernstein
2017-04-01  9:51   ` Bruce Ellis [this message]
2017-04-01 10:06   ` Kurt H Maier
2017-04-01 10:10     ` Bruce Ellis
2017-04-01 10:17       ` hiro
2017-04-01 16:51         ` Erik Quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2007-04-20 21:41 [9fans] ipv6 geoff
2007-04-20 23:46 ` Tim Wiess
2002-05-28 12:29 presotto
2000-05-08 14:38 [9fans] IPv6 Lucio
2000-05-08 14:06 Lucio
2000-05-08 12:56 presotto

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='CAJQxxw=0s9F6vGmTV_fACLRfL8_UJe0UXkvTow8D+TQPGT4Gyw@mail.gmail.com' \
    --to=bruce.ellis@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).