From nobody Fri Mar 17 20:16:17 2023 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pdb4Y2xWMz3ynZm for ; Fri, 17 Mar 2023 20:16:29 +0000 (UTC) (envelope-from nagy.attila@gmail.com) Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pdb4X6qQ1z3jyQ for ; Fri, 17 Mar 2023 20:16:28 +0000 (UTC) (envelope-from nagy.attila@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x22c.google.com with SMTP id s41so4643185oiw.13 for ; Fri, 17 Mar 2023 13:16:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679084188; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WHmwdMVtZCKM+HEKSSj9HvLG3Dd0wzmQFV9QGsRjEO4=; b=Qh9pgGSKstCwPI23n1ZBNqvPz1zSJq3DRYNH9ErX8NfH38H2wqEfvok8rx4PiflAiI 6lHeliQypj+IO2bhU8Cq4FIhUo5rjT/fHTM51slvfw8aaTey70+gV6GdXT9OTfpLnK8z FVgUTWqndzMpRQ6u6OxwOd4bukmwP/UOkq5ZDvqCPI4jFtOn+Yn1ZrfI3a7Gemlk1Cri cTSFUNkc2o9J4lRvcL3FpziK4B0/zhF9BcRgKtsmo3or2MpK0AGyNRxjZSw0RSDk/QpZ yuH8/xpZ1bXG3IzUTjeXyo/6DJmdE9kr2oeAkZsKYIWh44sxQ7Wb/8D28SpTcNM0Fvax pWaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679084188; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WHmwdMVtZCKM+HEKSSj9HvLG3Dd0wzmQFV9QGsRjEO4=; b=69uaWPGQ2EOnr0iMbeKb4dJD1rDZSd7Gek6K+eYyY1dLIOlqQ3+btpdMT5ii7yKHeO AY3f2621QJt3RfP8c+Azk2cFiOvVN7SPKskrztADBrS4cYeQnNvt5NFG3HCOunZgBuci 9K6NdeKw7CCjogOPEc3X9wzwZ0YKmSWXcZGX3iJJzStlY2dlO63CNkkq/fomLgEGSUig fAnsM0VdK/IaUEwB5JTLkHsa5Vqit/5kuYoULcv6SUi+ooYwZqjTGaNTaROEMcy7NdQT Y/5h9QSvr3jOX/Lyx0uJyLYjSHarz1xApxAMPa68ZWy0rOXlHj1RsdihTyysv92Ap1Cg dQtw== X-Gm-Message-State: AO0yUKW7TfeOIYdRv9FKbd4UAMjp2L4jNwUbXKzM+2nBz0VjWI19IBt4 m0qEROxkmdm90/9cRFr3VSnDYhqh1pbj0t0JEKweIh91 X-Google-Smtp-Source: AK7set8bDJQpaiYokya2KdJNBrh5Voi08H4n9L4SGgFjrVat3gmiEHj4XIKcdh/w2U9E8+pmJsvDJ/UawsY/tpEyOGM= X-Received: by 2002:aca:1717:0:b0:386:9718:cfeb with SMTP id j23-20020aca1717000000b003869718cfebmr3765983oii.11.1679084188084; Fri, 17 Mar 2023 13:16:28 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <0b95a502-eea0-46cc-5d0d-ec6e861ad51f@marco.de> In-Reply-To: <0b95a502-eea0-46cc-5d0d-ec6e861ad51f@marco.de> From: Attila Nagy Date: Fri, 17 Mar 2023 21:16:17 +0100 Message-ID: Subject: Re: Fwd: Kernel DHCP unpredictable/fails (PXE boot), userspace DHCP works just fine To: Matthias Pfaller Cc: stable@freebsd.org Content-Type: multipart/alternative; boundary="000000000000942f1205f71e4052" X-Rspamd-Queue-Id: 4Pdb4X6qQ1z3jyQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000942f1205f71e4052 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Matthias Pfaller ezt =C3=ADrta (id=C5=91pont: 2023. m=C3=A1r= c. 17., P, 7:24): > > Do you have STP/RSTP enabled on the switch ports? When the link goes down > when > switching from firmware mode to kernel mode, the port will go back to > blocking. When > the dhcp requests don't make it to the dhcp server because of this and th= e > link goes > down and up again while retrying (don't know if this happens) you will ge= t > the same > problem on the next try. As a simple test you could put a dumb unmanaged > switch > between your core network and the server. > Thanks for the idea, but I don't think this might be the case. I can see the UDP datagrams coming into the kernel (replies to DHCP messages). --000000000000942f1205f71e4052 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable