Hi Sir, Here is the BIOS engineer from Quanta Computer Inc., there is a requirement from our customer regarding networkstack driver, can you please help on this?
Issue: There is one network issue in customer datacenter, the “ClientID/DUID/Link-Layer Address” is not bundled with the MAC from source network device if multi LANs on the system. And, this cause the PXE boot failure at customer datacenter environment. On our system, it has two network devices, one is Intel NIC, the other is Mellanox NIC, from RFC mentioned, either one MAC of both NICs can be used to generate the DULD-LLT. However at customer Data Center, they do NOT accept this. Each interface needs to generate their DUID-LL(T) based on their own LL. This means that they must use their own MAC address. Both interface will have different DUIL-LL(T), which is technically against the RFC here. Can you please help to check how networkstack driver could be supported on this requirement? https://tools.ietf.org/html/rfc3315#section-9 9.2<https://tools.ietf.org/html/rfc3315#section-9.2>. DUID Based on Link-layer Address Plus Time [DUID-LLT] This type of DUID consists of a two octet type field containing the value 1, a two octet hardware type code, four octets containing a time value, followed by link-layer address of any one network interface that is connected to the DHCP device at the time that the DUID is generated. The choice of network interface can be completely arbitrary, as long as that interface provides a globally unique link-layer address for the link type, and the same DUID-LLT SHOULD be used in configuring all network interfaces connected to the device, regardless of which interface's link-layer address was used to generate the DUID-LLT. Thanks, Jim _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
