Date: Tue, 21 Nov 2023 07:53:03 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275169] Panic: rw_rlock: wlock already held for tcpinp @ /usr/src/sys/netinet/in_pcb.c:2529 Message-ID: <bug-275169-227-doCG3wRPyd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275169-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275169-227@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=3D275169 --- Comment #17 from Dani I. <i.dani@outlook.com> --- (In reply to Gleb Smirnoff from comment #16) Ah sorry, that wasn't clear in my last comment. No, we have just used "net.link.ether.ipfw=3D1" while testing with out 13.2 hosts - we do not hav= e it set in productive environment. What i meant were the fw rules from our init= ial report, which worked well and without a problem on 12.4: Host A has following IPFW rule: ipfw add 1000 allow ip from me to 10.1.1.20/32 uid 0 Host B has the following IPFW rule: ipfw add 2000 allow tcp from any to 10.1.1.20 80,443 keep-state --=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-275169-227-doCG3wRPyd>