Ting, Any follow up on this? Is this an issue in the current EDK2 implementation that needs to be fixed?
Thanks, --Samer -----Original Message----- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of El-Haj-Mahmoud, Samer Sent: Friday, July 31, 2015 9:39 AM To: edk2-devel@lists.01.org Subject: [edk2] Concerns with IP4Config2 - Part 2 - DHCP re-initiate on connectivity issues This is Part 2 of the issues we observed in IP4Config2 in EDK2 On the UEFI 2.4 IP4Config Protocol, if the NIC is configured for DHCP, the IP4 driver instance for that NIC would re-initiate a DHCP if it detects that there is a network blip (cable remove, reconnect for example). On the UEFI 2.5 EDK2 (Ip4Config2 protocol) this doesn't happen. Can someone confirm please if this is an issue or is by design? This seems like a regression from the previous IP4Config implementation. Samer El-Haj-Mahmoud System Firmware Architect HP Servers el...@hp.com TÂ +1.281.514.5973 C +1.512.659.1523 Hewlett-Packard Company http://hp.com/go/proliant/uefi _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel