From owner-freebsd-net@freebsd.org Fri Jul 13 18:23:30 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4980E1047435 for ; Fri, 13 Jul 2018 18:23:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D0D017277C for ; Fri, 13 Jul 2018 18:23:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 94BA91047430; Fri, 13 Jul 2018 18:23:29 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80DCE104742F for ; Fri, 13 Jul 2018 18:23:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 199BF72777 for ; Fri, 13 Jul 2018 18:23:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6E36CF63E for ; Fri, 13 Jul 2018 18:23:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6DINSdw098883 for ; Fri, 13 Jul 2018 18:23:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6DINSWq098876 for net@FreeBSD.org; Fri, 13 Jul 2018 18:23:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 229727] On install, Broadcom chipset doesn't receive DHCPOFFER Date: Fri, 13 Jul 2018 18:23:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sten@artdecode.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 18:23:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229727 --- Comment #7 from Stephan Neuhaus --- Replying to Rodney W. Grimes form comment #5 and comment #6 There are two other machines (one another Debian, one Windows 10) hanging o= ff that (very cheap, consumer-grade Netgear) switch for which DHCP works. Also= , if I install Debian on the same laptop on the same port on the same switch, DH= CP *also* works. So I don't see how STP can be the root of this issue, but I'll try your suggestions. I cannot turn off STP or change the way it does STP, since it is not manage= d. If you say that putting it next to the server (which hangs off another swit= ch, this time managed) doesn't solve the problem, I will try fiddling with the = STP parameters on *that* switch and see if it solves things.=20 I must admit though, should that make it work, it would be deeply mysteriou= s to me. But I'm willing to concede that my mental model of how these things oug= ht to work might be totally wrong :) As to your other questions: "Are you using the PXE client in the broadcom BIOS?" I don't even know what that means, TBH. I'm using an old MacBook Pro, which happens to have a Broadcom NIC in it. "Are you using any VLAN taggging stuff?" Nope. "Is this NIC in use as a shared IPMI device?" Nope. This NIC runs in a lapt= op. Cheers Stephan --=20 You are receiving this mail because: You are the assignee for the bug.=