📎 AI Summary:
The thread discusses configuring IPv6 support on a local network, with the original poster trying to set up multiple IPv6 prefixes and integrate DHCPv6 on a Windows Server 2012 R2, similar to their Linux setup. The responder confirms that implementing IPv6 routing and forwarding is possible in Windows Server 2012 R2 but notes that IPv6 is generally unnecessary for most situations. Overall, the conversation centers on technical feasibility rather than practical necessity.

BMillikan73

New Member
Member details
Joined
Jan 5, 2021
Messages
1
Thread Author #1
I would like to setup IPv6 support for my local network as my ISP has IPv6 support. They provide a /64 network, but when I use a linux router I can request another prefix in the /60 network range. I was able to create a linux router doing this. However, I have been unable to get RRA services to support it. I have the IPv4 NAT setup and it works. But, I haven't been able to setup a similar IPv6 network. On Linux, I can request a second prefix for my internal network adapter and assign it. Then, I can sign a secondary static IPv6 address and setup DHCPv6 to hand out addresses from that subnet. Is this possible in Windows Server 2012 R2? I'd like my active directory server to also. be the router, if possible.
 

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
Yes it's possible as long as you setup forwarding and routing to handle IPv6 although there's virtually no need to use IPv6.
 

Solution