If the mac is 2e:c9:44:xx:xx:xx, is it: 20c9:44ff:fexx:xxxx(just incrementing bit +2) 30c9:44ff:fexx:xxxx(incrementing bit +2 and adjusting preceding bit to +1 since former carried over max value of F) 2cc9:44ff:fexx:xxxx(decrement bit -2) Thanks for your time.
It would be 8D. So you only change the second number, and they switch back and forth on that chart. His examples always use the top number/letter, so it made it a little ambiguous, but that's why the arrows go both ways. So D would change to F, and F would change to D. So in this case it's F -> D, making it 8F -> 8D.
Is this just creating the host portion of the IPv6 address? If an IPv6 address is 128 bit, where does the other 64 bits come from for this automatic static IP configuration?
A question: In step 3 of the DHCPv6 process. If there can be multiple DHCP servers in the subnet advertising their existance, how does the client direct its DHCP Request to the specific one it chooses if its sent as a multicast? I'm assuming this is just a simple explanation and not going into the details fully.
Probably similar to the way it works in IPv4. It's based on route cost. It's almost like a priority list, or pecking order, if you will. Whoever has the lowest cost, that is the server that will get the request.
Why would there be multiple DHCP servers on the same subnet? DHCP requests are sent via a broadcast. The DHCP server for that subnet is the one that will respond. (?)
Couldn't this be a security issue? If you're using the full MAC address, which is a unique identifier of the company and technically their serial number, then you could possibly trace the IPv6 address to said company and ask to who the product sold? Or am I missing something?
Give it a try with your own MAC address and see what the vendor says. I'd be shocked if they released any actual information other than troubleshooting links. Every vendor, for every product, I have ever contacted has always asked for my proof of purchase for anything beyond basic support. Even if they gave you the sale info, it would just lead back to a supplier, not you personally. It's moot right now anyway. Everything is happening at ipv4 on the internet, and will do so until probably 2030. I doubt they will allow your personal ipv6 address based on your MAC on the internet even if it's designed to. First thing I think of is Spoofing MAC addresses, and you can see this when you phone connects to a new AP under properties. To protect your identity (even though they were the ones who tracked you that way in the first place!) they give a random MAC address to the AP unless you change the setting for that connection. So what happens when NAT is gone and you have duplicate ipv6 addresses on the internet from MAC spoofing? Well you can't, so you end up with something like the same solution we did for ipv4.
Oh my god. Thank you SO MUCH for the quick conversion. I love you.
You are a god. Thank you Professor.
I just figured out how to count binary with my fingers, that works for me to do the conversion quick.
How?
If the mac is 2e:c9:44:xx:xx:xx, is it:
20c9:44ff:fexx:xxxx(just incrementing bit +2)
30c9:44ff:fexx:xxxx(incrementing bit +2 and adjusting preceding bit to +1 since former carried over max value of F)
2cc9:44ff:fexx:xxxx(decrement bit -2)
Thanks for your time.
We are just inverting the binary value of the 7th bit so it would be 2C:C9:44, I believe.
What if the MAC address started with 8F, would it be changed to 91?
It would be 8D.
So you only change the second number, and they switch back and forth on that chart. His examples always use the top number/letter, so it made it a little ambiguous, but that's why the arrows go both ways. So D would change to F, and F would change to D. So in this case it's F -> D, making it 8F -> 8D.
@@BeyondDNA-gv3pf Oh ok, that explains why the arrows go in a circle like that, thank you for clarifying it
@@jojobaggins9224 Sure thing!
This is great!
Is this just creating the host portion of the IPv6 address? If an IPv6 address is 128 bit, where does the other 64 bits come from for this automatic static IP configuration?
A question: In step 3 of the DHCPv6 process. If there can be multiple DHCP servers in the subnet advertising their existance, how does the client direct its DHCP Request to the specific one it chooses if its sent as a multicast? I'm assuming this is just a simple explanation and not going into the details fully.
Probably similar to the way it works in IPv4. It's based on route cost. It's almost like a priority list, or pecking order, if you will. Whoever has the lowest cost, that is the server that will get the request.
Why would there be multiple DHCP servers on the same subnet? DHCP requests are sent via a broadcast. The DHCP server for that subnet is the one that will respond. (?)
Couldn't this be a security issue? If you're using the full MAC address, which is a unique identifier of the company and technically their serial number, then you could possibly trace the IPv6 address to said company and ask to who the product sold? Or am I missing something?
Give it a try with your own MAC address and see what the vendor says. I'd be shocked if they released any actual information other than troubleshooting links. Every vendor, for every product, I have ever contacted has always asked for my proof of purchase for anything beyond basic support. Even if they gave you the sale info, it would just lead back to a supplier, not you personally.
It's moot right now anyway. Everything is happening at ipv4 on the internet, and will do so until probably 2030. I doubt they will allow your personal ipv6 address based on your MAC on the internet even if it's designed to. First thing I think of is Spoofing MAC addresses, and you can see this when you phone connects to a new AP under properties. To protect your identity (even though they were the ones who tracked you that way in the first place!) they give a random MAC address to the AP unless you change the setting for that connection.
So what happens when NAT is gone and you have duplicate ipv6 addresses on the internet from MAC spoofing? Well you can't, so you end up with something like the same solution we did for ipv4.