Date: Fri, 13 Jul 2018 18:23:28 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 229727] On install, Broadcom chipset doesn't receive DHCPOFFER Message-ID: <bug-229727-7501-s1sTxmbCjK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229727-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-229727-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229727 --- Comment #7 from Stephan Neuhaus <sten@artdecode.de> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229727-7501-s1sTxmbCjK>