Date: Sat, 22 Oct 2022 04:06:44 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 252165] usb network and mii bus media status race condition Message-ID: <bug-252165-7501-Ino7Nd3Ued@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252165-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-252165-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=3D252165 --- Comment #25 from vxasxfepbikrfqdruz@nvhrw.com --- (In reply to Ali Abdallah from comment #24) Yeah, I was pretty surprised as well that this is entirely broken despite several USB to ethernet adapters being listed as supported by FreeBSD. This also affects pfSense and opnSense which you think would generate some atten= tion about this, but they just seem to recommend not using USB adapters at all.= =20 If it's any help when I was getting my USB adapters I checked with the supported devices list and the comments on amazon. There were several comme= nts saying their adapters worked fine with freebsd with the latest one being fr= om October 2016. That would mean this problem was probably introduced sometime between v10.4 and now. This is kinda over my head but I would really appreciate if this were fixed= and I was able to build the fixed mii module. Thank you for your efforts. P.S. This is only sort of related but there's another issue with USB adapte= rs if you have more than one. They get picked up at boot in a random order so which adapter is which interface will get shuffled every boot. I was able to mitigate that using the ethname package. --=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-252165-7501-Ino7Nd3Ued>