First post, by superfury
I've been improving the packet server (in git only atm, not released yet) a bit(DHCP still a WIP).
It now has response to ARP packets when it receives ARP requests for the configured IP address of a logged in user(as in it's (default) IPaddress setting).
Could this cause issues with Windows 10 somehow? After testing it(Windows 10 being configured with a static IP in the network card settings), I see the original IP in "arp -a". But after I issue a ping command to the IP that's different in UniPCemu's settings(a logged in user with a different IP), the IP reported by arp changes to the new setting and "arp -a" doesn't change back to the old setting, even when performing a ping to the old IP address?
I also ran into issues with the network card when I tried to disable and then re-enable it in the settings of the card, with Windows being unable to start it back up again(device manager gave some kind of error code), even after a full reboot (needed to run Windows system restore to an earlier restore point to fix this)?
Does the server also need to respond to ARP packets to the original IP address(before being changed by UniPCemu's reply ARP packet)? Or does Windows do that itself already?