Date: Sun, 19 Mar 2023 06:16:37 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Attila Nagy <nagy.attila@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Fwd: Kernel DHCP unpredictable/fails (PXE boot), userspace DHCP works just fine Message-ID: <1634f44f-cb69-ee74-5300-4a8c414850f4@grosbein.net> In-Reply-To: <CAM2hQG-BtvEz649QsFou_sG-QamEdZscCUygKxSuK_C3_MhNow@mail.gmail.com> References: <CAM2hQG-p=bfSh_nxuah9zcTBbz7HQ9pYyvOR2f6rC=CUGePKsg@mail.gmail.com> <CAM2hQG-oDRsoccg3S1LykyUF=joWbdJz=GSPOnUroDRxjZ2_iQ@mail.gmail.com> <ab14beaf-f41b-8f45-05f6-fad8a764eba3@grosbein.net> <CAM2hQG-BtvEz649QsFou_sG-QamEdZscCUygKxSuK_C3_MhNow@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
19.03.2023 5:01, Attila Nagy wrote: > Sometimes UEFI/BIOS SETUP has some settings for ACPI/HPET timers (enable/disable), > did you try "playing" with such options? > > Nope, I haven't thought about that. > It's enabled (default setting). Another possible reason: DHCP packets sent from DHCP client have 1-bit flag indicating if client wants to receive an answer as unicast or broadcast UDP packet. You could try hacking source to force broadcasts and see if that changes things. This NIC's driver has previous history of bad in-chip filtering packets in transit from the wire to the host (CPU). Broadcasts should get through without a problem, nevertheless. https://www.rfc-editor.org/rfc/rfc2131#section-4.1 > A client that cannot receive unicast IP datagrams until its protocol > software has been configured with an IP address SHOULD set the > BROADCAST bit in the 'flags' field to 1 in any DHCPDISCOVER or > DHCPREQUEST messages that client sends. The BROADCAST bit will > provide a hint to the DHCP server and BOOTP relay agent to broadcast > any messages to the client on the client's subnet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1634f44f-cb69-ee74-5300-4a8c414850f4>