[Bug 186114] net/mpd5 hangs after a certain number of users connect

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 --- Comment #74 from Kubilay Kocak --- (In reply to Eugene Grosbein from comment #73) I order to ensure that (base) change is tracked and merged correctly, I'd recommend (as suggested in comment 69) creating a separate dependent issue so t

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #12 from Eugene Grosbein --- (In reply to Cassiano Peixoto from comment #10) You can also just skip this patch for now if your system does not process any multicast traffic including routing protocols like OSPF or RIPv2. -- Y

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #11 from Eugene Grosbein --- (In reply to Cassiano Peixoto from comment #10) You have revision earlier than 315456 that changed context for this patch: - CTR3(KTR_IGMPV3, "%s: imr_interface = %s, ifp = %p", -

RE: Solution Seekers| Facility Management

Hi, I am Teresa from B2B Data Group., Following one of our recent market studies; we have compiled a list of Facility Management Professionals and this list can be used for your marketing initiatives, to provide them your Solutions. The list has been based on the following requirements: *

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #10 from Cassiano Peixoto --- (In reply to Eugene Grosbein from comment #9) mcast has been reject: # patch < mcast.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -- |-

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #9 from Eugene Grosbein --- (In reply to Cassiano Peixoto from comment #8) Kernel only. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@f

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #8 from Cassiano Peixoto --- (In reply to Eugene Grosbein from comment #7) Do i need to recompile the world or only the kernel? -- You are receiving this mail because: You are on the CC list for the bug. __

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 --- Comment #7 from Eugene Grosbein --- (In reply to Cassiano Peixoto from comment #6) This PR presents several patches for several kernel subsystems. Apply patches for ip_mcast.c and ip_input(). The patch for ipfw is only needed if you

[Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to unlocked INADDR_TO_IFP usage

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078 Cassiano Peixoto changed: What|Removed |Added CC||freebsd-net@FreeBSD.org -- You

[Bug 220076] [patch] [panic] [netgraph] repeatable kernel panic due to a race in ng_iface(4)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220076 Cassiano Peixoto changed: What|Removed |Added CC||freebsd-net@FreeBSD.org -- You

[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 --- Comment #35 from Eric Joyner --- (In reply to pete from comment #34) I don't think this change is causing your problem. It only changes something in an 82574-specific conditional. -- You are receiving this mail because: You are the a

[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 --- Comment #34 from p...@twisted.org.uk --- Actually, not quyite that simple. Sometimes it works, sometimes it does not. If it does not then ifconfig em0 down and ifconfig em0 up will get it working again. The only chnage to em0 is the appl

[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 --- Comment #33 from commit-h...@freebsd.org --- A commit references this bug: Author: sbruno Date: Mon Jun 19 15:56:03 UTC 2017 New revision: 320117 URL: https://svnweb.freebsd.org/changeset/base/320117 Log: Direct commit to stable/10 t

[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 p...@twisted.org.uk changed: What|Removed |Added CC||p...@twisted.org.uk --- Comme

[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 --- Comment #31 from commit-h...@freebsd.org --- A commit references this bug: Author: sbruno Date: Mon Jun 19 15:03:48 UTC 2017 New revision: 320102 URL: https://svnweb.freebsd.org/changeset/base/320102 Log: Direct commit to stable/11 t

[Bug 210726] tcp connect() can return invalid EADDRINUSE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210726 --- Comment #4 from a...@playground.ru --- Can this be processed more fast to make it patched in upcoming 10.4? -- You are receiving this mail because: You are the assignee for the bug. ___ freeb