That means the number of possible outcomes is 16 raised to the power of 12. That’s 16 possible outcomes for each digit. What about this MAC address thing? As Bart explained last week, MAC addresses have 12 digits, where each digit can be 0-9 and a-f. Now that we can calculate how many bits we have where there’s only 1s and 0s. So 3 coins is 2 raised to the power of 3. What about 3 coins or bits? It turns out the answer is 2 to the power of however many of them you have. Same thing with bits, they’re 1 or 0 so two possible outcomes with one bit. A coin has heads and tails, so two possible outcomes. He explained bit by talking through flipping of a coin. I know I should already know this and I explained to him that he’s just the next in a long line of people attempting to get it to stick in my brain, but he said he was determined to get me to understand. Bart first had to explain to me what bits were. First of all, Bart wasn’t technically wrong, but DJ and Kevin are more specifically correct.īecause Bart and I are nerds, we decided to work out the answer, and actually “do the math” and see if they’re right that MAC addresses are 48 bits not 64 bits. Now this is going to sound a bit like explaining the tax code but I hope you’ll bear with me because there are a couple of parts here I think are interesting. They both explained that MAC addresses as we are used to seeing them, are 48 bits, not 64 bits. This is conveniently the length of a MAC address. In IPv6, the host part is always 64bits long. Seriously,Īnyway, they were both commenting on this statement: As always though, Bart is weird in that he actually likes to be corrected. One of the rules of this episode was that Bart only had a few days to learn the background himself so it was expected there might be errors. After the show aired, Kevin Jones DM’d me on Twitter and DJ made a comment on the blog, both with the same correction. Can’t rely on the windows randomly generated IPV6 address.In last week’s Chit Chat Across the Pond, I asked Bart to come during his off season to explain IPv6 to us. Therefore if I want to parse the WDS log files to identify each PC in the logs I need to construct the IPv 6 address using the EUI-64 method. This site explains, the Windows does not use the Mac address to generate the IPv6 LinkLocalAddress IPv6: How Windows generates Link-Local Addresses (EUI-64) – SID-500.COM. We are talking about the same Ethernet device. The windows IPv6LinkLocalAddress value for that device is fe80::6d8d:28d8:191b:3f30%3 in this example the WDS server show a log entry such as : The WDS Bitlocker network unlock logs show the IPv6 Link local address of the physical device when the client PC is booting, and it the PC’s UEFI bios that send’s out the Network unlock request. I agree simple is better but in this case it does not work, The WDS logs are obtained in this manner $WDSEventsVerbose = Get-WinEvent -cn $WDS -EA silentlycontinue -FilterHashtable = (Get-Netadapter -CimSession $Script:RemoteCimSession | Where-Object įor remote systems just use PSRemoting as normal. I am parsing WDS network unlock logs and want to identify source computer. I got starting by getting the Mac I am interested in. Note the that IPV6 address obtained by the ipconfig / Get-NetIPAddress are not suitable for my needs, these address obfuscate the Mac address. prepend the link-local prefix: fe80::5074:f2ff:feb1:a87f.replace first octet with newly calculated one: 5074:f2ff:feb1:a87f.convert octet back to hexadecimal: 01010000 -> 50.convert the first octet from hexadecimal to binary: 52 -> 01010010.reformat to IPv6 notation 5274:f2ff:feb1:a87f.take the mac address: for example 52:74:f2:b1:a8:7f.basically doing this ( ref ) in powershell. Trying to convert a Mac address to an Ipv6 link-local address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |