Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt

[Nick Hilliard <[e-mail]>]

Brian E Carpenter wrote on 09/07/2021 22:10:
> C:\WINDOWS\system32>ping ::1%0
> 
> Pinging ::1 with 32 bytes of data:
> Reply from ::1: time<1ms
> 
> so I guess interface 0 is the loopback, but it is listed nowhere as such.

this really is odd. The loopback interface is technically interface 1:

> C:\Users\nick>netsh interface ipv6 show address
> 
> Interface 1: Loopback Pseudo-Interface 1
> 
> Addr Type  DAD State   Valid Life Pref. Life Address
> ---------  ----------- ---------- ---------- ------------------------
> Other      Preferred     infinite   infinite ::1

and:

> C:\Users\nick>route print
> ===========================================================================
> Interface List
>   4...00 xx xx xx xx xx ......Intel(R) 82574L Gigabit Network Connection
>   1...........................Software Loopback Interface 1
> ===========================================================================

and using more up-to-date tools:

> PS C:\WINDOWS\system32> get-netipinterface -InterfaceIndex 1
> 
> ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore
> ------- --------------                  ------------- ------------ --------------- ----     --------------- -----------
> 1       Loopback Pseudo-Interface 1     IPv6            4294967295              75 Disabled Connected       ActiveStore
> 1       Loopback Pseudo-Interface 1     IPv4            4294967295              75 Disabled Connected       ActiveStore
> 
> 
> PS C:\WINDOWS\system32> get-netipinterface -InterfaceIndex 0
> get-netipinterface : No MSFT_NetIPInterface objects found with property 'InterfaceIndex' equal to '0'.  Verify the
> value of the property and retry.
> At line:1 char:1
> + get-netipinterface  -InterfaceIndex 0
> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>     + CategoryInfo          : ObjectNotFound: (0:UInt32) [Get-NetIPInterface], CimJobException
>     + FullyQualifiedErrorId : CmdletizationQuery_NotFound_InterfaceIndex,Get-NetIPInterface
> 
> PS C:\WINDOWS\system32>

"ping ::1%0" works, but "ping ::1%1" returns a general failure.  But if 
you attempt to scope a global IP address to the interface ID that the 
fe80: address is tied to, it will also fail.

So, not clear what the scope ID actually refers to here. Someone with 
more windows clue is going to have to answer this one, and you're right 
that there's a fairly deep lack of documentation on how this is supposed 
to work.

Nick