Subject: Re: scopeid on NetBSD-1.5.1 branch
To: Feico Dillema <firstname.lastname@example.org>
From: None <email@example.com>
Date: 02/15/2001 03:17:12
>On several machines running netbsd-1.5.1_ALPHA, ifconfig gives
>scopid's that do not make much sense. For example:
>le0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> address: 00:60:b0:c1:59:44
> media: Ethernet autoselect
> status: active
> inet6 3ffe:2a00:100:3008:260:b0ff:fec1:5944 prefixlen 64
> inet6 fe80::260:b0ff:fec1:5944%le0 prefixlen 64 scopeid 0x1
>It looks like the scopeid shows the interface-id instead. Is my
>source/includes messed up or do others see the same? Just checked;
>I see the same on a machine running -current.
why do you say they don't make sense? they do make sense to me.
what did you expect if the above does not make sense?
scopeid for link-local addresses are indeed interface id for the
interface. this is only because that KAME code assumes one-by-one
mapping between interfaces (hardware terminology) and links
(vip6 terminology), to simplify scope management.