Date: Wed, 02 Mar 2016 02:21:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207633] bce0: Discard frame w/o leading ethernet header (len 0 pkt len 0) - pfSense 2.2.6 and 2.3 Beta Message-ID: <bug-207633-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207633 Bug ID: 207633 Summary: bce0: Discard frame w/o leading ethernet header (len 0 pkt len 0) - pfSense 2.2.6 and 2.3 Beta Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: parwok@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I recently my physical pfSesne install to a virtual machine. I have tried b= oth pfSense 2.5.6 and 2.6 in kvm and am passing two physical interfaces through, using a Proxmox (debian) host. Each interface is a BCM5709, in a Dell Power= Edge R710. I have found that in order to work around the issue, I have to disconnect t= he ethernet cables and allow pfSense to fully boot to the login prompt before reconnecting them, or else all interfaces spam discard frame errors with le= n 0 and pkt klen 0. Occasionally, even this workaround fails. This is problematic in the case of a power event, as it means I will need t= o be physically present for the network to come back up. While I realize I'm thankfully not using this in an enterprise environment, it would be nice to= fix this issue if possible. Original bug on pfSense tracker: https://redmine.pfsense.org/issues/5649 --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207633-6>