fec0:0:0:ffff::1%1

[Santhosh]

Hi Team,

fec0:0:0:ffff::1%1

In the abvoe example, what does %1 refer to. I have seen %2,%3,%5 also.

Do you have a limit to %... meaning a table which explains %1 to %n.

Thanks for your help.
--
Santhosh Pallikara

[Jeroen Massar]

Santhosh wrote:
> Hi Team,
>
> fec0:0:0:ffff::1%1
>
> In the abvoe example, what does %1 refer to. I have seen %2,%3,%5 also.
>
> Do you have a limit to %... meaning a table which explains %1 to %n.

It is an interface identifier.

%1 = Interface 1
%2 = Interface 2
%x = Interface x

See 'ipconfig /all' to figure out which number which interface got.
(or "netsh interface ipv6 show interface")

Note that usage of fec0::/10 is deprecated:
8<----------------------------------------------------------------------
http://www.iana.org/assignments/ipv6-address-space
[4] FEC0::/10 was previously defined as a Site-Local scoped address
prefix. This definition has been deprecated as of September 2004
[RFC3879].
---------------------------------------------------------------------->8

As such, avoid use of it. If you need 'documentation' addresses, use
2001:db8::/32

Greets,
Jeroen

[Alun Jones]

"Jeroen Massar" <jer...@unfix.org> wrote in message
news:47288F26...@spaghetti.zurich.ibm.com...

> Santhosh wrote:
>> Hi Team,
>>
>> fec0:0:0:ffff::1%1
>>

...

>
> Note that usage of fec0::/10 is deprecated:

That is correct, but there are examples of addresses that use it, and are
still bound to by default in Windows Server 2008.

Try running "netsh int ipv6 sh dns", and you'll see that any adapter with
IPv6 addresses shows DNS servers at fec0:0:0:ffff::1, 2 and 3.

Alun.
~~~~

[Stefan Moser]

I have checked whether those dns server entries are still there with Windows
7 RC - and they are.

So, does anybody know what Microsoft´s strategy is towards future support of
those dns server entries? If I would make a large rollout today that would be
based on IPv6 autoconfiguration and those dns server entries, instead of
using DHCP - would this be a wise idea?
--
Stefan Moser

[Edward Feustel]

On Mon, 25 May 2009 04:25:01 -0700, Stefan Moser
<stefan...@discussions.microsoft.com> wrote:

>I have checked whether those dns server entries are still there with Windows
>7 RC - and they are.
>
>So, does anybody know what Microsoft�s strategy is towards future support of
>those dns server entries? If I would make a large rollout today that would be
>based on IPv6 autoconfiguration and those dns server entries, instead of
>using DHCP - would this be a wise idea?

Why not use DCHP6?
Ed

[Stefan Moser]

Operating a failure proof DHCP infrastructure in large enterprise networks is
expensive. Usually, in large enterprises DHCP is part of an (costly) IP
management solution.

So, the idea is: With IPv6, would it be possible to avoid any kind of DHCP
infrastructure (at least towards your Windows hosts that do not need any
further DHCP options, of course this is not the case if you think of an IP
phone that needs an DHCP option for the TFTP bootserver)? An ordinary Windows
Client in IPv4 typically needs (hopefully WINS is not used...):

- IP-Adress
- Subnet Mask
- Default Gateway
- Domain-Suffix
- IP-Address(es) of DNS-Server(s)

With autoconfiguration in IPv6, the situation would be:
- IP-Adress ==> derived from autoconfiguration
- Subnet Mask ==> not needed because subnets are /64 per definitionem
- Default Gateway ==> derived from autoconfiguration / router advertisements
- Domain-Suffix ==> not sure so far if you really need it in an active
directory domain, I have to talk to my AD guys
- IP-Address(es) of DNS-Server(s) ==> fec0:0:0:ffff::1

So, the charming thing would be that the client would get everything it
needed WITHOUT any DHCP Infrastructure.
--
Stefan Moser

[Gary]

On Wed, 27 May 2009, Stefan Moser wrote:

> Operating a failure proof DHCP infrastructure in large enterprise
> networks is expensive. Usually, in large enterprises DHCP is part of an
> (costly) IP > management solution.

What do you consider large?

> So, the idea is: With IPv6, would it be possible to avoid any kind of

> DHCP infrastructure ... So, the charming thing would be that the client

> would get everything it needed WITHOUT any DHCP Infrastructure.

The router advertisement daemon can supply everything you need for IP
connectivity. What exactly are you trying to do and why do you want to
avoid DHCPv6? I have a heterogeneous network with Mac, Windows, mobile
devices, etc, and in my IPv6 lab am using router advertisement on the
OpenBSD firewall for router announcement only. I decided to not use it for
address leases since I want someone else to be able to open up the admin
tools on Windows Server 2008 in order to see what leases have been
obtained.

Replacing WINS, on the other hand, is an altogether different matter for
an IPv6 only environment. In that case I suggest that you read the
prolific amount of documentation available for the GlobalNames DNS zone.

-Gary

[Stefan Moser]

"Large enterprise", to me it means a network of >1000 sites, distributed
accross the whole world, >100.000 network clients, >10.000 teleworkers,
connections via different ISPs and different access technologies (leased
lines, MPLS, IPSEC-VPNs, etc.), use of shared infrastructure, different
organizational models (starting with customers that rely completely on their
supplier, ending with customers that only want to get very few services from
their supplier), and so on.

If you are a service provider that has to manage such an LARGE environment,
you have a lot of work dealing with the assignment of address ranges,
operating DNS and DHCP - haven´t you? (Personally, I do not know any company
that accomplishes this with Windows Server 200x´s built-in DNS and DHCP). So,
what I would like to find out is: Does IPv6 offer something that may make
life easier as it was with IPv4? If there is any possibility to get (partly)
rid of DHCP, it should be examined seriously.

Stefan

--
Stefan Moser