Monday, November 12, 2018

Understanding IPv6 in the context of Windows

Hi!

I've been going through some deep dives lately on IPv6 and fundamentally, I've always understand how it works and know a bit more about the differences with IPv4 now such as SLAAC, RFC4941, DAD, etc.

I've turned IPv6 on now in my home lab, which is just a basic OpenWrt router running the latest firmware. Everything works without issue, but there's a couple things that are bothering me that I don't quite understanding.

From my Router, I see the address that it's assigning to my Windows host. That's all fine and dandy, but within Windows itself I see multiple IPv6 addresses assigned to it when I do an ipconfig. Now initially, this is where I did some research and learned a lot about how Microsoft has implemented RFC4941 and Temporary IPv6 addresseses, this is all over the internet.

For the sake of wanting to see IPv6 without any of that applied, I turned it off so I help correlate the address from my router to Windows directly. The problem is, even after that I usually see two IPv6 addresses associated to a single Network Interface at a time.

I can't for the life of me figure out where the second address is coming from, so I was hoping someone could maybe point me in the right direction for how Windows in particular, works under the context of IPv6 and how I can correlate some of these addresses that I'm assuming must be generating from Windows itself since it's showing up in my ipconfig's on that system.

Hope this all makes sense, and I appreciate any assistance regarding this. I'm moving towards eventually going live with IPv6 with more than just my home-lab, but before I do that I'd like to be able to correlate exactly where some of the addresses come from for eventual troubleshooting scenarios.



No comments:

Post a Comment