With the advent of USB-Ethernet, it became clear that @Zeroconf was not foreseen for tested with hot-plug devices.
The following new and old issues have surfaced:
Interface identify is incorrectly tied to the interface number (we should also check the MAC address)
DHCP lease expiration is not implemented
Out of boundary checks are missing in parser
The service can be started multiple times simultaneously, which should not be allowed.
With the advent of USB-Ethernet, it became clear that @Zeroconf was not ~~foreseen for~~ tested with hot-plug devices.
The following new and old issues have surfaced:
1. Interface identify is incorrectly tied to the interface number (we should also check the MAC address)
2. DHCP lease expiration is not implemented
3. Out of boundary checks are missing in parser
4. The service can be started multiple times simultaneously, which should not be allowed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
With the advent of USB-Ethernet, it became clear that @Zeroconf was not
foreseen fortested with hot-plug devices.The following new and old issues have surfaced: