If not, compare your Wireshark logs on both systems and look for missing packets on either side. You should now find Kali's IPv6 address set as DNS server if you type ipconfig /all on your victim system. I described part of this issue here: DNS server spoofing only working once #11 (which I will update in a second). However, I wouldn't do this on large networks because I had problems with victim systems which didn't "forget" the DHCPv6 options after 5 minutes and needed to be rebooted. Enable Promisicous Mode on the switch forcing it to act like a hub and send all traffic to all ports.Windows sends ICMPv6 solicit to the all-dhcp-agents multicast address and your Kali machine is not part of this group (although this functionality could be added to mitm6 I guess). Warning: If your lab is running on an ESXi environment your Kali won't see the DHCPv6 messages coming from the client because vSphere virtual switches implement the MLDv2 protocol. mitm6 replies with a final DHCPv6 REPLY message.The victim then sends a DHCPv6 REQUEST message to the multicast group.mitm6 will reply with an DHCPv6 ADVERTISE message to the link-local IPv6 address of the client.The victm sends a DHCPv6 SOLICIT to the all-dhcp-agents multicast address in order to discover the DHCPv6 servers. ![]() Shortly after that the Windows system should start with the following process: One of them caused Wireshark to stop listening because it "found no interface". ![]() ![]() I'm not sure if option 2 or 3 was working with VMware. VM: Disconnect and reconnect the network interface in VMware Workstation.Netsh interface set interface "" disabled
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |